Privacy decision · checked September 3, 2026

Claude Fable 5.1 Retention and ZDR for Legal Teams

Anthropic’s commercial no-training promise and its Covered Models retention rule answer different questions. A legal team must record both before it sends approved matter material to Fable 5.1.

Direct answer

Do not describe Fable 5.1 as zero retention by default. Anthropic says the Covered Models rule retains prompts and outputs for 30 days across named platforms, while some eligible organizations may receive an express ZDR exception. Verify the executed order form, platform and written eligibility before matter use.

Decision matrix separating commercial no-training terms, covered-model retention and eligible ZDR exceptions
Review frame. The executed route decides which retention rule applies.

Training and retention are separate questions

FieldPublic source saysProcurement record
Model trainingAnthropic’s commercial terms say it may not train models on customer content from the services.Confirm the commercial service, feedback settings and operative agreement.
Covered-model retentionPrompts and outputs for designated Covered Models are retained for 30 days to support safety work.Name the model, platform, start date and stated exceptions.
Human accessAnthropic describes a controlled path after automated flags, limited reviewers and recorded access.Ask which audit evidence the customer can receive.
DeletionAnthropic says retained data is deleted after 30 days except when flagged or legally required.Record exception handling rather than promising unconditional deletion.

Who the Covered Models update affects

Anthropic says the change applies to organizations that previously used ZDR through Claude Console workspaces, Claude Code Enterprise or named cloud platforms and did not receive eligibility notice for continued ZDR. Consumer plans were already subject to their own retention practices. That scope makes account and platform identification part of the legal answer.

ZDR requires evidence, not an assumption

An eligible exception should be treated as a configuration and contract fact. Retain the provider notice, organization or project identifier, applicable platform, covered model, effective date and any safeguard conditions. A sales statement or an unrelated workspace screenshot is not enough to establish the exception for the production route.

A pre-matter decision record

  1. Name the workflow and permitted data class.
  2. Record the product surface, account, model ID and hosting route.
  3. Attach the executed agreement, order form and current retention notice.
  4. State whether the 30-day rule or an approved exception applies.
  5. Record who may review flagged content and what audit evidence exists.
  6. Define the output destination, human reviewer and incident owner.

What the public pages do not decide

They do not establish privilege treatment, compliance with a particular professional rule, client consent, data residency for every route or the terms of a negotiated enterprise order. Those fields remain Unknown until the firm reviews its own documents and configuration.

FAQ

Does Anthropic train Fable 5.1 on commercial customer content?

Anthropic’s public commercial terms say it may not train models on customer content from the services. Confirm that those terms govern the exact account and route.

Is Fable 5.1 zero data retention?

Not by default under Anthropic’s Covered Models guidance. Some eligible organizations may receive an exception, which should be verified in writing for the exact platform and project.

Does no training mean no retention?

No. Training use and operational or safety retention are separate data-handling fields.

Sources checked

Operational information, not legal advice. Verify current terms, account configuration and applicable professional duties before use.