Google’s official Gemini API release notes say new paid-tier projects using generateContent, streamGenerateContent or batchGenerateContent now have store=true by default. Existing projects retain their prior setting. The change aligns the Generate Content API with the Interactions API and is easy to miss if you create a new integration from an old sample.
This matters when testing client documents, contracts, family information or code that should not be retained in an extra provider log. Google documents two ways to opt out: set store=false on individual requests or disable Generate Content API logging in the Logs and Datasets dashboard. It is not evidence that every Gemini API project suddenly changed settings.
Before any new AI Roundtable or consulting proof-of-concept, inspect the project’s logging defaults and write the intended retention behavior into configuration. Make a test request containing a harmless marker, then confirm the expected logging behavior in the console.
For any newly created paid Gemini API project, explicitly review store=true and decide whether to set store=false.