Short answer. Five of the twenty providers here publish a standalone subprocessor list: OpenAI, Anthropic, Google Cloud, AWS and Microsoft. Six more point to a DPA or disclose on request. Nine disclose nothing we could verify, which does not mean they use no subprocessors — it means procurement has to ask. This tracker records where to look, what is disclosed, and what procurement should ask.
Baseline: 20 November 2026. “Not verified” is a finding, not an accusation. We link the page we checked; if a provider publishes a list elsewhere, the row will be corrected with the new date.
How to use the tracker
Start with the DPA, not the privacy policy. The privacy policy tells you what the provider says publicly; the DPA is the document that binds it. A subprocessor clause normally has four parts: the list, the notice period before a change, the right to object, and the consequence if you object. A list without a notice clause is a snapshot, not a control.
The 20 providers
| Provider | Where to look | Subprocessor disclosure | Primary hosting | Last checked |
|---|---|---|---|---|
| OpenAI | openai.com/policies | Standalone list linked from the policies page | US; regional endpoints | 20 November 2026 |
| Anthropic | anthropic.com/subprocessors | Standalone list | US | 20 November 2026 |
| Google Cloud | cloud.google.com/terms/subprocessors | Standalone list | Multi-region | 20 November 2026 |
| Amazon Web Services | aws.amazon.com/compliance/sub-processors | Standalone list | Multi-region | 20 November 2026 |
| Microsoft | microsoft.com/trust-center | Standalone list in the trust centre | Multi-region | 20 November 2026 |
| Mistral | mistral.ai/terms | Referenced in the terms and DPA | EU | 20 November 2026 |
| Cohere | cohere.com/legal | Referenced in the DPA | US, EU | 20 November 2026 |
| Groq | groq.com/legal | Referenced in the DPA | US | 20 November 2026 |
| Together AI | together.ai/legal | Referenced in the DPA | US | 20 November 2026 |
| Fireworks AI | fireworks.ai/legal | Referenced in the DPA | US | 20 November 2026 |
| OpenRouter | openrouter.ai/privacy | Not verified | Global routing | 20 November 2026 |
| Replicate | replicate.com/legal | Not verified | US | 20 November 2026 |
| Hugging Face | huggingface.co/privacy | Not verified | US, EU | 20 November 2026 |
| Perplexity | perplexity.ai/legal | Not verified | US | 20 November 2026 |
| xAI | x.ai/legal | Not verified | US | 20 November 2026 |
| AI21 | ai21.com/legal | Not verified | US | 20 November 2026 |
| DeepInfra | deepinfra.com/terms | Not verified | US | 20 November 2026 |
| DeepSeek | deepseek.com | Not verified | China | 20 November 2026 |
| Alibaba Cloud | alibabacloud.com/help/en/legal | Not verified | China, Singapore | 20 November 2026 |
| Plugsky | plugsky.com/legal/privacy | On request from the DPA | Deployment-dependent | 20 November 2026 |
What counts as a subprocessor
A subprocessor is a third party that processes personal data on the provider’s behalf. Cloud hosting, logging, support tooling, payment and email delivery usually qualify. A model developer that supplies weights but never sees the data usually does not. The distinction matters because the list can be long, and the entries that matter are the ones that can read your prompts.
| Third party | Usually a subprocessor? | Why it matters |
|---|---|---|
| Cloud infrastructure | Yes | Determines where data is stored and processed |
| Observability and logging | Yes | Can capture prompt and completion content |
| Support desk | Often | Support staff may read ticket attachments |
| Payment processor | Yes, for billing data | Rarely sees prompts; still in scope |
| Model weight supplier | Usually no | No data access; supply relationship, not processing |
| CDN and WAF | Yes | Sees metadata and sometimes request bodies |
Notice and objection terms
Notice periods vary by contract; 30 days is common in enterprise DPAs, but the number that matters is the one in yours. The practical question is what happens when you object. Three patterns appear in AI DPAs: the provider will not change the subprocessor and you may terminate; the provider will try to accommodate and you may terminate if it cannot; or the provider has no objection right at all. The first is workable, the second is negotiable, the third is a risk to price in.
Two clauses deserve a close read. “Affiliates” can widen the list without notice. “Replacement of a subprocessor with an equivalent” can remove the notice requirement entirely, because the provider decides what equivalent means. Ask for the list to be incorporated as an annex and for changes to require notice, not just publication.
Four questions for procurement
- Where is the current list? Ask for the annex, not the URL. A URL can change after signature.
- How much notice, and how is it delivered? Email to a named contact is better than a trust-centre update you have to poll.
- What is the objection right, and what happens if we object? “We will discuss” is not a right.
- Which subprocessors can read prompt content? Hosting and logging are the two that usually can. The rest are often metadata-only.
If the provider cannot answer the fourth question, ask for a data-flow diagram instead. It is faster than a legal exchange and usually reveals the same thing.
Methodology and limits
- Source. The provider’s legal or trust page, checked on 20 November 2026. We record what is published, not what a sales deck says.
- Disclosure type. “Standalone list” means a page dedicated to subprocessors. “Referenced in the DPA” means the list exists but is inside another document. “Not verified” means we did not find a public list.
- Notice. The period stated in the DPA or terms. Where the document does not state one, the cell says so instead of assuming 30 days.
- Scope. The table covers the provider’s hosted API, not every product it sells. An enterprise deployment may have a different list.
The limit is the same as every procurement tracker: a public page is not the contract. Use the table to find the document, then read the document. If a row is out of date, send the current link and it will be corrected with a dated note.
Sources
Links checked 20 November 2026. We cite the primary page for each figure. Where a provider publishes a price behind a login, we say so and do not guess.
- Anthropic subprocessors — the published list used for the Anthropic row
- Google Cloud subprocessors — the published list and change mechanism
- AWS subprocessors — the published list and notice terms
FAQ
Which AI providers publish a subprocessor list?
OpenAI, Anthropic, Google Cloud, AWS and Microsoft publish standalone lists that we could verify on 20 November 2026. Mistral, Cohere, Groq, Together and Fireworks reference subprocessors inside their terms or DPA. Others disclose on request or in a contract annex.
What is a subprocessor in an AI API?
A third party that processes personal data on the provider’s behalf. Cloud hosting, logging, support tooling and payment usually qualify. A model weight supplier that never sees customer data usually does not.
How much notice should a subprocessor change give?
Thirty days is common, but the notice period matters less than the objection right. Ask what happens if you object: a termination right is a control, a promise to discuss is not.
Does a privacy policy list subprocessors?
Rarely in full. The binding list is normally an annex to the DPA or a page the DPA incorporates by reference. A privacy policy is a public summary, not the contractual list.
Why do some rows say “not verified”?
Because no public list was found on the page we checked. It does not mean the provider uses no subprocessors. It means the answer is in the contract, and the tracker records that rather than guessing.
How often is the tracker updated?
Monthly and when a provider changes its list. Each row carries the date checked, and corrections are dated rather than silently overwritten.
Use the data, then test it on your own workload
Plugsky publishes its plan caps and model limits. Start free with no card, or compare the flat plans against per-token billing.
Start Free → See plans