Product

Trust Centre

Publish approved security, privacy and compliance information through a branded customer-facing site.

Simplified illustrative trust centre publishing workflow with fictional sample data

The outcome

Give customers and partners a reliable place to find assurance information before they send another questionnaire.

How it helps

How Trust Centre works

This product connects with the wider Apollo platform, so information can support action, evidence and reporting without being entered again.

Feature 1

Publish from approved sources

Share policies, artefacts and assurance information already governed inside Apollo rather than maintaining another disconnected site.

  • Publish approved privacy resources
  • Share compliance information
  • Maintain subprocessor disclosures
Simplified illustrative publish approved assurance content workflow with fictional sample data

Feature 2

Control what visitors can see

Choose which sections are public and which documents or disclosures require an access request.

  • Set public and restricted content
  • Review access requests
  • Preview changes before publishing
Simplified illustrative control restricted access workflow with fictional sample data

Feature 3

Let prospects find answers themselves

Use an AI assistant grounded in approved Trust Centre content so prospects can ask follow-up questions without waiting for your team.

  • Answer from published knowledge
  • Show supporting sources
  • Keep unanswered questions visible for follow-up
Simplified illustrative answer from approved knowledge workflow with fictional sample data

What is included

One product, connected to the wider platform

Use the product you need now while keeping its records, work and evidence ready for related products across Apollo.

Included features

  • Branded assurance site
  • Privacy resources
  • Compliance disclosures
  • Subprocessor directory
  • Self-service knowledge assistant
  • Restricted access requests

Questions and answers

Questions about Trust Centre

Practical answers to common questions about managing this responsibility well.

How should organisations manage customer security assurance?

Publish approved security, privacy and compliance information through a branded customer-facing site. Give customers and partners a reliable place to find assurance information before they send another questionnaire.

What should a good process for customer security assurance include?

It should cover Branded assurance site, Privacy resources, Compliance disclosures, Subprocessor directory and Self-service knowledge assistant, with clear ownership, review and evidence rather than disconnected activity.

Who should be accountable for customer security assurance?

Ownership should sit with the person who can make decisions, allocate resources and keep the work current. A governance or specialist team may coordinate the process, but material records and actions need named accountable owners.

How often should customer security assurance be reviewed?

Use scheduled reviews based on risk and trigger an earlier reassessment after relevant incidents, regulatory change, audit findings or material changes to systems, suppliers or operating conditions.

What evidence should be retained for customer security assurance?

Retain the source information, owner, review and approval history, supporting documents and actions needed to explain what was known, what was decided and what happened next. Relevant records include trust centre publishing, artefact library, subprocessor directory and trust centre assistant.

See Trust Centre in Apollo

Book a focused demonstration and we will show how the product fits your current responsibilities, existing information and next practical priorities.