The label vs the signed route

The left column is the ZDR label as OpenRouter documents it; the right column is an attested TEE route as this directory defines it in theFAQ andmethodology. Rows compare like with like.

AspectZDR labelAttested TEE route
What it isA 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 trustThe 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 leaksAnything 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.

What happened in November 2026

Each item is summarized from its linked primary source; several also have entries in this directory’s incident log.

  • OpenRouter, Nov 22. Researchers reported providers whose data policies were not upheld. OpenRouter off-boarded three providers, removed 125 endpoints from ZDR eligibility, and notified affected customers; it says it is adapting the researchers’ testing and verifying network paths for forwarding to third parties.Announcement
  • Novita, Nov 22. A routing configuration issue forwarded some MiniMax requests to MiniMax’s official API between May 28 and November 11, 2026 — including requests routed to Novita through OpenRouter.Notice
  • Dragos (HD Moore), Nov 19. About two million prompts with unique URLs and canary credentials were sent to AI services between July and November 2026. The report presents evidence of provider compromises, resellers viewing and retaining prompts through standard logging, and providers not honoring privacy settings. Its advice includes picking upstream providers yourself on routers and seeding your own canaries. Report
  • Together AI, Nov 21. Stored prompt samples were downloaded after a credential leaked. Together then made ZDR the default for new accounts.Post-mortem
  • Fireworks/Notion; Tinfoil, Nov 16. Fireworks advertises ZDR by default for inference; Notion says a stored Fireworks dataset held Notion AI chat transcripts (incident entry). Tinfoil’s post compares ZDR terms of 12 providers and notes carve-outs for batch, caches, and tools. Tinfoil
  • Phala, Nov 10. Phala says DeepSeek V4 Flash 0731 requests that OpenRouter routed to it between October 21 and November 8 should be treated as exposed (incident entry).

Through a router

A router that terminates TLS sees the plaintext prompt; that is what terminating means. OpenRouter’s own documentation describes processing prompts in flight: it screens inference requests, including ZDR traffic, for CSAM, and it does not store prompts unless you opt in or content is flagged, but it does sample a small number of prompts for anonymous categorization (data collection docs). Screening and sampling both happen in plaintext at the router.

Attested routes only help through a router if the client encrypts the payload to the enclave key, or the router itself runs an attested workload. The enclave’s attestation alone says nothing about a hop in front of it. SeeTLS vs E2EE for the topologies and theRoute Explorer for which tracked routes cross another organization, including the router FAQ entry.

How to check

  • Read each provider’s verification panel on this directory (provider pages, #verify section) for the checks this monitor runs against them.
  • Inspect current hardware, channel, workload and route evidence in theattestation monitor, and how verdicts are produced in themethodology.
  • For retention promises, follow Dragos’s advice and seed your own canary prompts (report); a label cannot be checked from the outside.

Short answers

Is ZDR enough?

ZDR is a retention policy, not a technical control. OpenRouter defines it as no routine storage of prompts or responses after processing, and its enforcement covers provider routing for inference only, not plugins or tools. The policy also has to be upheld: in November 2026 researchers reported providers whose data policies were not upheld, and stored prompt data surfaced at Together AI and Fireworks.

Can a router see my prompt?

Yes, if your connection is decrypted at the router. OpenRouter documents that it screens inference requests, including ZDR traffic, in flight, and samples a small number of prompts for anonymous categorization. An enclave attestation says nothing about that hop unless the payload is encrypted to the enclave key, or the router itself runs an attested workload.

Can I verify ZDR?

Not directly. As a customer you rely on the operator to enforce the label. In November 2026 it was outside researchers who reported providers not upholding their policies, and OpenRouter says it is adapting their testing; Dragos advises seeding your own canary prompts. Attestation, by contrast, produces a signed hardware report you can check yourself against the hardware vendor root of trust.