Their domain
Served from the client's own domain
Point a subdomain at us and the page is issued its own certificate automatically. Visitors see the client's domain and your branding, and nothing else.
Trust pages
A trust page you publish, on the client's own domain
The page a client's prospects ask for before the questionnaire arrives. Built from the same confirmed facts as their documents, served from their domain, with no sign of the tool that made it.
Free · No sign-up · Up to ten websites
What is a trust page?
A trust page is the public page where a company answers the security and privacy questions its buyers ask first: where data is held, which sub-processors are used, how access is controlled, how an incident is handled, and which documents can be requested.
It is worth having because it moves work earlier. Questions answered on a page are questions that do not arrive as a spreadsheet, and a prospect who can read the sub-processor list at two in the morning does not open a thread with your client's sales team.
What it has to cover
- Sub-processors, with entity, country and purpose for each
- Where data is stored and which transfer mechanisms apply
- Technical and organisational measures, in plain language
- Documents available on request, and how to request them
- A contact for privacy and security questions
What changes when it is not done by hand
Same facts
It cannot drift from the documents
The page reads the same confirmed facts and the same vendor records as the client's pack, so the published list and the contractual annex agree by construction.
Requests to you
Document requests arrive as work, not email
A request for a document reaches your workspace with who asked and for what, so you decide what is shared rather than finding out later.
What you get
Every vendor fact comes from our own registry: 157 vendors with the date each entry was checked.
Custom domain with automatic certificates
Add the client's subdomain, they add one DNS record, and the certificate is issued and renewed without anyone handling a key.
Your brand, not ours
Your firm's logo and colours. No logo, link or mention of us anywhere on the page.
Sub-processor list from the registry
Published straight from the verified records, with the date each vendor was last checked.
You choose what is public
Each section is published only when you turn it on. Nothing goes public because it exists in the workspace.
Document requests with a trail
A visitor asks for a document, you approve or decline, and the decision is recorded.
Updated when a vendor changes
A change to a published vendor marks the page so you can republish before a prospect reads something untrue.
Get started in three steps
- 1
Choose what the client publishes
Turn on the sections the client is comfortable making public, from the facts they already confirmed.
- 2
Point the domain
The client adds one DNS record for a subdomain of their own. The certificate is issued automatically.
- 3
Publish, and keep it true
Publish under your brand, handle document requests from the workspace, and republish when a vendor change touches the page.
Questions
- Does the page mention you anywhere?
- No. Not in the page, not in its source, and not in the documents it offers. The client engaged your practice, and that is what the page shows.
- Who controls what is published?
- You do, section by section. Nothing becomes public automatically.
- What happens to a document request?
- It arrives in your workspace with the requester and the document asked for. You approve or decline; the decision is recorded.
- Can several clients have pages at once?
- Yes. Each client has its own page, its own domain and its own published sections.
- Is a trust page a substitute for a questionnaire?
- No, but it answers the common questions before they are asked, which makes the questionnaires that still arrive shorter.
See what changed since your clients' policies were written
Enter up to ten client websites. Free, no sign-up, the first report in about a minute.