Subprocessors
Who else may process your data, and where.
Where ProjectX engages another party to help run ProjectX, that party is a subprocessor for the data placed with it. These are the categories we engage, the regions they may process in, and how to get the current named list.
Subprocessors
Categories of processing
| Category | Purpose | Regions |
|---|---|---|
| Infrastructure capacity | Compute, storage and network capacity where a region is served by a contracted provider rather than our own data centre. | The region you choose, among European, North American and Asia-Pacific regions. |
| Content delivery and DNS | Serving public endpoints and resolving names, for the parts of the service that are public by design. | Global edge, carrying no customer content — identifiers and requests only. |
| Email delivery | Sending transactional and notification email — sign-up confirmations, invoices, alerts you have asked for. | The region of your account, for the metadata required to deliver a message. |
| Model inference | Where you have enabled a feature that uses an external model provider; sovereign mode keeps inference in-region instead. | The region you choose, or in-region only under sovereign mode. |
Residency
Your data is placed in the region you choose, and strict residency confines it to one region — including from any subprocessor outside it. A subprocessor engaged for capacity in another region does not receive data from a tenant whose residency keeps it elsewhere.
The current list
The current named list of subprocessors is available on request, and we notify customers of a change before a new subprocessor begins processing — the same commitment the data processing addendum makes. Ask us for the list, or ask to be notified of changes, and we will add you.
A contact address is not configured for this site. The contact page carries the general channel, which reaches us too.