Sub-processors
01Current sub-processors
[THIS LIST MUST BE COMPLETED FROM THE ACTUAL VENDOR REGISTER BEFORE PUBLISHING — nothing is pre-filled here on purpose, because an invented sub-processor list is a false contractual representation, not a placeholder]
| Sub-processor | Purpose | Data processed | Location |
|---|---|---|---|
| [cloud hosting provider] | Platform hosting and storage | All customer data | [regions] |
| [email / notification provider] | Transactional email | Name, email address | [region] |
| [support desk provider] | Customer support tickets | Contact details, ticket content | [region] |
| [analytics provider, if any] | Website analytics | Technical data | [region] |
02How we manage them
- Every sub-processor is assessed before onboarding and reassessed [reassessment cadence]. We use our own TPRM module to do it.
- Each is bound by a written contract with data protection terms at least as protective as our own.
- We remain responsible to you for their performance.
03Notice of changes
We will post new sub-processors here [notice period, e.g. 30 days] before they begin processing customer data. To be notified by email, write to [email protected]. Customers may object on reasonable data protection grounds under the process in their DPA.