Gemini API now enables request storage by default for new paid projects
In short: Google has updated the Gemini API to automatically store requests (store=true) for all new projects on the paid tier. This change aligns standard content generation methods with the Interactions API, requiring developers to manually opt out if they prefer not to store request data.
This summary was generated automatically by AI from Gemini API Changelog's publication. It is our own text, not a copy of the original — facts, figures and quotes belong to the source, linked above and below.
What changed?
- 1New paid projects now default to store=true for generateContent, streamGenerateContent, and batchGenerateContent.
- 2Existing projects retain their previous settings.
- 3Opt-out is available via request parameters or dashboard settings.
Why it matters
If you rely on the Gemini API for sensitive customer conversations or private data processing, your company must now proactively manage storage settings to ensure compliance. Failure to adjust this default may lead to unintended storage of PII or proprietary information on Google servers.
What it means for AI agents and contact centers
For voice AI pipelines, this introduces a compliance requirement. When building telephony agents, check your project settings to disable storage if your client's data privacy policy prohibits external logging of voice-to-text transcriptions or API prompt data.
Sources
- Gemini API ChangelogOfficialPrimary sourceOriginal article →„Generate Content API storage on by default : New projects using the“26 Oct 2026, 02:00Licence: Google Developers: CC BY 4.0 · our summary (content changed)
- Published by source
- 26 Oct 2026, 02:00
- Found by our system
- 26 Oct 2026, 12:51
- Summary generated
- 26 Oct 2026, 12:51
This article was written by AI from the original source. Facts, numbers and prices come from the source; missing values are marked “Not specified”. Legal notice, copyright and privacy