Google Now Keeps Gemini Chats for About Two Months Even With History Off, Up From 72 Hours
Google split Gemini's history setting from model training on Monday 16 November and, in the same change, raised retention with history off from three days to about two months. What stays the same and what to tell staff.

Google told Gemini users on Monday 16 November that it was splitting the chat history setting from permission to train its models, and in the same announcement raised how long it keeps chats when history is off from about three days to about two months. The first change gives people more control. The second means that “history off” no longer comes close to “not stored”, and any employee who pastes work material into a personal Gemini account should know that. Google says the longer period is for safety and abuse detection and that the data will not be used to train its models. We read the privacy page on Friday 20 November, and what follows is what it says, what Google has told The Register, and what an IT team can reasonably do with it.
#What changed on Monday
Until Monday, a single setting in Gemini Apps tied together two things: whether your chats were saved in your history, and whether they could be used to improve Google’s models. As The Register reports it, the new History setting separates them, so a person can keep a searchable history of their Gemini chats without also agreeing that those chats feed model training. That is a real improvement for anyone who wanted the first without the second.
The same announcement changed what happens when History is turned off. Google’s Gemini Apps Privacy Hub now says that temporary chats, and chats you have while History is off, are “retained with your account for around two months”. The Register compared an archived copy of the page and found that the figure used to be 72 hours. Google confirmed the old figure to The Register, which quotes a spokesperson saying the company is “lengthening the time from the 72-hour window to around two months to detect, report, and investigate complex emerging abuse scenarios”.
The arithmetic is simple: two months is about twenty times three days, which is the multiple The Register uses in its headline. Google’s page gives the purposes. The retained chats are used to respond to the user, using the last 24 hours of the chat as context, and to “help protect Google, our users, and the public”. It gives an example: the chats are stored so they are available in case of a potential system failure.
#What did not change
The page also describes what happens to anything that reaches a human reviewer, and none of that moved. If you send feedback on a Gemini answer, Google says the feedback, the last 24 hours of your chats and any content in them, including attachments and data from connected apps, are reviewed by specially trained teams. Reviewed material is kept for up to three years, separated from your Google Account. The page adds that reviewed chats are saved for up to three years even if you delete them or turn the setting off afterwards. The Register points out that this was already the case before Monday.
Google’s own feedback explanation says the data may be used to provide, improve and develop its products and machine-learning technologies, and The Register notes that Google’s own FAQ says submitting feedback may mean chats are used to train its models. Google told The Register that this is not what is happening to the two-month retained data: “this retained data will be used strictly for safety and security purposes”, the spokesperson said, and it “will strictly not be used for GAI model training or for other product improvement purposes”. We have no way of testing that claim, so we report it as Google’s.
When History is on, the page says chats are deleted automatically after 18 months by default, and the user can change that period. Temporary chats are not used to train Google’s models, according to the page, but they are retained for the same two months.
#Whose accounts this covers
The page we read is the Gemini Apps Privacy Hub, which describes Gemini for people’s own Google Accounts. It links to a separate “Generative AI in Google Workspace Privacy Hub” for Workspace. We have not found anything saying the two-month change applies, or does not apply, to a company’s Workspace accounts, and Google’s announcement as The Register describes it was aimed at Gemini Apps users. Do not assume either way. If your staff use Gemini through your Workspace tenant, read the Workspace hub and your own admin settings; we covered one such control in our story on the new Workspace Studio collaboration setting.
The group this change certainly touches is the one most IT teams cannot see: people using a personal Gemini account on a work task. It is the same worry we have about any personal chatbot account, and the retention rule makes it a little more concrete. A draft contract, a customer list or a support ticket pasted into a chat with History off still sits with Google, tied to that person’s account, for around two months. If feedback is sent on the answer, a copy can stay for up to three years.
#Our reading: the number to remember is two months
We think Google has done two things at once and presented them as one. Separating history from training is the kind of change privacy advocates have asked for, and it should be judged on those terms. Raising the floor from three days to two months is a different kind of change, and it was made in the same paragraph as the good news. Google’s explanation, that Gemini is more capable than it was and so brings more abuse risk, is plausible, and abuse monitoring is a legitimate reason to retain data. It is also a reason that cannot be checked from outside, so a business should treat the two months as a fact about the service and not as a promise about what happens to the data.
The practical rule we would give staff is short. “History off” means “not in your sidebar”, not “gone”. Treat anything you would not email to an outside supplier as something you should not put into a personal chatbot account, whatever the setting says. For UK organisations, we would add that personal data about customers or colleagues pasted into such a chat is a data protection question for whoever is accountable for it, and worth raising with the person who looks after data protection in your organisation. That is our reading, not a statement of the law from Google or a regulator.
#What an IT team can do this week
- Check your acceptable use policy. If it says only “do not use unapproved AI tools”, add a plain sentence on personal accounts and on what “history off” does and does not do.
- If you use Gemini through Workspace, read Google’s Workspace privacy hub and look at your admin console settings for Gemini. Do not infer them from the consumer page.
- Ask your Google reseller or account manager, word for word: “Does the two-month retention of chats with history off apply to our Workspace accounts, and where is that written down?”
- If staff already use a personal account for work, tell them what feedback does: sending feedback on an answer can put the chat in front of reviewers and keep it for up to three years.
We expect other vendors to be asked the same question now, since retention windows for “history off” modes are rarely given in a single clear place. What would change our view is Google publishing, in its Workspace documentation, the same plain statement of retention that it has now written for individuals.
#If you run a small business without an IT team
If your staff use free chatbot accounts for work, the main step is to decide which one you are happy with and say so in writing. Free accounts are fine for questions that contain nothing about your customers or your finances. For anything else, use a business plan from the supplier you already trust, where the retention and data-use terms are written for organisations, and ask them the question above. You do not need a policy document to start: a message to staff that says “do not paste customer details into personal chatbot accounts” does most of the work.
Evidence trail
Sources and verification
Primary documentation and external technical references used in this article.
About this page
Credited to
Dates
Published
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
More news
All newsWas this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Get new fixes by email.
New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.




Comments
Add a thoughtful note on Google Now Keeps Gemini Chats for About Two Months Even With History Off, Up From 72 Hours. Comments are checked for spam and held for moderation before appearing.