New paid Generate Content API projects store requests by default
New projects on the paid tier of Generate Content API now have store=true enabled by default. Storage can be disabled for individual requests or in the logging settings. Existing projects retain their previous settings.
According to the Gemini API Changelog entry dated 26 October 2026, new projects on the paid tier of Generate Content API store requests by default using the store=true setting. The change applies to the generateContent, streamGenerateContent and batchGenerateContent methods and aligns the default behavior with Interactions API.
Existing projects retain their current settings. Storage can be disabled by setting store=false for individual requests or by turning off Generate Content API logging in the Settings panel in the Logs and Datasets overview.
Why it matters
For new paid projects, explicit action is now required to prevent requests from being stored. The change to the new default behavior does not affect existing projects.
Two audiences, two different impacts
What this means
For individuals
A developer can disable storage for individual calls in a new paid project directly through a request parameter.
For a business
Creating new paid projects now has implications for corporate data governance: unless the settings are changed, request storage will be enabled for these projects.
Risks and complianceCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.