SUB-PROCESSORS
Who can receive your work.
Every company that can receive anything of yours, generated live from the running service. Not a list somebody remembers to update — one that cannot go stale, because it is read from the same fleet the router reads.
How to read this
Drafted by the engineering team so that every factual statement traces to running code. Not reviewed by a qualified data-protection lawyer. Last checked September 13, 2026. Where we cannot yet make a commitment, the document says so, dates it, and names what would close it. We would rather you found the gap here than found it yourself.
What would change that: A review is commissioned when the first controller who is not us signs the processing agreement, or at the first paid business customer — whichever comes first. It is deferred rather than skipped: today there is no customer to make these statements to.
What changed in this version: The opt-out decision at one company is recorded: decided yes, not yet exercised, so the list still says that company trains on your work. The point about unnameable services is removed because it is settled — the one service nobody could name was dropped, and whether any remain is now read from the live list rather than asserted here.
A printed copy carries this version and its date, and leaves the navigation behind.
What we cannot yet commit to
These are listed rather than omitted. Each says which KIND of gap it is, when it was last checked, and what would close it — because “open” covered four different situations, and a limitation with no date on it is indistinguishable from one nobody has looked at.
- One company trains on your text, avoidably. Decided, not yet done One company on the list above trains on input and output subject to an account-level opt-out. We have decided to exercise it — it is free, it is reversible, and there is no argument on the other side — and it has not been exercised yet, because it lives behind a login in that company’s console. Until it is flipped and dated in our catalogue, the list keeps saying that company trains on your work, because a decision to opt out is not an opt-out. Look for the row that reads yes under learns from it. What would close it: The owner flipping the setting in that company’s console and dating it in our catalogue. The list, the router and your receipts then move together, because they read the same record. Last checked September 13, 2026.
When we last checked
Who is on this list is read from the running service the moment you open the page, so it cannot be out of date. What each company DOES with your work is a different kind of fact: somebody has to read that company's published terms and record them. The date below is the oldest of those readings, because the oldest one is what the whole list is worth.
The list
We could not read the live list as this page loaded, and we will not show you a remembered one — an out-of-date list here is worse than none, because you would act on it. Reload, or fetch /v1/sub-processors directly, which is the same document this table is made of.
Where we say not known
Not known is an honest answer and it is not a finished one, so each of them says which kind it is. For a router, no single answer exists — it picks the company that runs the model per request and does not tell us which — and not known is permanently the true answer. For a company we cannot name, it is a decision we owe you rather than reading we owe ourselves. For a named company, it means their terms are public and we have not read and recorded them yet, and we will not summarise terms we have not read.
How this list is made
It is derived, not typed. The model services come from the same live fleet the router reads and the same catalogue the receipt reads; whether a company keeps your text and whether it trains on it come from the same code that signs every answer's receipt. So this page and your receipts cannot disagree, which is the only version of this document worth publishing.
Three honest things most gateways do not publish. Not known is printed rather than hidden: a company whose terms we have not verified first-hand reads not known, and you can act on that where you cannot act on a comfortable guess. Routers are named as routers: some of our sources are themselves gateways that pick which company runs the model per request, and for those the final processor is genuinely undeterminable in advance. And your own machines are not on the list at all — hardware you own and operate is not a third party, and counting it would both inflate our footprint and misdescribe the one lane where nobody else is in the path.
Notice, and how to object
We could not read the notice period from the running service just now. The processing agreement states it.
If you object to a company on reasonable data-protection grounds, tell us and we will work to offer an alternative. If we cannot, you may end the affected part of the service and get back anything you prepaid for it. Under Article 28(2) that right only means something if you hear about a new sub-processor before it processes your data, which is what the notice period and the change feed are for.
Earlier versions
This page has no version history because it is not a version of anything: it is generated from the running service every time you open it. What it said on any past day is not something we kept, and we would rather say that than publish a version number we cannot evidence.
The rest of the shelf
Questions about any of this reach a real person at the contact page, with or without an account — [email protected] for anything about your own data, [email protected] for a security report. We answer within 10 working days.