The short version: no request text is stored. The long version, with the test that keeps each line, is the file TRUST.md in the source; the privacy page says it for a reader who is not a developer.
Text
- A check reads the text, answers and forgets it. No database, cache, log or trace holds it. The usage record holds ids, counts and buckets.
- Text the rules answer never leaves Cloudflare. In balanced mode, the default, that is only the text they block outright: every other text goes to the model, which on mostly clean traffic is nearly every check.
mode: "fast"keeps a request on the rules; an Edge-only project keeps every check on the rules by never constructing the model client. - Text sent to the model carries the questions and nothing about the sender. Who processes it, and what they retain, is on the subprocessors page.
- The model’s numeric answers are cached for seven days under a SHA-256 of the text with the engine version. The key is a hash, the value is numbers.
- Feedback stores
textonly when you send it, and deletes it with your account.
Keys and sessions
- Only the SHA-256 of a key is stored, with its prefix and last four characters. A key is shown once.
- Sign-in links work once, for fifteen minutes, and are stored as hashes. Sessions are signed cookies, thirty days, revocable.
- Rate limits and abuse counters key on an hourly-rotating pseudonym of the address, never the address.
Operations
- Invocation logs and traces are switched off on both services; the deploy step refuses to run while they are on. The AI gateway the model calls pass through has logging and caching off, and the deploy step reads that setting too.
- Deleting an account removes everything under it within 24 hours. Nightly backups are kept for 30 days and then deleted.
Answering your users
“Is my message stored?” No. “Was it sent to an AI?” Only if the rules could not settle it, and never on an Edge-only project. “Who can see it?” Nobody: it is not kept.