Anthropic Fable 5 / Mythos 5, all platforms zero data retention: terms and exceptions
ZDR 2.0 (s,h) · A
Short answer
Mandatory 30d retention incl. ZDR orgs; on Bedrock, sharing with Anthropic required. Flagged-content human-review path; defining example of flag r.
Scope and evidence
| Provider | Anthropic |
|---|---|
| Service | Fable 5 / Mythos 5, all platforms |
| Lane | Enterprise |
| Origin |  US United States |
| License | proprietary |
| Hosting | Provider-hosted |
| Score | ZDR 2.0 (s,h) · A Bounded retention. Content retained a defined window (<=90d) for abuse monitoring, possibly human-reviewed, then deleted |
| Evidence | Contractual agreement reviewed (A: contractual (DPA/agreement-backed)) |
| Source-review date | 2026-08-24 (registry) |
Other lanes for Anthropic
Structured breakdown
- Default posture
- mandatory 30d retention incl. ZDR orgs; on Bedrock, sharing with Anthropic required
- Exceptions and carve-outs
- flagged-content human-review path; defining example of flag r
Approval and setup path
none (customer-held-storage variant reportedly planned)
Flags on this record
- s
- safety-flag retention beyond base window
- h
- human review possible
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 2.0 (s,h) · A
Seeded from published documentation.
Full key on the scale. Method notes on methodology. Notation is always ZDR 1.0 (s,f,r) · A.