Gemini API’s changelog and Logs and datasets docs say request storage for Generate Content is now on by default for paid-tier projects created on or after October 26, 2026. The change covers the three Generate Content methods above and is framed as aligning with how the Interactions API already stores requests.

Projects created before that date are unchanged: they keep the previous Generate Content storage setting—off (store=false) unless logging was already turned on in AI Studio.

Log storage itself is only available on paid-tier projects. The Logs page lead can read as if both APIs always store by default; the Note and changelog say Generate Content defaults on only for new projects from October 26, 2026—not for every project all along.

How to opt out (official)

  • Set store=false on an individual request (request-level store overrides the project default).
  • Or open the Logs and Datasets dashboard Settings and turn off Generate Content API logging for the project.

Request-level store on Generate Content needs recent SDKs: google-genai ≥2.33.0 (Python), @google/genai ≥2.31.0 (JS), google-genai ≥1.79.0 (Java), google.golang.org/genai ≥1.76.0 (Go).

Logs expire after a default 55-day retention window (configurable to 7／14／28／55 days)—background only; this piece is about the default store flip, not a retention guide.

How entries show up in the dashboard has not been tested on this site—for reference only. Checked results can go through the site-owner contact link in the footer.

Related reading: Gemini 4 Argon Usage Limits in the Gemini App, Antigravity and API (October 2026).