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.

Google Gemini Developer API, paid tier zero data retention: terms and exceptions

Q: What is the ZDR score for Google Gemini Developer API, paid tier?

On zdr.dev the published score is ZDR 2.0 (f,h) · B. Abuse logs 55d, storable in any country; no product-improvement use. Search grounding stores 30d non-disablable; Interactions API store defaults true; Live API caches 24h.

ZDR 2.0 (f,h) · B

Short answer

Abuse logs 55d, storable in any country; no product-improvement use. Search grounding stores 30d non-disablable; Interactions API store defaults true; Live API caches 24h.

Scope and evidence

Provider	Google
Service	Gemini Developer API, paid tier
Lane	API default
Origin	US United States
License	proprietary
Hosting	Provider-hosted
Score	ZDR 2.0 (f,h) · 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 Google

ZDR 1.0 (s,f,r) · Bgoogle/vertex · geapEnterprise

ZDR 2.0 (f,h) · Bgoogle/gemini-api · paid tierAPI default

Structured breakdown

Default posture: abuse logs 55d, storable in any country; no product-improvement use
Exceptions and carve-outs: search grounding stores 30d non-disablable; Interactions API store defaults true; Live API caches 24h

Approval and setup path

per-project ZDR approval (logs sanitized before write)

Flags on this record

f: stateful-feature carve-outs (files, batch, threads, caching, grounding)
h: human review possible

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 Google

Sources

Trust and security

Trust Center cloud.google.com
Compliance cloud.google.com

Posture ledger

2026-08-24

seeded

ZDR 2.0 (f,h) · B

Seeded from published documentation.

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