# Google DeepMind — Generate Content API storage on by default

- Company: Google DeepMind (deepmind.google)
- Announced: 2026-10-26
- Category: safety-policy-update
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://ai.google.dev/gemini-api/docs/changelog#10-26-2026
- Record: https://forck.live/items/27707-generate-content-api-storage-on-by-default
- Subject: Gemini API

Google DeepMind is turning on request storage by default for new paid-tier projects that use the Generate Content API, matching how the Interactions API already behaves. The change covers generateContent, streamGenerateContent and batchGenerateContent, and applies only to new projects; existing projects keep whatever setting they have now. Developers who do not want their requests stored can set store=false on individual requests, or switch off Generate Content API logging in the Settings panel of the Logs and Datasets dashboard. The company points to its Logs and datasets documentation for the details.

## Evidence

Verbatim from https://ai.google.dev/gemini-api/docs/changelog#10-26-2026:

> New projects using the Generate Content API (generateContent, streamGenerateContent, and batchGenerateContent) on the paid tier now store requests by default (store=true), matching the Interactions API. Existing projects keep their current setting.

---

Record: https://forck.live/items/27707-generate-content-api-storage-on-by-default
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md