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.

DeepSeek first-party API zero data retention: terms and exceptions

Q: What is the ZDR score for DeepSeek first-party API?

On zdr.dev the published score is ZDR 4.0 · B. Trains on inputs by default (email opt-out); retention up to life of account; PRC storage; group sharing. US hosts serving DeepSeek weights are different endpoints with different scores.

ZDR 4.0 · B

Short answer

Trains on inputs by default (email opt-out); retention up to life of account; PRC storage; group sharing. US hosts serving DeepSeek weights are different endpoints with different scores.

Scope and evidence

Provider	DeepSeek
Service	first-party API
Lane	API default
Origin	CN China
License	open-weight
Hosting	Self-host
Score	ZDR 4.0 · B Open intake. Trains on content by default, or retention undefined/indefinite
Evidence	Public documentation reviewed (B: published documentation)
Source-review date	2026-08-24 (registry)

Other lanes for DeepSeek

ZDR 4.0 · Bdeepseek/api · first-partyAPI default

Structured breakdown

Default posture: trains on inputs by default (email opt-out); retention up to life of account; PRC storage; group sharing
Exceptions and carve-outs: US hosts serving DeepSeek weights are different endpoints with different scores

Approval and setup path

Approval and setup path not yet reviewed.

Flags on this record

No exception flags on this record.

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?