Zero Data Retention

What it is. Zero data retention locks your entire interaction into a memoryless pipe. The model receives your Figma exports, component specs, brand guidelines, unreleased product screenshots, and long agentic instructions, generates its response, then every byte vanishes. No disk write. No training queue. No 30 day compliance hold. For designers this is not abstract policy. When you hand an AI a full design system with proprietary interaction patterns or client color systems you need the data to die immediately after the handoff. Claude Fable 5 launched without this option. It ships as a Covered Model which bakes in a mandatory 30 day retention rule. That single line in the FAQ turned the highest scoring coding model on every benchmark into an instant non starter for any studio with real NDAs.

What it isn't. Zero data retention is not the same as a privacy checkbox on the enterprise plan. It is not the incognito chat that still writes temporary logs for safety classifiers. It is not negotiable fine print or a marketing promise that quietly expires after 90 days. On Fable 5 the retention policy is structural. Anthropic labeled it a Covered Model and the 30 day clock is not a bug they plan to fix. Zed teams and GitHub Copilot for Business users spotted it within hours of launch and immediately flagged it as a hard blocker. Those teams already standardized their pipelines on true ZDR so they could upload entire codebases without triggering legal review. Fable 5 broke that workflow the day it dropped.

Concrete example. In June 2026 a Berlin product studio won a redesign contract for a major automotive supplier. The brief required ingesting 180 Figma files, migrating an entire React Native design system, and producing accessible variants across 14 markets. They fired up Fable 5 for a test run because the SWE-Bench numbers looked unbeatable. Legal killed the project same afternoon. The supplier contract explicitly demanded zero data retention on every vendor tool. Fable 5 offered none. The studio rerouted the work to a self-hosted setup and shipped two weeks late but kept the client. The same month a New York packaging agency ran into identical trouble on a pharmaceutical brief. Their prompts contained HIPAA-adjacent UI copy and bottle diagrams. The Fable 5 FAQ page stating no zero-data-retention option ended the test before it started. They switched back to their GitHub Copilot for Business instance where ZDR had been toggled at org level since 2024. The Copilot run left zero trace. The Fable 5 run would have left a 30 day audit trail. These two projects became the exact stories that spread through every design Slack the week after launch.

When to use it. Use zero data retention the moment client IP or regulated data enters the workflow. Deploy it for full design system refactors where you upload every token, component, and usage rule. Use it for multi-hour agentic sessions that ingest entire repositories or Figma libraries containing next-season product strategy. Demand it from any tool when your studio signs contracts with banks, medical device makers, defense contractors, or consumer electronics brands that audit third-party data flows quarterly. GitHub Copilot for Business and certain Zed configurations gave teams this guarantee before Fable 5 launched. Those tools let designers work without lying to legal. The retention policy is the difference between using frontier models on real billable work and keeping them quarantined to mood boards.

When not to use it. Skip worrying about zero data retention on personal experiments, open-source component explorations, or internal training sessions on public datasets. Do not waste cycles demanding it from brand-new flagship models like Claude Fable 5 in the first weeks after launch. The policy is deliberate and immovable. Test the model on throwaway tasks, then route sensitive design handoff work to tools that actually support ZDR. Many studios now run parallel setups: one locked-down ZDR stack for client projects and one wide-open stack for pushing the limits on personal or R&D work. That split became standard operating procedure the day Fable 5's retention rules hit the FAQ.

Zero data retention is table stakes for any design team that wants to use frontier models on client work instead of just tweeting about them.