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.

Moonshot Kimi API, first-party zero data retention: terms and exceptions

Q: What is the ZDR score for Moonshot Kimi API, first-party?

On zdr.dev the published score is ZDR 4.0 (f) · B. OpenPlatform privacy: user content is used to train and refine models, and account, input, and payment information are retained while the account is active. API help page separately claims API data is not used for training. Storage stated as Singapore. Help Center contradicts the privacy policy on training. Files persist until deleted. Content safety review exists. Mainland moonshot.cn not scored separately.

ZDR 4.0 (f) · B

Short answer

OpenPlatform privacy: user content is used to train and refine models, and account, input, and payment information are retained while the account is active. API help page separately claims API data is not used for training. Storage stated as Singapore. Help Center contradicts the privacy policy on training. Files persist until deleted. Content safety review exists. Mainland moonshot.cn not scored separately.

Scope and evidence

Provider	Moonshot
Service	Kimi API, first-party
Lane	API default
Origin	CN China
License	proprietary
Hosting	Provider-hosted
Score	ZDR 4.0 (f) · B Open intake. Trains on content by default, or retention undefined/indefinite
Evidence	Public documentation reviewed (B: published documentation)
Source-review date	2026-08-25

Other lanes for Moonshot

ZDR 4.0 (f) · Bmoonshot/kimi-api · first-partyAPI default

Structured breakdown

Default posture: OpenPlatform privacy: user content is used to train and refine models, and account, input, and payment information are retained while the account is active. API help page separately claims API data is not used for training. Storage stated as Singapore.
Exceptions and carve-outs: Help Center contradicts the privacy policy on training. Files persist until deleted. Content safety review exists. Mainland moonshot.cn not scored separately.

Approval and setup path

none found

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?

Does your agreement cover this deployment?

We can review the relevant terms, feature choices, and customer commitments, then help your team identify what to clarify or negotiate.

Speak to a ZDR expert about Moonshot

Sources

Trust and security

Security kimi.com

Posture ledger

2026-08-24

seeded

ZDR 4.0 (f) · B

Seeded from published documentation.

Full key on the scale. Method notes on methodology. Notation is always ZDR 1.0 (s,f,r) · A.