Gemini History Off Still Keeps Chats for Around Two Months
Google separates Gemini history from AI training, but History off still retains future chats for around two months. Check review, feedback and deletion boundaries.
Gemini History Off Still Keeps Chats for Around Two Months
Google is separating Gemini's chat-history setting from permission to use chats for generative-AI training. That lets people retain their visible conversation history while declining training use. But History off does not mean no retained conversation: Google says future chats will still be saved for around two months for service, feedback and protection purposes. The changes are rolling out, not necessarily available in every account today. Google's announcement explains the change.
For anyone comparing private AI assistants, the question is no longer simply whether a training switch is off. Ask which copy remains, who can process it, and what the setting actually changes.
What Is Confirmed
Google announced the independent controls on November 16, 2026. Its announcement explicitly pairs a useful new choice—keeping history without contributing it to model training—with the longer, roughly two-month retention described for future chats when History is off. It says global rollout will take place in the coming weeks.
This is a documented product-policy change, not a newly reported Gemini data breach. It is also not evidence that opting out is meaningless: restricting one use of content can matter even when the service retains it for other purposes.
What Is Still Unclear
We have not tested the rollout in a signed-in Gemini account, inspected Google's storage systems, or verified deletion of any individual conversation. A published policy is not an independent audit of its implementation.
The announcement does not provide a precise deletion timestamp for each retained chat. Do not silently turn an approximate period into an exact 60-day guarantee. Account eligibility, interface wording and rollout timing also need to be checked in the account you actually use.
History Visibility, Training Permission and Retention Are Different
These are three different questions:
- Visibility: Can I reopen the conversation in the product?
- Use: May the provider use it for a particular purpose, such as training?
- Retention: Does a copy still exist, even if it is not displayed?
A training opt-out is primarily a use restriction. Removing a conversation from the visible list is a visibility change. Neither action alone describes every remaining copy or permitted use.
The practical mistake is treating a convenient interface label as a complete data-lifecycle description. A chat that disappears from a sidebar has not thereby proved anything about a service's operational records. Equally, a provider retaining a record does not automatically prove it used that record for model training.
For the broader distinction, read why turning off AI training does not necessarily stop retention.
The Human-Review and Feedback Exceptions Matter
The updated Gemini Apps Privacy Hub says the training-off commitment applies to future chats, with a feedback exception. Human review can still support other improvement and safety purposes. Chats reviewed by service providers can be kept for up to three years, separated from the account. History-off and Temporary chats are retained with the account for around two months; the last 24 hours can supply response context. Feedback can include conversations, attachments and connected-app content. Other Google services keep their own settings and records.
Those are separate boundaries, not one master privacy switch. Before reporting a problem, inspect what the feedback form proposes to send. A useful bug report usually needs a minimal reproducible example, not a complete client document or a personal conversation.
Training permission also is not a retroactive eraser. When changing an account's settings, record the effective state for future work separately from what you want removed from earlier sessions.
A Five-Question Visibility, Use and Copy Check
Use this worksheet for any hosted assistant, not only Gemini. It is our decision framework, not a report of storage tests we performed.
| Decision | Question to answer | Evidence worth keeping |
|---|---|---|
| Keep working history | Do I need to reopen this conversation later? | The visible history setting and an export plan for work I need |
| Permit training | Which future-content uses am I allowing? | The relevant setting, account type and dated policy |
| Minimize copies | Which attachments, reports or connected services receive content? | A destination list, with an owner for each copy |
| Request deletion | Am I changing future behavior or removing an existing record? | The separate deletion action and its confirmation |
| Verify the boundary | What have I actually checked, rather than assumed? | A narrow test result and its limitations |
Write down the answer before sending something sensitive. If your requirement is that no provider retains or processes the text, stop at the architecture decision: a hosted chat label cannot establish that requirement.
Do not test deletion by uploading real secrets and waiting to see what happens. Use harmless synthetic text, and remember that a clean product screen cannot prove what is absent from infrastructure you cannot inspect.
What To Check in Your Gemini Account
Google's current history-management instructions describe the personal-account path as Settings → History, or the Gemini section of My Activity. The chat-content choice is separate from the audio/Live-recordings choice. Check both rather than assuming a text setting covers recordings.
The same guide distinguishes Turn off from Turn off and delete history, and offers manual deletion. For saved history, it documents auto-delete choices of 3, 18 or 36 months, or no auto-delete; 18 months is the default. These are not the History-off retention period. Work and school controls can instead be managed by a Workspace administrator.
When the new interface reaches your account:
- Identify the account and product surface before following a tutorial.
- Decide whether you need a visible working archive.
- Check the separate training permission and any recording-specific choice.
- Review earlier content separately; changing future use and deleting past content are different tasks.
- Review any connected destination before assuming a source action reaches its copy.
- Record the date and the state you actually saw. Do not assume a rollout announcement describes your interface already.
If the new options are absent, consult the current account-specific help rather than repeatedly changing unrelated settings.
A Practical Example: Private Drafting Without an Unnecessary Archive
Suppose you want help making a business proposal clearer. You do not need an assistant to know the client name, confidential price, personal contact details or an unreleased product codename to evaluate the structure of a paragraph.
A lower-exposure starting task is:
Review this fictional proposal paragraph for clarity. Identify three places where the argument needs better evidence. Do not add facts or invent a client endorsement.
Use a short sample you own and are authorized to process. Replace identifiers before sending it. Keep the actual business record, evidence and approved revisions in the system responsible for that work.
This approach changes the amount of context you disclose. It does not depend on a provider knowing whether the draft feels sensitive, and it does not turn a hosted tool into an offline one.
For a workflow comparison, see private AI chat versus local AI. If the main concern is account-side conversation storage, start with what browser-local chat history means.
Where OpenVeil Fits—and Where It Does Not
If you want hosted help with everyday brainstorming and drafting without a normal server-stored private-chat archive, OpenVeil offers a different history design: private-chat history stays in your browser rather than being maintained as a server-side chat-history record. OpenVeil does not use prompts or uploads to train foundation models.
You can try the ten-action OpenVeil preview without a card, or sign up for OpenVeil Plus at $10/month with 10,000 monthly credits. Try a fictional paragraph like the example above before deciding whether the workflow is useful to you.
OpenVeil remains a hosted service: active requests require OpenVeil and necessary provider processing, while account, billing and operational records are separate. It is not fully offline, anonymous or a promise of zero logs. Browser-local history can also be lost when site data is cleared or a different browser is used.
OpenVeil cannot change Google's policies, erase Gemini records, prove a deletion, or make restricted work appropriate to upload. Review the OpenVeil privacy policy and your own requirements before using sensitive material.
Frequently Asked Questions
Is this a Gemini data breach?
No. This article covers announced settings and retention policies, not evidence that an attacker accessed chats.
Does a training opt-out make a hosted assistant local?
No. Permission to use content for training and the location of active processing are different decisions.
Should I keep history on or off?
Choose based on whether you need a working archive and whether the documented processing fits your requirements. Do not choose based only on whether the sidebar looks empty.
Does paying automatically make an AI conversation private?
No. Compare the actual history design, permitted uses and provider-processing boundaries. A price alone proves none of them.
Bottom Line
The new Gemini controls improve the ability to choose history and training separately. They do not collapse visibility, permitted use, retained copies and deletion into a single decision.
Treat each setting as an answer to a specific question. For sensitive work, minimize the content first, then choose a service whose documented boundaries match the task—not a reassuring switch label.
Try OpenVeil Plus for $10/month
Want hosted drafting and research without a normal server-side private-chat archive? Start with a harmless task in the one-time, ten-action preview—no card required. Video is paid-only.
If it fits, create your account for OpenVeil Plus at $10/month, then choose Plus in Credits & billing to complete checkout. Plus includes 10,000 monthly credits and the same feature set as the higher paid plans; usage is credit-bounded, not unlimited. OpenVeil is for adults 18+, and active requests still require necessary provider processing.
Sources
- Google: updated Gemini controls, November 16, 2026.
- Google: Gemini Apps Privacy Hub, updated November 17, 2026.
- Google: manage and delete Gemini history.
Research cutoff: November 18, 2026. We reviewed public documentation, not a signed-in account or Google's internal retention systems. Rollout timing and settings may change.