Fable 5, why retention is the new normal, and why data control starts today

Claude Fable 5 is out, and it deserves the attention it’s getting.

This is Anthropic’s first Mythos-class model, a tier above Opus. Not an incremental update but a genuine step up in capability: software engineering, analysis, knowledge work, vision. The most capable model you can get access to today.

And that capability is exactly why the fine print changed.

A model this strong can be misused in ways weaker models can’t. Some attacks only become visible across many requests: send hundreds of prompt variations and hope one slips through. You can’t catch that by looking at requests one at a time. So Anthropic now retains all Fable 5 traffic for 30 days to analyse patterns of misuse. On every platform: direct API, Bedrock, Google Cloud, Azure. Zero-retention agreements don’t apply to this model class. Anywhere.

I think Anthropic is being honest here, and that matters. Capability and safety analysis come as a package now.

Which means this is not an Anthropic story. Every provider shipping frontier models will face the same trade-off, and I expect they’ll land in the same place. Retention windows are becoming a structural part of using the best AI.

So the question changes. It’s no longer “which provider promises not to keep my data”. That promise is expiring. The question is: what do they receive in the first place?

That’s why we built Aimable the way we did. Sensitive data, names, client information gets filtered out before anything reaches the model. You keep a logbook of exactly what was sent. And work that should never leave your environment runs on an EU-hosted or local model instead, while your team works in the same environment either way. A 30-day window at the provider becomes a manageable risk instead of a blocker.

The best models will keep getting better. The terms will keep getting stricter. Controlling your data is no longer a compliance checkbox. From today, it’s the price of admission to the frontier.