Gemini API stores generateContent requests by default for new paid-tier projects

Archive entry: this covers an event from October 26, 2026, and we published it on November 8, 2026. The details come from sources dated at the time and may have changed since.

On October 26, 2026, Google changed a default in the Gemini API: new paid-tier projects store generateContent requests unless they opt out. The change was listed in the Gemini API changelog for October 26, 2026 and matches the default behavior of the Interactions API.

What changed

• From October 26, 2026, new paid-tier projects store generateContent, streamGenerateContent and batchGenerateContent requests by default, which means store=true.
• The default matches the behavior of the Interactions API.
• Existing projects keep the setting they had.
• Developers can opt out on individual requests by setting store=false.
• Developers can also opt out for a whole project by turning off Generate Content API logging in the Settings panel of the Logs and Datasets dashboard.

What it means for people building with the Gemini API

The change moves the data-retention default for new paid projects, so it belongs on the privacy and compliance checklist of any team that creates one. A team can keep the default, send store=false on individual requests, or turn off logging for the project in the dashboard.

Because existing projects keep the setting they had, storage behavior can differ between older projects and projects created after October 26, 2026. Teams that run several projects may want to confirm the setting for each one in the Settings panel of the Logs and Datasets dashboard.

Sources

• Gemini API changelog: October 26, 2026 (Google AI Studio (Gemini API changelog), October 26, 2026, official)

Written with AI assistance, strictly from the sources listed above. Before it went live, automated checks verified its dates, sources and every language edition.