Gemini API now stores requests by default for new paid-tier projects using generateContent and related endpoints
An easy-to-miss default change that decides whether user data stays on Google's side. This covers who is affected and how to opt out.
// Key points
- From October 26, new projects using the Generate Content API (generateContent, streamGenerateContent and batchGenerateContent) on the paid tier store requests by default (store=true), matching the Interactions API.
- Existing projects keep their current setting.
- Opt out with store=false on individual requests, or turn off Generate Content API logging in the Settings panel of the Logs and Datasets dashboard.
Builder's takeThis hits new projects, so the likely victims are freshly created test or client projects. I would pass store=false explicitly in the call layer rather than rely on a console setting. For a product like AI Cloud Drive that handles people's private files, whatever the privacy notice promises has to be switched off in code to match.
// Background · from #Google
Full timeline →- Oct 27 Google Docs edits Markdown files natively and Drive previews them, aimed at humans and agents working together
- Oct 26 Google details TB screening in the field: a partner device has read 25,000 chest X-rays, and open MedGemma has passed 10 million downloads
- Oct 23 Claude Models on Google Cloud (Anthropic managed) launches: the Claude API run by Anthropic, reached through a Google Cloud project, with IAM for access and Marketplace for billing