Anthropic ZDR org, non-covered models zero data retention: terms and exceptions
ZDR 1.0 (s,f,r) · A
Short answer
No content retention. Safety carve-outs survive ZDR; stateful features step outside ZDR and are NOT blocked; classifier results retained.
Scope and evidence
| Provider | Anthropic |
|---|---|
| Service | ZDR org, non-covered models |
| Lane | ZDR |
| Origin |  US United States |
| License | proprietary |
| Hosting | Provider-hosted |
| Score | ZDR 1.0 (s,f,r) · A Contractual ZDR. Paper ZDR: no content retention by agreement, with typed carve-outs in force |
| Evidence | Contractual agreement reviewed (A: contractual (DPA/agreement-backed)) |
| Source-review date | 2026-08-24 (registry) |
Other lanes for Anthropic
Structured breakdown
- Default posture
- no content retention
- Exceptions and carve-outs
- safety carve-outs survive ZDR; stateful features step outside ZDR and are NOT blocked; classifier results retained
Approval and setup path
Approval and setup path not yet reviewed.
Flags on this record
- s
- safety-flag retention beyond base window
- f
- stateful-feature carve-outs (files, batch, threads, caching, grounding)
- r
- revocable: provider reserves unilateral downgrade
Practical questions for your agreement
- Does your signed agreement cover this exact service, model set, and feature path?
- Which retention, logging, and human-review exceptions still apply after any ZDR election?
- What configuration evidence (flags, project settings, store defaults) confirms the posture you expect?
- Do your customer commitments match what the reviewed evidence supports?
Does your agreement cover this deployment?
We can review the relevant terms, feature choices, and customer commitments, then help your team identify what to clarify or negotiate.
Sources
Trust and security
- Trust Center trust.anthropic.com
Posture ledger
seeded
ZDR 1.0 (s,f,r) · A
Seeded from published documentation.
Full key on the scale. Method notes on methodology. Notation is always ZDR 1.0 (s,f,r) · A.