Skip to content
Hugin
An empty aisle between tall dark server cabinets under grey overhead pipework.

Hugin News

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

2 min read

Original fictional editorial illustration from the Hugin archive; not documentary evidence or a depiction of the actual institution, product, people or event.

This record was prepared on the date shown and recovered after a publishing interruption.

Google's October 26 release note says new paid Gemini API projects now store Generate Content requests by default. Existing projects keep their settings. Developers can turn logging off for a project or set store=false on a request; Google's guide says ordinary logs have a default 55-day retention window, while logs saved to datasets do not expire.

googlegemini-apiprivacydata-retentiondeveloper-tools
source receipts
2
source host
1
read time
2min
primary source
Linked

New paid Gemini API projects now store Generate Content requests by default, Google announced in an October 26 release note. Projects created before that date keep their existing setting.

The change covers the generateContent, streamGenerateContent and batchGenerateContent methods. Google says it brings their default into line with the Interactions API, which already stores requests by default.

What the stored logs contain

Google's Logs and datasets guide says a developer can inspect a log's full prompt, Gemini's response and context from previous turns in Google AI Studio. Log storage is available only for projects on the paid tier.

Ordinary logs expire and are marked for deletion after a default 55-day retention window. Project settings allow windows of 7, 14, 28 or 55 days. There is an important exception: logs saved to a dataset do not expire.

The guide presents logging as a way to observe and debug applications. It separately describes a developer's choice to share datasets with Google as demonstration examples. The change in logging defaults alone does not establish that a project's data was shared for that purpose.

How developers can change it

Google gives two routes: turn off Generate Content API logging in the Settings panel of the Logs and Datasets dashboard, or set store=false on individual requests. The request-level setting takes precedence over the project setting.

For older projects, Generate Content storage remains off unless logging was previously enabled in AI Studio. The guide says developers can change project preferences at any time and can control Generate Content and Interactions logging separately.

Turning off Interactions logging has an additional consequence: Google warns that the API will stop automatically storing and retrieving conversation history unless a request explicitly overrides the setting.

Limits of the change

The guide says logging does not currently support several categories, including inputs containing videos, GIFs or PDFs, and Imagen, Veo, Gemini embedding and Gemini Robotics models. No account settings or live API behavior were tested for this report.

Source links