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.

Mistral ZDR approved zero data retention: terms and exceptions

Q: What is the ZDR score for Mistral ZDR approved?

On zdr.dev the published score is ZDR 1.0 (f) · B. Default 30d rolling abuse logs; EU storage. Stateless endpoints only; agents/batch/files excluded; Labs models train regardless.

ZDR 1.0 (f) · B

Short answer

Default 30d rolling abuse logs; EU storage. Stateless endpoints only; agents/batch/files excluded; Labs models train regardless.

Scope and evidence

Provider	Mistral
Service	ZDR approved
Lane	ZDR
Origin	FR France
License	open-weight
Hosting	Self-host
Score	ZDR 1.0 (f) · B Contractual ZDR. Paper ZDR: no content retention by agreement, with typed carve-outs in force
Evidence	Public documentation reviewed (B: published documentation)
Source-review date	2026-08-24 (registry)

Other lanes for Mistral

ZDR 1.0 (f) · Bmistral/api · zdr approvedZDR

ZDR 2.0 (f) · Bmistral/api · defaultAPI default

Structured breakdown

Default posture: default 30d rolling abuse logs; EU storage
Exceptions and carve-outs: stateless endpoints only; agents/batch/files excluded; Labs models train regardless

Approval and setup path

application: paid plans, stated justification, discretionary approval

Flags on this record

f: stateful-feature carve-outs (files, batch, threads, caching, grounding)

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?