What changed
From October 26, 2026, new paid-tier Gemini API projects store Generate Content API requests by default. Existing projects retain their settings. This is an API change for integrations, not an announcement about every conversation in the Gemini app.
Who should check
An owner commissioning a new AI integration should add a question to acceptance: does the supplier store requests in the project’s logs? Drafting customer replies automatically is one illustrative scenario, not a case tested by Nadali.
Our suggested checking sequence:
- Ask the person responsible to establish the project’s creation date, billing tier and actual API.
- Agree why logs are needed, who reviews them and what data may be submitted.
- Check settings before a fictional-data test, and retain evidence of the result.
- Repeat the check when accepting the next new project rather than relying on old arrangements.
Availability and limits
The documentation allows Generate Content logging to be disabled in AI Studio settings or with store=false for an individual request; the request setting takes precedence. The developer needs to verify support in their SDK version.
According to the logging policy, logs are private to the project, and their prompts and responses are not used for product improvement by default. Voluntarily sharing datasets with Google is a separate choice. The default retention window is 55 days, with 7, 14 or 28 days also available. Records are marked for deletion when the window ends; saved datasets have no such retention period.
The takeaway: explicitly check storage for a new integration rather than assuming it works as before. Disabling this log does not guarantee the absence of other storage, including abuse monitoring.
Author: Nadali. Prepared with AI. Sources checked October 28, 2026; Nadali made no API requests or account tests. Cover: a conceptual AI illustration, not the Gemini interface or a test photograph.
