Feature 1
Publish a useful subprocessor directory
Maintain the provider context customers ask for and publish approved records directly to the Trust Centre.
- Describe the service
- Record data and location context
- Set public visibility
Capability
Subprocessor Directory
Maintain and publish the third parties involved in delivering your service, with the context customers need for assurance and privacy review.
The outcome
Give prospects and customers a current, transparent view of subprocessors without answering the same vendor questions repeatedly.
How it helps
How Subprocessor Directory works
This capability connects with the wider Apollo platform, so information can support action, evidence and reporting without being entered again.
Feature 2
Keep supplier disclosures current
Review changes centrally so customer-facing information reflects the organisation's current suppliers.
- Assign review dates
- Update provider status
- Publish approved changes
What is included
One capability, connected to the wider platform
Use the capability you need now while keeping its records, work and evidence ready for related capabilities across Apollo.
Included features
- Subprocessor records
- Service purpose
- Data and hosting context
- Public visibility
- Status and review dates
- Trust Centre publication
Connected platform
Keep exploring Apollo
See where this capability is available and the related capabilities and solutions that use the same connected information.
Trust Centre Publishing
Configure and publish a branded site for sharing approved security, privacy and compliance information.
Explore capabilitySupplier Register
Maintain the third parties the organisation relies on, their services, data context, ownership and review status.
Explore capabilityAvailable in:Trust Management
Questions and answers
Questions about Subprocessor Directory
Practical answers to common questions about managing this responsibility well.
Why does subprocessor directory matter?
Give prospects and customers a current, transparent view of subprocessors without answering the same vendor questions repeatedly.
What should subprocessor directory include?
It should cover subprocessor records, service purpose, data and hosting context, public visibility and status and review dates, with enough context to support action and explain decisions.
Who should be responsible for subprocessor directory?
Ownership should sit with the person who can make decisions and keep the information current. A specialist or governance team may provide the method, but accountability should not be left with an unnamed group.
How do you keep subprocessor directory current?
Set review dates according to risk and reassess after relevant incidents, material change, new evidence or overdue follow-up work. Preserve the history so changes remain explainable.
What evidence should be retained for subprocessor directory?
Keep the source information, owner, review and approval history, supporting documents and resulting actions needed to show what was considered and what happened next.
See Subprocessor Directory in Apollo
Book a focused demonstration and we will show how the capability fits your current responsibilities, existing information and next practical priorities.