.webp)
We sell SaaSFrame licenses on Gumroad, a secured online selling platform for creators.
SaaSFrame gets updated all the time! Every new update and version will immediately be made available to all SaaSFrame users.
The licence key required to create your SaaSFrame account is send by Gumroad once you made your purchase. If this email is blocked by your email client, send me an email at antoine[at]unmake[dot]io so I can resend the licence key.
You can generate an invoice on Gumroad once you purchased SaaSFrame. You will find the link in the order confirmation email.
If you're not satisfied, you can ask for a refund within 7 days. Just send me an email at antoine[at]unmake[dot]io
A SaaS compliance page helps prospective customers find the information needed for an organizational review. Its design should connect clearly scoped statements to maintained documents, relevant evidence, and an appropriate contact route.
This is a guide to page structure, not legal advice or an assessment of any product's compliance. The SaaSFrame captures show how companies present information; the screenshots do not independently verify their claims.
A reviewer may need to understand data processing, hosting, subprocessors, agreements, or assurance documents. Group content so those questions have recognizable entry points.
Avoid a broad compliant headline with no scope. Visitors need to know which service, operation, or document a statement concerns.
Use plain summaries for orientation and maintained documentation for detail. The summary should help readers locate evidence without replacing the authoritative material.
The Fernand capture uses a largely textual page with sections about information handling, security, rights-related topics, agreements, and questions. An update date appears near its introduction.
This format can hold substantial detail, but headings and navigation need to support lookup. A reviewer should not have to read every paragraph to find an agreement or relevant contact.
Keep dates meaningful and content ownership clear. A visible date does not establish that every statement remains current; the underlying review process must support that expectation.
The Forest Admin reference separates audit-related information from ongoing monitoring and transparency, then provides a questions area. Different labels identify the subjects of its statements.
That separation matters because an audit report, regulatory statement, operational practice, and customer testimonial are different kinds of information. Do not make them appear interchangeable through identical badges.
Explain the scope and route to supporting material for each claim. Marketing language should not imply that a logo alone proves every aspect of the service has been independently assessed.
The NewsCatcher capture uses assurance cards above an enterprise-compliance section and customer-oriented material. This makes the page scannable but requires careful alignment between concise labels and supporting detail.
For your page, provide a direct evidence route or explain how a reviewer can request restricted material. An inaccessible generic sales form can slow a review when the visitor only needs a specific document.
Do not reproduce another company's claims as guidance for your own service. Each statement needs verification by the responsible team and alignment with current operations.
A processing agreement, policy, audit report, and security contact serve different purposes. Label destinations by the document or task rather than using a vague learn-more link everywhere.
If a document requires an access request, explain the process and the information needed. Avoid implying immediate availability when approval is required.
Preserve a route for questions the public page cannot answer. A reviewer should be able to identify who handles the inquiry without submitting an unrelated product demo request.
State relevant service or regional scope where it affects a claim. Avoid an absolute assurance that is broader than the evidence behind it.
Do not infer requirements or legal obligations from a design reference. Use the product's maintained legal and assurance material for exact wording.
Keep customer proof contextual. A case study can illustrate adoption but does not substitute for a reviewer's requested documentation.
Check that linked documents exist, labels match their contents, dates are appropriate, and access requests reach the intended route. Review changes to claims when the service or evidence changes.
Use SaaSFrame's compliance-page references to compare information hierarchy and document access. The useful pattern is making a review easier through accurate scope and findable material.
No. Identify the claim's scope and provide an appropriate route to its supporting information.
The access model depends on the material. Explain any request process clearly and keep public summaries accurate.
Verify claims with responsible owners and check every document, date, and contact route. Visual clarity cannot compensate for stale information.
