What is zero data retention (ZDR)?

Zero data retention (ZDR) is the claim that an AI endpoint does not keep the prompt, the completion, or other residue of a request after the call finishes.

Anthropic first-party API, default zero data retention: terms and exceptions

Q: What is the ZDR score for Anthropic first-party API, default?

On zdr.dev the published score is ZDR 2.0 (s) · B. 30d auto-delete; no training without permission. Flagged content <=2y; classifier scores <=7y.

ZDR 2.0 (s) · B

Short answer

30d auto-delete; no training without permission. Flagged content <=2y; classifier scores <=7y.

Scope and evidence

Provider	Anthropic
Service	first-party API, default
Lane	API default
Origin	US United States
License	proprietary
Hosting	Provider-hosted
Score	ZDR 2.0 (s) · B Bounded retention. Content retained a defined window (<=90d) for abuse monitoring, possibly human-reviewed, then deleted
Evidence	Public documentation reviewed (B: published documentation)
Source-review date	2026-08-24 (registry)

Other lanes for Anthropic

ZDR 1.0 (s,f,r) · Aanthropic/api · zdr org, non-coveredZDR

ZDR 2.0 (s,h) · Aanthropic/claude-fable-5 · all platformsEnterprise

ZDR 2.0 (s) · Banthropic/api · defaultAPI default

Structured breakdown

Default posture: 30d auto-delete; no training without permission
Exceptions and carve-outs: flagged content <=2y; classifier scores <=7y

Approval and setup path

contractual, via sales, per-organization

Flags on this record

s: safety-flag retention beyond base window

Practical questions for your agreement

Does your signed agreement cover this exact service, model set, and feature path?
Which retention, logging, and human-review exceptions still apply after any ZDR election?
What configuration evidence (flags, project settings, store defaults) confirms the posture you expect?
Do your customer commitments match what the reviewed evidence supports?