Trust Centre
Customers and prospects ask the same questions again and again: what are you certified against, what policies do you have, who are your subprocessors, have you been pentested? The trust centre answers them on one public page, at an address you can put in a sales pack or a procurement reply, drawn from the records you already keep in QuantAssure.
You choose exactly what is published. Nothing appears on the public page until you switch the trust centre on, and then only what you have ticked.
Setting It Up
Open Settings → Trust centre. The tab is for owners and admins only; members and viewers don't see it. Work down the page, then choose Save at the bottom. The page confirms with "Trust centre settings saved".
- Enable Trust centre ("Make your compliance posture
publicly visible"). Turning it on shows your Public URL,
which looks like
/trust/your-organisation-slug. Anyone with the address can open the page; no sign-in is needed. - Organisation Details: a Description (up to 2,000 characters) shown under your organisation's name, and a Contact Email. When there is a contact email the page ends with a "Need More Information?" panel and a Contact Security Team button.
- Choose what to publish, using the sections below.
- Choose Save.
Open the Public URL and check it as a visitor would before you share it. Switching the trust centre off makes the page return "This trust centre does not exist or is not enabled."
What You Can Publish
Each section below is a list of your own records with a tick box. A section appears in settings only when you have something to choose from, and on the public page only when you have ticked something.
| Settings section | Public page section | What visitors see |
|---|---|---|
| Published Frameworks | Compliance & Certifications | For each framework you target: its name, its status (In progress, Achieved or Lapsed), and its achieved, last audit and next audit dates and scope where you've recorded them. These come from the frameworks you target under Settings → Compliance and Compliance → Frameworks. |
| Published Policies | Security Policies | A table of each policy's name, category, version, status and last reviewed date. Only your active policies are offered, and an archived policy is left off the public page even if it is still ticked. The policy text is not published here; to let someone read it, use a share link (below). |
| Subprocessors (a switch) | Subprocessors | Every vendor you've marked as a subprocessor: its name (linked to its website), processing purpose, data categories, data location and DPA status (Signed or Pending). To add one, turn on the Subprocessor switch on the vendor's edit page. |
| Published Security Tests | Security Testing | For each pentest report you tick: its name, who carried it out, its status, date and scope, and the number of findings by severity (Critical, High, Medium, Low), or "No findings". The report itself is not published. |
| Published Q&A | Security Questions & Answers | For each completed questionnaire you tick: each reviewed question with its category and answer. Where someone has edited an answer, the edited wording is shown. Answers nobody has approved or edited are left out. Confidence ratings and sources are not shown. Beside each questionnaire the tab reads "N of M answers reviewed". |
Questionnaire answers are drafted by AI, and only answers a person has approved or edited are public. Ticking a questionnaire does not publish its unreviewed answers; they appear once someone reviews them on the questionnaire's page. See Questionnaires.
If your organisation already published a questionnaire before this change: answers that a person had not edited are no longer public. Open the questionnaire and approve them to bring them back. Answers a person had already edited stay public.
Keep the lists current. A published item stays published until you untick it. If a framework lapses, check this tab so the public page still says what you intend. A policy that you archive is hidden from the public page automatically, but stays ticked here until you untick it.
Sharing Documents by Link
For anything that shouldn't be public for everyone, such as the policy text itself or a compliance report, create a time-limited share link and send it to the one person who needs it. The Shared Documents section is described as "Create time-limited share links for policies and reports".
- Choose a Document Type: Policy or Report.
- Choose the Document. Type to filter the list. The list offers active policies that have written content in QuantAssure or a link to a source document, and completed reports.
- Choose Expires In: 1 day, 7 days, 30 days or 90 days.
- Choose Create Share Link. The page shows "Share link created!" with the link and a Copy button.
Copy the link straight away. QuantAssure stores only a fingerprint of it, so it can't be shown again. If you lose it, revoke the link and create a new one.
Unlike the other settings, share links take effect at once; you don't need to choose Save. The table below the form lists each link's Document, Type, Expires date and Views, with a Revoke button that switches the link off immediately. With none, it says "No share links". An expired link stops working and is marked Expired in the table; revoke it to remove it.
What the recipient sees
The link opens a "Shared Document" page showing the document's name, who shared it and when the link expires, with a View Document button:
- A policy written in QuantAssure opens as a formatted page. A policy that links to a document elsewhere, such as Google Drive, sends the visitor to that link, so make sure they can open it. A policy with neither shows "This document is available upon request", with a Request Access button that emails your contact address.
- A report downloads as a JSON file.
- An expired or revoked link shows "Link Not Available" and asks the visitor to contact you for a new one.
Share links work on their own: they don't depend on the trust centre being switched on.
Embed Badges
Once the trust centre is enabled and at least one framework is ticked, the Embed Badges section ("Add compliance badges to your website") shows a small badge for each published framework, reading "QuantAssure" and the framework's name and status. Choose Copy to copy the HTML snippet, and paste it into your website. The badge links to your trust centre page.
A badge updates itself as the framework's status changes, though browsers and CDNs may hold on to the old image for up to an hour. If you untick the framework or switch the trust centre off, the badge stops loading.
Who Can Do What
| Role | Can |
|---|---|
| Owner, Admin | See the Trust centre tab, change what is published, create and revoke share links |
| Member, Viewer | The tab is hidden, and changing trust centre settings or share links is refused. Members can still review questionnaire answers (see Questionnaires). They can see the public page like any visitor. |
| Anyone on the internet | Open the public page when it's enabled, and open a share link until it expires or is revoked |
How It Connects to the Rest of QuantAssure
- Compliance: framework status and audit dates published here come from your framework targets.
- Policies: policies must be active to be offered, and their version and review date are shown.
- Questionnaires: the source of the Q&A section.
- Reports: completed reports can be shared by link.
- Vendors and Pentests: the sources of the Subprocessors and Security Testing sections.
- Audit log: changes to the trust centre settings, creating and revoking share links, approving and editing questionnaire answers, and each time a shared document is opened are recorded, so you can see who has looked at what.
The trust centre does not use AI itself and doesn't publish findings, severities or risk scores.