Enterprise customers who built their Claude deployments around strict data governance received significant news alongside the Fable 5 launch on June 9. Effective immediately, Anthropic requires a 30-day retention window on all traffic processed by Claude Fable 5, Claude Mythos 5, and any future model with comparable capabilities. The requirement overrides zero-data-retention (ZDR) agreements that organizations had previously negotiated across the Claude API, AWS Bedrock, Google Cloud Agent Platform, and Microsoft Foundry.
For the vast majority of Claude users, the change is invisible. ZDR arrangements have always been an enterprise option, not the default, and standard subscription users were never in scope. But for regulated industries that made ZDR a baseline requirement before deploying Claude, the launch of Fable 5 demands a fresh compliance review before any production use of the new model.
Who Is Affected
The policy applies to three categories of customer. Organizations that configured ZDR workspaces in Claude Console are affected. So are teams using Claude Code with ZDR enabled in a Claude Enterprise account. The third group is the largest: any organization accessing Claude through AWS Bedrock, Google Cloud Agent Platform, or Microsoft Foundry with a ZDR agreement in place.
That last category covers a broad range of enterprise deployments. Many large organizations chose to route their Claude usage through cloud providers specifically because those providers offered contractual data-handling guarantees that matched internal compliance requirements. The Fable 5 launch creates a gap: the model is available on these platforms from day one, but the ZDR protections that governed prior models no longer apply when Fable 5 or Mythos 5 is in use.
Key Facts
- Retention window30 days for all Fable 5 and Mythos 5 traffic
- Affected customersZDR users on Claude API, AWS Bedrock, GCP, Microsoft Foundry
- Data useSafety investigations only, never for model training
- Auto-deletionAfter 30 days (except active safety/legal holds)
- ScopeApplies to all future Mythos-class models
- Free-access period endsJune 22, 2026
What Anthropic Says the Data Is For
Anthropic is explicit that the retained data will not be used to train new models and will not be applied to any commercial purpose. The stated use cases are narrow: defending against complex and novel attacks including new jailbreak techniques, and identifying cases where Fable 5's safety fallbacks incorrectly block legitimate queries. After 30 days, the data is deleted automatically. The exceptions are active safety investigations and any situation where a legal hold applies.
The reasoning is connected to the nature of Mythos-class models. These systems were developed in part through capability research that surfaced serious security vulnerabilities. Anthropic's position is that maintaining visibility into how the model is being used is a prerequisite for keeping advanced capabilities in general circulation. A model that can execute sophisticated multi-step tasks across large codebases, as the Stripe migration case shows, creates an attack surface that past models did not have. The 30-day window gives Anthropic the ability to study novel attack patterns as they emerge in real usage, rather than after the fact.
"We will require 30-day retention for all traffic on Mythos-class models, on both first- and third-party surfaces, and won't use this data to train new Claude models, or for any non-safety-related purpose." Anthropic, data retention policy for Mythos-class models, June 9, 2026
The Compliance Implications
Healthcare organizations, financial firms, and legal teams have been the most consistent users of ZDR arrangements. Their compliance programs often specify that sensitive information processed by AI tools must not be retained by any third party. A 30-day retention window, even one limited to safety purposes and subject to automatic deletion, may require review by legal, security, and procurement teams before the organization can use Fable 5 in production. That review cycle is typically not fast.
The GitHub Copilot integration makes this concrete. Claude Fable 5 is now generally available in GitHub Copilot, and the data retention requirement applies there as well. Developers using Copilot at organizations with blanket data-retention prohibitions may find that Fable 5 is technically available but effectively off-limits until their organization completes a compliance assessment.
The policy also sets a precedent that goes beyond this single model. Anthropic has stated the retention requirement will apply to "Mythos-class models and future models with similar or higher capability levels." That language suggests organizations should not expect ZDR to return as a standard option for Anthropic's most capable models. Enterprise teams building workflows around Anthropic's infrastructure will want to factor mandatory retention into long-term planning for any deployment involving frontier-class models.
What to Do Before June 23
The free-access period for Fable 5 on Pro, Max, Team, and seat-based Enterprise plans ends June 22. After that date, using the model requires usage credits. For enterprise compliance teams, the period between now and June 22 is a window to complete a preliminary assessment before any decision to purchase credits for production use.
The practical steps are straightforward: identify which Claude deployments are governed by ZDR agreements, confirm whether those agreements cover third-party cloud providers, and determine whether the 30-day retention window is compatible with existing data governance policies. Anthropic has not published detailed regional data maps tied to the retention policy, which means organizations with data-residency requirements will also need to confirm storage geography separately.
The change does not affect standard Claude Pro, Claude Max, or Claude Team subscriptions that were never configured with ZDR. For those users, Fable 5 works exactly like any prior model and carries no new data-handling obligations.
