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 records that decide where your requests go.
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 note about the one company that learns from your text now says what is true under your own accounts: the switch is in your own account with that company, and Clint's connect steps show where. It used to describe a setting on an account of ours that your work no longer reaches.
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 learns from your text unless you switch it off. Our recorded position One company on the list above learns from what you send unless the account holder switches that off. Your work reaches that company only through your own account with it, so the switch is yours: in that company's own settings, under Privacy — the steps Clint gives you when you connect it show where. We never sign in to your accounts, so we cannot read that setting or change it for you, and until we can, the list keeps saying that company learns from your work. Look for the row that reads yes under learns from it. What would close it: Being able to read that setting from your own account, or that company changing its default. Either would let the list, the choice of where requests go and your receipts say no for your account, because they read the same record. Last checked September 29, 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 company that passes requests on, 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 records that decide where requests go 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. Companies that pass requests on are named as such: some of the services we use 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 path where nobody else is involved.
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 other documents
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.