Google flips request storage on by default for new Gemini API projects

Google changed a default on 26 October: new projects calling the Gemini API’s Generate Content endpoints, generateContent, streamGenerateContent and batchGenerateContent, on the paid tier now store requests by default. That brings the Generate Content API in line with the Interactions API, which already stored by default.

Existing projects keep whatever logging setting they already had, so this only bites on new projects. To opt out, set store=false on individual requests, or turn off Generate Content API logging entirely in the Settings panel of the Logs and Datasets dashboard.

// opt a single request out of storage
{ "store": false, ... }

Why it matters: a default you don’t choose is still a default you’re responsible for. If you’re spinning up a new Gemini API project and sending anything sensitive through it, customer data, internal documents, anything under a contract that restricts where content can be retained, you now need to actively set store=false or flip the dashboard setting, rather than assume logging is off until you turn it on.

The caveat: the changelog entry doesn’t state a retention period or say what the stored requests are used for beyond pointing to Google’s Logs and Datasets docs, so if that detail matters for your compliance case, check there rather than assuming.