Subprocessors and service providers
A useful subprocessor page identifies the provider, purpose, data involved, processing location and change-notification process. It must match the technologies actually used for the relevant service.
Current review version
This review version does not send public enquiries or newsletter subscriptions to external providers. It is not evidence of an active production data flow, and no complete production subprocessor inventory is asserted here.
Provider use must be verified
Hosting, email, enquiry handling, booking, analytics, advertising, chat and monitoring each need an accurate inventory. Existing service identifiers and proposed integrations must be checked against the final configuration; a planned integration is not an active service.
Before production
Inventory hosting, email, CRM, analytics, support, automation and other providers; reconcile contracts and real data flows; then obtain legal review.
Change management
Define how clients are notified of a material processor change and where objections or questions should be directed.
Questions this page answers
Why is there no named list yet?
A generic list would be misleading. The production architecture and actual client-processing services must be verified first.
Are software vendors always subprocessors?
No. The role depends on whether and how personal data is processed for the service. Assess the actual use.
Will this page replace a DPA?
No. A public inventory can support transparency, while binding obligations belong in the appropriate agreement.