← Back to feed

Claude Fable 5 launched on June 9 with a condition that appeared in the fine print of every major distribution channel: Anthropic retains prompts and outputs for 30 days. The policy applies universally, including to enterprise customers who previously negotiated zero-data-retention (ZDR) agreements for Claude.

It is the first time a frontier model vendor has made safety-oriented data collection a non-negotiable precondition for accessing a general-release model. Anthropic says the retained data will not be used for training. It exists to detect novel jailbreaks and reduce false positives in Fable 5’s safety classifiers.

How It Works at Each Distribution Point

AWS Bedrock: Accessing Claude Fable 5 requires explicit opt-in via a new Data Retention API call, setting provider_data_sharing before invoking the model. Amazon’s documentation states this mode “allows Amazon Bedrock to retain and share your inference data with model providers per their requirements,” and that once enabled, data “will leave AWS’s data and security boundary.” There is no console toggle at launch — API only.

GitHub Copilot: Fable 5 is off by default for all Copilot Enterprise and Copilot Business plans. Organization administrators must explicitly enable a Fable 5 policy in Copilot settings. GitHub’s changelog notes: “Unlike other Claude models in GitHub Copilot, Claude Fable 5 requires data retention.” Claude Opus 4.8, Sonnet 4.5, and Haiku 4.5 continue to operate under ZDR.

Anthropic API direct: The requirement applies. All previously negotiated ZDR agreements are superseded for Fable 5 traffic.

The scope is deliberately forward-looking. AWS documentation states the retention requirement applies to “Fable 5, Mythos 5, and future models on Bedrock with similar or higher capability levels.” Anthropic has effectively created a policy class: the more capable the model, the more surveillance required to access it.

What Gets Retained and Why

Anthropic’s stated purpose is narrow: detect patterns of misuse across exchanges that would not be visible from a single turn, reduce false positives in the safety classifiers that route queries away from Fable 5 to Opus 4.8, and catch novel jailbreaks before they spread.

The 30-day retention window is then deleted. Anthropic commits explicitly that retained data is not used for training. The policy is positioned as a defensive security measure, not a product improvement loop.

Whether that commitment is technically enforceable at the contract level is a separate question from whether enterprises believe it. Healthcare, legal, and financial services companies routinely negotiate ZDR agreements precisely because prompt content carries regulated data — patient information, attorney-client communications, material non-public information. Under those terms, the choice is binary: do not use Fable 5, or accept that inference data leaves the AWS security boundary with a 30-day window before deletion.

The Compliance Trap

The policy creates an immediate problem for regulated industries. A hospital system that has a BAA (Business Associate Agreement) with AWS covering Claude Opus 4.8 under ZDR now faces a model upgrade that nullifies that agreement. Legal teams will need to determine whether a 30-day retention window, even for declared non-training purposes, constitutes a HIPAA-compliant arrangement — or whether it requires renegotiating data processing terms with Anthropic directly.

For financial services, the issue is slightly different: MNPI (material non-public information) can appear in prompts during M&A analysis workflows. If that data is retained by Anthropic for 30 days, even in a declared read-only abuse-detection capacity, legal risk teams will flag it as a disclosure concern.

Anthropic acknowledged the friction will be real. The company said it tuned the Fable 5 safety classifiers conservatively, meaning benign requests will occasionally trigger fallback to Opus 4.8. The retention policy is not a concession it made lightly — it is described in the launch announcement as a necessary condition for releasing a Mythos-class model to the general public at all.

The Broader Precedent

Before Fable 5, ZDR was a commercial feature AI vendors competed on. Enterprises with sensitive workloads could credibly choose a vendor based partly on data handling terms. The Fable 5 policy breaks that dynamic at the frontier tier.

If Anthropic holds this line and other frontier labs follow the logic — that sufficiently powerful models require safety monitoring to deploy — ZDR will become unavailable for the most capable models on the market. Enterprises that require it will be permanently capped below the capability frontier, using whichever sub-frontier models still offer it.

That is not a hypothetical. Claude Opus 4.8 still supports ZDR. But Opus 4.8 is no longer Anthropic’s best model. The new capability hierarchy runs Fable 5, then Mythos 5, then Opus 4.8. The retention requirement lives at the top.

Model	ZDR Available	SWE-Bench Pro
Claude Fable 5	No — 30-day retention required	80.3%
Claude Mythos 5	No — 30-day retention required	80.3% (no classifiers)
Claude Opus 4.8	Yes	69.2%
Claude Sonnet 4.6	Yes	~55%

The performance gap between Fable 5 and the last ZDR-compliant model is 11 points on SWE-Bench Pro — roughly the gap between capable and transformative on complex engineering tasks. That is the cost of keeping data in-boundary.