Data processing agreement
What we do with your data, as a binding term.
Last updated 12 November 2026. This page forms part of the terms of service. Where you decide what happens to data and we act on your instructions, you are the controller and we are the processor, and these are the terms of that work. One set of terms applies everywhere; where two regimes differ we follow the stricter one.
Draft for review. The version that binds us is the one signed with you or named in your contract.
The subject matter
What is being processed, and why.
Our obligations
The nine things we are bound to.
For buyers in the United States
The four prohibitions, spelled out.
Where California law applies, we act as your service provider and we are prohibited from each of the following. We state them because the law requires them to be in the contract, and because they are good descriptions of what we do anyway.
- We do not sell or share your personal information.
- We do not retain, use or disclose it for any purpose other than the business purposes in our contract with you.
- We do not retain, use or disclose it outside our direct business relationship with you.
- We do not combine your personal information with personal information from any other client or from our own dealings with anyone. This is the one that matters most for how our agents learn, so here is exactly how it is kept: what pools across clients is the business function, the right answer and a reason code, and nothing else — no name, no words, no evidence, no numbers.
If a subprocessor of ours engages anyone else, we tell you, and they are bound by a contract carrying all the same terms.
You may check that we are keeping to this, by assessment, audit or technical testing, once in any twelve months.
Subprocessor list
Everyone who helps us run the service.
This is the whole list. It is derived from the code, not from memory: each row names what the service does and where in the system it is called.
| Who | What they do | What reaches them | Where |
|---|---|---|---|
| Our own server | Runs the app and the database | Everything described in the privacy policy | United Arab Emirates |
| Stripe | Takes payment | Your billing details and card data, which goes to them and never to us | Confirm |
| OpenRouter | Routes our requests to the AI models | The text of a question and the evidence it is answered from | Confirm |
| Anthropic | The model that answers, by default | The same text, with instructions to keep nothing and train on nothing | Confirm |
| Alibaba Cloud (Qwen) | First fallback model, used when the default is busy or refuses | The same text, same instruction | Confirm |
| DeepSeek | Second fallback model | The same text, same instruction | Confirm |
| Our mail host | Sends sign-in codes | Your email address and a six-digit code | United Arab Emirates |
Every model host above is sent an instruction with each call not to keep the text and not to train on it. That instruction is the default in our code, not a setting someone remembered to switch on.
Retention schedule
How long each thing lives.
If something goes wrong
Breaches, and who tells whom.
If personal data we hold for you is exposed, lost or reached by someone who should not have it, we tell you without undue delay — we do not assess whether it is serious first and we do not wait for a weekly report. You then decide what has to be told to a regulator or to the people affected, because that decision is the controller's, and we give you what you need to make it.
What we send you: what happened, when, which of your data is involved as far as we know it, what we have done to stop it, and what we think you should consider. In phases if we do not know everything at once, rather than a delay while we find out.
The full process, including the clocks that apply in each place, is on your rights and our breach process.
Said plainly, because you should not have to find it out: we have a route for an agent exceeding its limits — it stops itself, writes a record and tells your named person — and we are building the separate process for a personal-data breach. The commitment above is real and is kept by people today.
The rest