| What it is | A policy label. OpenRouter: ZDR “means no routine storage of prompts or responses after processing”; every endpoint carries one of three tiers — ZDR, Safety Retention, or Retention and Training (docs). | Signed evidence: a hardware report of the TEE and a measurement of the software that started inside it, checked against the hardware vendor’s root of trust. |
|---|
| Who you trust | The operator and every provider on the route to uphold the policy. OpenRouter “works with providers to understand each of their data policies” and, when it cannot ascertain a policy, assumes the endpoint retains and trains (docs). | The hardware vendor’s root of trust and the measured software. Unless the route is bound to the request, you still trust the operator to send your request to that machine at all. |
|---|
| Can you check it yourself? | Not directly. In November 2026 it was outside researchers, not customers, who reported policies not being upheld (OpenRouter,Dragos). Dragos advises seeding your own canaries. | Yes: the quote can be verified against the vendor root of trust (methodology). A valid quote still does not prove the code is bug-free, or that your request reached that machine unless the route is bound. |
|---|
| Covers tools/plugins? | No. OpenRouter’s ZDR enforcement covers provider routing for inference only, not plugins/tools such as web search (docs). | Covers the measured TEE workload. Hops outside the enclave — a gateway, a tool call — are not covered by its signature (TLS vs E2EE). |
|---|
| Survives a breach of the operator’s storage? | Only if no copy exists. In 2026, stored prompt samples were downloaded at Together AI (notice), and Notion says a stored Fireworks dataset held Notion AI chat transcripts (incident). | On an attested E2EE route the client encrypts to a key proven to belong to the TEE, so the operator’s storage holds the encrypted payload, not the prompt. |
|---|
| What still leaks | Anything the operator or its subprocessors keep or forward. Resellers were observed viewing and retaining prompts through standard logging (Dragos); a Novita configuration issue forwarded requests for over five months (Novita). | Bugs in the software inside the TEE — a TEE protects code from the host, it does not make the code correct (seethe near-sglang RCE incident). Metadata such as IP address, timing, and traffic size also stays visible. |
|---|