◉GEMINI LABJP
●OMNI 1.2 — Gemini Omni 1.2 Flash is generally available (11/5) with up to 15-second video and conversational editing; 1.1 Flash is routed to 1.2 on 12/3●COMPUTER — Computer Use is now generally available in the Interactions and GenerateContent APIs (10/30)●LIVE — Live and TTS preview models shut down as early as 11/17 (10 days left). Move to gemini-3.8-live and the 3.8 TTS models●CLI — Gemini API CLI (gemini-api) is out in beta (10/27): a zero-dependency client for agents and CI●2.5 PRO — gemini-2.5-pro and 2.5-flash are routed automatically on 12/1 (24 days left), to 3.8 Flash and 3.5 Flash-Lite●NEW — Stop Re-Reading Every Crash Report: Gre…●OMNI 1.2 — Gemini Omni 1.2 Flash is generally available (11/5) with up to 15-second video and conversational editing; 1.1 Flash is routed to 1.2 on 12/3●COMPUTER — Computer Use is now generally available in the Interactions and GenerateContent APIs (10/30)●LIVE — Live and TTS preview models shut down as early as 11/17 (10 days left). Move to gemini-3.8-live and the 3.8 TTS models●CLI — Gemini API CLI (gemini-api) is out in beta (10/27): a zero-dependency client for agents and CI●2.5 PRO — gemini-2.5-pro and 2.5-flash are routed automatically on 12/1 (24 days left), to 3.8 Flash and 3.5 Flash-Lite●NEW — Stop Re-Reading Every Crash Report: Gre…
Articles/API / SDK
◈ API / SDK/2026-10-27Beginner

New paid projects now start with request storage switched on. Three places to check the day you notice

Gemini API paid projects created on or after October 26, 2026 store generateContent requests by default. How to tell whether your project is affected, how to turn storage off in Logs Settings, how to set store=False per request, and how to shorten retention, following the official wording.

Gemini API255LoggingPrivacystore parameterAI Studio4

Picture the day you rebuild a paid Google Cloud project for a new app prototype. You issue a key, the first request goes through, and you finally relax. Then you open Logs in AI Studio, and the text you sent is sitting there in a neat list.

As an indie developer, I pass user-written app review text straight into the API for translation. Names and email addresses sometimes ride along, so "where does this end up?" is a question I want answered before the demo works, not after.

On October 26, 2026, the Gemini API changelog added one line about exactly this. What I'd like to say first is that you don't need to panic and switch everything off. There are just three places to check.

What changed, read as the changelog words it

The entry is titled "Generate Content API storage on by default". In short:

  • It covers generateContent, streamGenerateContent and batchGenerateContent
  • Paid projects created on or after October 26 default to store=true
  • Existing projects keep their current setting
  • To opt out, set store=false on individual requests, or turn logging off in Settings under Logs and Datasets in AI Studio

If you only skim the headline, it sounds like everyone's setting changed. On my first read I nearly took it that way too. The body says plainly that existing projects stay as they are, so only newly created paid projects are affected.

Project stategenerateContent default
Paid project created on or after Oct 26Stored (store=true)
Paid project created earlierUnchanged (not stored unless logging was enabled in AI Studio)
Free-tier projectLog storage itself is a paid-tier feature

The Interactions API already stored requests by default. This change brings generateContent in line with it.

Check 1: is your project affected?

Look at the project's creation date. If it's October 26 or later, assume storage is on. The Google Cloud console's project list shows it. If you're unsure, open Logs in AI Studio and see whether recent requests appear.

If they do, storage is active. If not, nothing is being stored right now. One caveat: Logs only displays for a project with at least one active API key. Deleting every key hides the logs, but it doesn't mean what was stored is gone.

Check 2: turn it off for the whole project

If a project doesn't need storage at all, open Settings under Logs and Datasets in AI Studio. generateContent and the Interactions API can be switched separately.

One thing is easy to miss. Turning off Interactions logging also stops automatic saving and retrieval of conversation history. If your implementation leans on server-side history, it will behave differently unless you override it per request.

If you're rethinking where history should live, keeping history on the server versus pruning it on the client may help.

Check 3: set store per request

To keep the project setting but skip storage for particular calls, override it on the request. The official documentation shows a Python SDK example that passes store in config.

from google import genai
 
client = genai.Client()  # the API key is read from the environment
 
response = client.models.generate_content(
    model="MODEL_ID",  # replace with the model ID you actually use
    contents="Translate this text into Japanese: ...",
    config={"store": False},  # do not store this request only
)
print(response.text)

The SDK version is where people may get stuck. According to the documentation, using store with generateContent requires google-genai 2.33.0 or later. Check your installed version first:

pip show google-genai | grep Version

For direct REST calls, the field name wasn't in the pages I read. I'd rather not guess, so please confirm it in the official API reference before relying on it.

The request-level setting wins over the project-level one. That means you can put store=False only on calls that might carry personal data and leave the rest at the default.

If you decide to keep storage: shorten retention

Sometimes you want storage for debugging. In that case, tighten retention. The default is 55 days, and you can choose 7, 14, 28 or 55. Logs are marked for deletion after the window (datasets you save don't expire).

How you use the APISuggested setup
Routinely send input that may contain personal dataTurn storage off project-wide, or use store=False on those calls
Want to review failed inputs and outputs while developingKeep storage, set retention to 7 or 14 days
Want to keep examples for evaluationSave only what you need as a dataset

Some inputs are outside logging: inputs with video, GIFs or PDFs, and models such as Imagen, Veo and embeddings. I'd still avoid treating "not logged" as your basis for handling personal data.

What the official pages did not say

Neither the changelog nor the Logs and Datasets page states exactly what is stored beyond "requests", or whether logs are used for training. I won't fill that gap with a guess. The "data logging and sharing" terms on the official site are the part to read against your own use.

For my own projects, I'd check in this order: the creation date, whether history shows up in Logs, and whether calls that carry personal data have store=False. Those three go at the top of my checklist for any new project.

If you can spare a minute today, open Logs on the most recent paid project you created, just once.

Share

Thank You for Reading

Gemini Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

If you found this article helpful, a small tip ($1.50) would mean a lot to us. Your support helps keep this site ad-free and covers server and hosting costs.

Related Articles

◈ API / SDK2026-10-30
An 'API key expired' Error Doesn't Always Mean Expired. Check Which Key Is Actually Sent Before You Renew It
A 400 with API_KEY_INVALID from the Gemini API cannot tell you whether the key expired or something else is wrong. A small diagnostic script checks env-var precedence and stray quotes first, run here against dummy keys.
◈ API / SDK2026-10-30
My ADK Agent Never Ran and Said 'API key expired' — Reading the Reason Code Gave Me a Triage Order
When ADK returns 400 INVALID_ARGUMENT 'API key expired. Please renew the API key.' on every run, check this order before assuming the key expired: read the reason code, compare shell and .env keys by their last four characters, then test the key alone over REST.
◈ API / SDK2026-10-14
When Your config Raises "Extra inputs are not permitted", Check the Spelling of Every Key
If a google-genai call fails with a pydantic ValidationError (extra_forbidden) the moment you pass a config, it is almost always a one-letter typo. Here is the output I reproduced, a small function that checks keys before the call, and how to tell why response.text came back as None.