What the official source reports
New paid Generate Content projects began storing requests by default. Existing projects retain their settings, and an opt-out is available.
What this means for your operation
Our view: a new project does not necessarily inherit the previous project’s privacy choices. Data inventory must follow provisioning. Teams should know what information reaches the provider, who controls settings and what evidence confirms the approved policy was applied.
Next step for evaluation
Review project settings before sending real data. Check store behavior and logging controls against current documentation. Record the decision with the data owner and validate the full workflow. Provider settings and integration settings are separate checkpoints in the same review.
Sources and references
- Gemini — Release notes Checked on
Retrospective edition 2026-W24. The week identifies this collection’s editorial organization; the text was prepared on the date shown above.
Bring this idea into your operations.
Map the process, connect systems and evaluate outcomes with Zild.
Talk to an expert