The brief but turbulent launch of Anthropic's Claude Fable 5, the public release of its Mythos-class AI model, has triggered a wave of scrutiny over data retention practices and the near-total absence of identity infrastructure around frontier AI systems, exposing risks that enterprise leaders can no longer defer.
Related articles
Anthropic’s Mythos-Class Fable Shutdown Raises Questions About Sovereignty and AI Continuity in CX
Anthropic Releases Mythos-Class Claude Fable 5 as Enterprises Struggle to Govern AI Security Risk
Anthropic Exposes the Enterprise Patch Gap as Exploitation Hits “Minus Seven Days”, Red Hat Warns
Anthropic’s “Mythos-Class” Release Plans Should Put CX Leaders on Alert as Security Risks Accelerate
What Your AI Vendor Does With Your Data and Why Most Enterprises Haven't Asked
Under Anthropic's retention policy for Mythos-class models, every prompt submitted and output generated is held for 30 days for trust and safety purposes, on every platform where the models are offered. If an interaction is flagged by Anthropic's trust and safety classifiers as potentially violating its usage policy, that data can be retained for up to two years.
Anthropic removed both Fable 5 and Mythos 5 from use on June 12, less than a week after their release. But immediately after Anthropic released Claude Fable 5 on June 9, Microsoft reportedly told employees its legal teams were evaluating Anthropic's updated data retention requirements, effectively restricting internal use of the model while the review proceeded. The concern, according to reports, centered on customer data and confidential information flowing through the model's API.
The implications are significant for an organization the size of Microsoft. Employees routinely work with confidential product roadmaps, unreleased financial data and sensitive customer information. A blanket 30-day retention window, with the prospect of a two-year hold on flagged content, creates obvious tensions with internal data governance frameworks and client confidentiality obligations.
Ashish Nagar, Founder and CEO of customer experience AI company LevelAI, told CX Today that it’s a wake-up call for enterprises that have been treating public large language models like utility services. "Don't be dependent on a public LLM provider for critical AI resources—this stuff can be cut off anytime. The more data security and privacy risk an enterprise has, the more it needs its underlying AI to be personalized to its own use case."
Nagar argued that the real risk is structural.
"With public LLMs, there is very limited control over how data is being used, where it is being stored, and how it is being used for model training. That will become the gating factor for enterprise adoption."
Nagar suggested that enterprises should work with partners that have their own purpose-built models, or develop them internally, to avoid "runaway token costs" and opaque data practices.
"When you control your own destiny, you don't have a surprise bill of a few hundred million dollars without budgeting," Nagar added, likening using a general-purpose frontier model for a specific CX task to "taking a Boeing 747 from Mountain View to San Francisco Airport — you just need an Uber."