Feature-by-feature retention matrix
| Feature | Google documents | Zero-footprint action |
|---|---|---|
| Abuse-monitoring logs | Approved ZDR projects clear user content and identifiable metadata before logging. | Keep the project approval and verify the production project. |
| Grounding with Search or Maps | Prompts, context and outputs are stored for 30 days; storage cannot be disabled while using the feature. | Do not use the feature when the workflow requires zero storage. |
| Interactions API | Conversation state is stored by default. | Set store to false. |
| Live API | Session resumption can retain conversation state for up to 24 hours. | Do not configure session resumption. |
| File API | Files remain at rest until deletion or expiry. | Delete files and verify the lifecycle. |
| Explicit context cache | Cached content persists for its TTL or expiry time. | Avoid the feature for an absolute zero-data footprint. |
| Implicit in-memory cache | Project-isolated RAM cache has a 24-hour TTL and is not treated by Google as violating ZDR. | Record the vendor definition and decide whether the firm accepts it. |
Pre-matter checklist
- Confirm the request is a paid service through the intended billing project.
- Attach Google’s ZDR approval for that project.
- List every API and feature the application can call.
- Disable or avoid the storage paths that conflict with the target.
- Use a de-identified canary request and capture configuration, timestamp and logs.
- Verify file deletion, cache expiry and downstream application logging.
- Assign a reviewer for terms, configuration and future changes.
The application can defeat the provider setting
A ZDR provider route does not remove copies created by proxies, observability tools, prompt stores, tracing systems, browser extensions, support tickets or the firm’s own database. Draw the complete data path and test deletion at every hop.
Evidence to keep
Retain project ID, billing state, ZDR approval, region, endpoint, model ID, feature flags, request trace, logging configuration, file and cache lifecycle, test date and reviewer. Re-run the checklist after a model, endpoint, feature or terms change.
What ZDR does not establish
ZDR is a provider retention configuration. It does not establish privilege, legal sufficiency, model accuracy, compliance with a jurisdiction’s professional rules or the absence of customer-side copies.
FAQ
Can Gemini API Search grounding be zero data retention?
Google says Search grounding stores prompts, context and output for 30 days and that this storage cannot be disabled while the feature is used.
Is setting store=false enough?
No. That setting addresses Interactions API state. Grounding, files, caches, Live API session resumption, provider logging and customer-side systems remain separate.
Does Gemini API ZDR require approval?
Google’s documentation describes approval for a particular project before user content and identifiable metadata are cleared prior to abuse logging.
Sources checked
- Zero data retention in the Gemini Developer API, checked 2026-09-03.
- Gemini API Additional Terms, checked 2026-09-03.
Operational information, not legal advice. Verify current terms, account configuration and applicable professional duties before use.