Gemini API turns request storage on by default for new paid projects

Google has changed the default storage behavior of the Gemini Generate Content API: new projects on the paid tier now store requests unless developers opt out. The October 26 release note covers generateContent, streamGenerateContent and batchGenerateContent. Existing projects retain their current settings.

The practical consequence is that a fresh project can behave differently from an older one running the same application code. Storage now defaults to store=true, matching the Interactions API. Developers can set store=false for an individual request or disable Generate Content logging in AI Studio's Logs and Datasets settings.

The documentation says request-level settings override project settings. Passing the Generate Content store property requires Python google-genai 2.33.0, JavaScript @google/genai 2.31.0, Java google-genai 1.79.0 or Go google.golang.org/genai 1.76.0 or later.

The logs expose the full prompt, response and previous-turn context. Their default retention window is 55 days, after which they expire and are marked for deletion; projects can choose 7, 14, 28 or 55 days. Logs saved to datasets do not expire. Sharing those datasets with Google for research is a separate choice.

For applications that depend on storage being disabled, an explicit setting now matters when creating a project.