Google Vertex / Gemini Enterprise Agent Platform zero data retention: terms and exceptions
ZDR 1.0 (s,f,r) · B
Short answer
Flag-triggered abuse logging only, <=90d, in-region; 24h caching on by default. Advanced AI Safety Addendum: ZDR 'may not be possible' on some advanced models; grounding logs 3d non-disablable.
Scope and evidence
| Provider | |
|---|---|
| Service | Vertex / Gemini Enterprise Agent Platform |
| Lane | Enterprise |
| Origin | |
| License | proprietary |
| Hosting | Provider-hosted |
| Score | ZDR 1.0 (s,f,r) · B Contractual ZDR. Paper ZDR: no content retention by agreement, with typed carve-outs in force |
| Evidence | Public documentation reviewed (B: published documentation) |
| Source-review date | 2026-08-24 (registry) |
Other lanes for Google
Structured breakdown
- Default posture
- flag-triggered abuse logging only, <=90d, in-region; 24h caching on by default
- Exceptions and carve-outs
- Advanced AI Safety Addendum: ZDR 'may not be possible' on some advanced models; grounding logs 3d non-disablable
Approval and setup path
cache disable per project + abuse-monitoring exception form
Flags on this record
- s
- safety-flag retention beyond base window
- f
- stateful-feature carve-outs (files, batch, threads, caching, grounding)
- r
- revocable: provider reserves unilateral downgrade
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.
Sources
Trust and security
- Trust Center cloud.google.com
- Compliance cloud.google.com
Posture ledger
seeded
ZDR 1.0 (s,f,r) · B
Seeded from published documentation.
Full key on the scale. Method notes on methodology. Notation is always ZDR 1.0 (s,f,r) · A.