Not by default. Anthropic's release notes for Claude Fable 5.2 (claude-fable-5-2), dated November 9, 2026, say the model requires 30-day data retention and is not available under zero data retention (ZDR) unless Anthropic expressly authorizes it. A team on a ZDR agreement has to pick a path first.
TL;DR: Claude Fable 5.2 requires 30-day data retention and is not available under zero data retention unless Anthropic expressly authorizes it. Anthropic's announcement says eligible customers can continue using it with ZDR, and describes Enterprise Frontier Safeguards as a monitoring option for stored prompts. The Covered Models article says ZDR is not available for Covered Models in Claude Enterprise organizations, and the Console workspace route appears only on the API retention page.
Key Takeaways
- The rule: Fable 5.2 and Mythos 5.2 require 30-day retention and are unavailable under ZDR without express authorization from Anthropic.
- The workspace route: The API and data retention page documents a Console option to enable 30-day retention for one workspace while others keep ZDR. The Claude Code ZDR docs do not mention it.
- The Enterprise limit: The Covered Models article says ZDR is not available for Covered Models in Claude Enterprise organizations.
- The exception: Anthropic's announcement says eligible customers can continue using Fable 5.2 with ZDR, and it names Enterprise Frontier Safeguards (EFS) in private beta.
- Claude Code behavior: Where an organization cannot use Fable 5.2, the Claude Code docs say it is absent from the
/modelpicker or disabled. - Your move: Decide per workload which data may sit in 30-day retention, then ask Anthropic about eligibility rather than assuming a route exists for Claude Code.
What do the Fable 5.2 release notes say about data retention?
The release notes say both new models require 30-day data retention and are not available under zero data retention unless expressly authorized by Anthropic. The entry says Fable 5.1 and Mythos 5.1 work the same way.
The API and data retention page calls these models Covered Models and repeats the rule. It adds that the requirement applies wherever Covered Models are offered.
Anthropic's Covered Models support article says prompts and model completions are retained for at least 30 days and then automatically deleted.
What can a team on a ZDR agreement do today?
The API and data retention page documents one route for the Claude API: enable 30-day retention for a specific workspace only. It states that organizations with a ZDR arrangement can make these models available in one workspace this way, and that other workspaces keep zero data retention. The page says the Default Workspace always follows the organization's setting, so that workspace must be a different one. In the Claude Console you select the workspace on the Data retention page, choose Standard data retention, and accept the terms.
That route is documented only on the API retention page. The Claude Code ZDR docs do not mention it, and the Covered Models article says ZDR is not available for Covered Models in Claude Enterprise organizations. I found no page saying a Claude Code team can use the Console workspace override, so confirm with Anthropic before planning around it.
A second option is to stay put. The Covered Models article says customers eligible for ZDR can continue to use prior Claude models under their existing settings and agreements.

What does Enterprise Frontier Safeguards change?
Anthropic's announcement says Enterprise Frontier Safeguards is in private beta with customers like Bridgewater, Salesforce, and Stripe. It describes EFS as automated safety monitoring run on prompts and responses stored in a customer's infrastructure, and says this makes it compatible with zero data retention.
The announcement also says eligible customers can continue using Claude Fable 5.2 and Claude Mythos 5.2 with zero data retention, and that for other customers Anthropic has 30-day retention for safety monitoring. Enterprise customers can request EFS access through their account team.
The Covered Models article adds a timing detail. It describes a temporary arrangement under which eligible customers can use ZDR with Fable 5.x for internal business applications. It says the arrangement is available for a limited time and intended as a transition to EFS, which rolls out in phases starting Fall 2026.
The pages I read do not state what makes a customer eligible, or an end date for the temporary arrangement.
How does Claude Code behave when ZDR blocks Fable 5.2?
The Claude Code zero data retention docs say Fable 5.2, Fable 5.1 and Fable 5 are Covered Models that require data retention by default. Whether a ZDR organization can use them is governed by the Covered Models policies.
Where your organization cannot use them, the docs say the models are absent from the /model picker or shown as disabled, and the server rejects requests for them. They also say Fable models are not the default and the best alias resolves to Opus.
Two more points from those docs affect a regulated rollout. ZDR is enabled per organization and applies only to requests that authenticate into that organization, so a developer on a personal account is not covered. Also, even with ZDR, Anthropic may retain inputs and outputs for up to 2 years if a session is flagged for a policy violation.

Which retention path fits which team?
The table sets out the three routes the pages describe.
| Path | What the pages state | Open question for your team |
|---|---|---|
| Stay on earlier models under ZDR | ZDR-eligible customers can continue to use prior models | Do you need Fable 5.2 for this workload? |
| Console workspace with 30-day retention (API retention page only) | Documented for the Claude API; other workspaces keep ZDR; not described in the Claude Code ZDR docs | Does this apply to your Claude Code setup at all? |
| Ask Anthropic about authorized ZDR or EFS | Announcement says eligible customers can continue with ZDR | What does eligibility require, and for how long? |
Frequently Asked Questions
Does Claude Fable 5.2 work with zero data retention?
Only if Anthropic expressly authorizes it. The release notes say both 5.2 models require 30-day data retention and are not available under ZDR otherwise. The announcement adds that eligible customers can continue using Fable 5.2 with zero data retention, without listing eligibility criteria.
Can I enable Fable 5.2 for one team without ending ZDR for my organization?
For the Claude API, the retention page says yes, at the workspace level: an organization with a ZDR arrangement can enable 30-day retention for a specific workspace only, and other workspaces keep zero data retention. The Claude Code ZDR docs do not describe this route, and the Covered Models article says ZDR is not available for Covered Models in Claude Enterprise organizations.
Will Claude Code switch me to Fable 5.2 automatically?
The Claude Code docs say Fable models are not the default and the best alias resolves to Opus. They also say that where an organization cannot use Fable models, the models are absent from the /model picker or shown as disabled.
Conclusion
Treat Claude Fable 5.2 as a retention decision before it is a model decision. Keep ZDR workloads on earlier models, and ask Anthropic in writing what authorization would require and whether the API workspace route applies to your Claude Code setup.
Learn from me

Claude Code in Practice, my Maven cohort. Master Claude Code from fundamentals to advanced orchestration: skills, subagents, hooks, MCP, and production automation. Join the next cohort →
Hire us
Traversaal.ai. We're a team of forward deployed engineers solving the toughest AI problems for Fortune 100 companies: document intelligence, agentic data platforms, and real-time web intelligence, deployed in production. Work with our team to deploy your next agentic ecosystem. Talk to Traversaal.ai →
Join us
Want to solve these problems with us? We're always looking for forward deployed engineers who want to ship production AI. jobs@traversaal.ai
