Google's Gemini API changelog for October 26, 2026 says new paid-tier projects using Generate Content API methods now store requests by default, matching the Interactions API. The note says existing projects retain their current setting.
What changed
The entry covers generateContent, streamGenerateContent, and batchGenerateContent. Google documents opting out through store=false on individual requests or by disabling Generate Content API logging in the Logs and Datasets settings. Teams should consult the linked logging documentation for the complete behavior and applicable terms.
Stored requests, model training use, and contractual retention are different questions. This release note should not be paraphrased as a blanket statement that customer data is used for training.
Why established teams can still be affected
A production integration may keep its settings while a newly created testing project inherits the new default. That can create a mismatch between your policy and what developers assume is happening. Infrastructure templates and onboarding checklists deserve the same review as application code.
An immediate verification plan
Inventory recently created projects, identify which handle confidential material, and review project-level logging alongside request options. Test the setting through the documented controls rather than relying on an old screenshot or a single developer's memory.
Update internal integration guidance with the chosen default and its rationale. Make privacy review part of project creation, not an occasional audit. This is a small release-note entry with a potentially important operational consequence: safe defaults must be deliberately maintained as vendors change their platforms.
Sources & further reading
Reviewed October 26, 2026. Product availability and regulatory guidance can change. Vendor performance claims are not independent Rovio AI benchmarks.
Found this useful? Share it.