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.

Cohere SaaS Platform API, default zero data retention: terms and exceptions

Q: What is the ZDR score for Cohere SaaS Platform API, default?

On zdr.dev the published score is ZDR 4.0 (s,h,r,x) · B. SaaS logs prompts and generations for 30 days. Training use is an opt-out dashboard toggle, so prompts train unless turned off. Enterprise Data Commitments do not apply to trial keys. Flagged misuse may be retained and reviewed. Private deployments receive no prompts.

ZDR 4.0 (s,h,r,x) · B

Short answer

SaaS logs prompts and generations for 30 days. Training use is an opt-out dashboard toggle, so prompts train unless turned off. Enterprise Data Commitments do not apply to trial keys. Flagged misuse may be retained and reviewed. Private deployments receive no prompts.

Scope and evidence

Provider	Cohere
Service	SaaS Platform API, default
Lane	API default
Origin	CA Canada
License	proprietary
Hosting	Provider-hosted
Score	ZDR 4.0 (s,h,r,x) · 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 Cohere

ZDR 1.0 (s,r) · Bcohere/api · zdrZDR

ZDR 4.0 (s,h,r,x) · Bcohere/api · defaultAPI default

Structured breakdown

Default posture: SaaS logs prompts and generations for 30 days. Training use is an opt-out dashboard toggle, so prompts train unless turned off.
Exceptions and carve-outs: Enterprise Data Commitments do not apply to trial keys. Flagged misuse may be retained and reviewed. Private deployments receive no prompts.

Approval and setup path

Enterprise-approved ZDR via support@cohere.com

Flags on this record

s: safety-flag retention beyond base window
h: human review possible
r: revocable: provider reserves unilateral downgrade
x: subprocessor exposure

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?