Plain words about what Cortesso stores, what it never does with it, what each model vendor sees when a position runs, and the terms you agree to. Last updated 8 September 2026.
When a position runs ("Run now"), Cortesso sends the position's rules, the brief, the memory and files it reads, and your question to the vendor's API with your key. That is the same as calling the vendor yourself. What the vendor may do with it is set by their API terms, which are different from the consumer chat apps:
| Engine | Data used for training? | Retention | Notes |
|---|---|---|---|
| Claude (Anthropic API) | No. Anthropic's commercial terms exclude API inputs and outputs from model training. | Short-term for abuse monitoring, per Anthropic's policy. | Web research uses Anthropic's search tool; your query goes to Anthropic's search provider. Billed by Anthropic per search on your key. |
| ChatGPT (OpenAI API) | No by default. OpenAI does not train on API data unless you opt in. | Up to 30 days for abuse monitoring, per OpenAI's policy. | The consumer ChatGPT app has different rules; a position running through Cortesso uses the API. |
| Grok (xAI API) | Check xAI's API data policy for your account tier; it has changed over time. | Per xAI's policy. | Live Search may send your query to X and the web. |
| Gemini (Google AI API) | Depends on your tier. On the free tier Google may use prompts to improve products; on the paid tier it does not. | Per Google's policy. | Cortesso asks you to confirm you are on the paid tier before it will run Gemini positions. |
These summaries are ours, written in good faith from the vendors' published terms at the date above. The vendors' own pages govern; links are in the dashboard next to each key. If a vendor changes its terms, we update this page and the dashboard notice.
Your account: an email address (as the account identifier, in clear), sign-in sessions, and the grants and connections you created. Your memory: facts, events, checkpoints, conversations you chose to save. Your team: positions, their rules, the board, the files you upload, the answers positions give. Numbers: how many calls, characters, tokens and dollars each position used, per day. Engine keys, sealed.
Where: Cloudflare's network (Workers, D1, R2), currently in US data centers. Mail for sign-in codes leaves through Cortesso's own mailbox. Nothing is stored anywhere else.
You. Positions you connected, within the scopes you granted, and only the projects they are members of. Cortesso's own systems, to run the service: the nightly consolidation pass reads your events to write facts, and support may look at metadata (never content) to fix a problem you report. Nobody else. We answer lawful requests only when legally compelled and tell you when the law allows.
This page is written by the Cortesso team in plain language and is not legal advice. Full terms of service, a privacy policy in the form regulators expect, and a data-processing agreement for business customers are being prepared with counsel; until then, this page is the agreement between us.