Google makes it easier to use Gemini without training AI on your data
- ID
- 47447
- Status
- summarized
- Published
- 18 Nov 2026, 12:50 AM
- Fetched
- 18 Nov 2026, 1:46 AM
- Provider
- Ars Technica
- Category
- technology
- Original URL
- https://arstechnica.com/ai/2026/11/google-will-let-you-opt-out-of-ai-training-in-gemini-without-losing-your-history/
- Source URL
- https://feeds.arstechnica.com/arstechnica/index
Summary
- Score
- 5.5
- Created
- 18 Nov 2026, 1:46 AM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
Ars Technica reports that Google has split Gemini's activity settings into two separate toggles: one for whether your chats are used to train AI models, and one for whether chat history is retained. Previously, per the piece, opting out of AI training meant giving up history; now you can keep history while declining training. The excerpt provided is truncated after the lede, so the rollout date, which plan tiers or regions get it, and default states are not stated in the text.
Why it matters
If you paste client code, internal docs, or customer data into Gemini, the decision changes: you can now plausibly keep conversational history (useful for continuity across a project) while turning off training — but the defaults and account-tier applicability are unconfirmed in this text, so check the actual toggles in your own Gemini activity settings before assuming your current usage is opted out. Teams with contractual data-handling clauses should still verify against the paid/API terms rather than a consumer settings toggle.
Discussion angle
For those of us who paste proprietary code into Gemini: is a per-account training toggle actually an acceptable control for client work, or do you treat consumer-tier chat as off-limits and route anything sensitive through API/enterprise terms instead?