How to request Zero Data Retention (ZDR) for a Gemini Developer API project?

Google AI Studio
21

Hello Mustan,

I have the same requirement for a paid Gemini Developer API project and would like clarification on the official project-specific ZDR approval process.

The official Gemini Developer API ZDR documentation states:

“When your request for ZDR for a particular project is approved…”

Reference: https://ai.google.dev/gemini-api/docs/zdr

Our intended implementation is designed to follow the documented zero-data-retention requirements:

  • Gemini Developer API
  • Interactions API v1
  • store=false on Interactions requests
  • no Google Search grounding
  • no Google Maps grounding
  • no persistent File API usage
  • no explicit context caching (cached_content)
  • no Live API session resumption

We specifically need to understand how to obtain the project-level approval referred to in the official documentation.

Could a Google team member please clarify:

  1. What is the official process for submitting a ZDR request for a particular Gemini Developer API project?
  2. Is a paid Google Cloud Customer Care support plan required to submit this request?
  3. How should the Google Cloud Project ID and Project Number be provided securely/private to Google?
  4. What official confirmation or approval artifact is provided once the project is approved for ZDR?
  5. Does that confirmation identify the exact Google Cloud Project ID and Project Number?
  6. Is there an effective date, expiration, renewal, or periodic review requirement for project-specific ZDR approval?
  7. Are there any additional technical or contractual requirements that must remain satisfied after approval?

For security reasons, I will not post the Project ID or Project Number publicly. I can provide them privately to an authorized Google representative.

I am not asking whether Gemini generally supports ZDR; I am specifically asking for the intake/approval process for the “particular project” approval described in the official Gemini Developer API ZDR documentation.

Thank you.

22

Hi @Mustan_lokhand — following up on my August 24 request above. We’re hoping to begin our small R&D study this week and would still strongly prefer to have project-specific ZDR approved before processing any participant images.

Our implementation is already designed around the documented ZDR requirements, including stateless generateContent, no Search/Maps grounding, no persistent File API use, and no explicit context caching.

Could you please DM me with the appropriate process for submitting the project ID/number for review? Thank you.