Google Rewrote Its "No Human Reviewers" Promise in a 2023 Blog Post. The New One Says Your Email Can Be the Summary.

Abhishek Dash11 min read
A glowing computer screen partially obscured by a large translucent frosted-glass eye looking at the viewer, with a ghostly email envelope behind it, reading glasses on a closed notebook, and a warm spotlight on a dark desk.

In short

In October 2023 Google promised that Workspace extension content was not seen by human reviewers, used for ads, or used to train the model. On 16 October 2026 it edited that same sentence to allow Connected Apps data to be used to train generative AI models and reviewed by humans in limited circumstances. Its own Help documentation now says the summary sent to reviewers may just be the email or file, and warns users not to connect apps containing confidential information.

Key takeaways

  • In October 2023 Google's VP of Trust and Safety published a commitment that Workspace extension content was not seen by human reviewers, used for ads, or used to train the model.
  • On 16 October 2026 Google edited that same sentence in the 2023 blog post, adding an italicised update allowing Connected Apps data to be used for model training and reviewed by humans in limited circumstances.
  • Help Answer 16836988 states that data from Connected Apps is used and human reviewed per the Gemini Apps Privacy Notice, and that the summary may just be the email or file.
  • The Gemini Apps Privacy Hub, last updated 26 October 2026, states that a subset of chats are reviewed by human reviewers and retained for up to three years.
  • Google warns users not to connect apps containing confidential information a reviewer should not see.
  • The 2023 commitment was scoped to Bard Workspace extensions, not all Google products, and the 2026 feature is an opt-in called Personal Intelligence with Connected Apps.

On 16 October 2026 Google edited a sentence it had published in October 2023. The sentence, written by Google's VP of Trust and Safety, promised that if you chose to use the Workspace extensions in Bard, your content from Gmail, Docs and Drive was not seen by human reviewers, used by Bard to show you ads, or used to train the Bard model. The edit, added inside the original paragraph rather than published as a new post, says that as Google has added features letting users connect Workspace apps to other Google services, that same subset of data can be used to train generative AI models depending on a user's settings, and can be subject to human review in limited circumstances.

The reversal is real, it is disclosed by Google in Google's own words, and it is two-sided in a way that is easy to miss. Google did not simply start reading emails. It built an opt-in feature, Personal Intelligence with Connected Apps, through which users connect Gmail, Drive, Docs, Calendar, Keep, Tasks, Chat, Meet, Wallet, Photos and YouTube to Gemini, and it updated the 2023 blog post and the Help centre to match. The 2023 commitment was not kept; the promise was rewritten to describe a different product with a different scope.

What Google actually wrote

The 2023 sentence, as originally published:

"If you choose to use the Workspace extensions in Bard, your content from Gmail, Docs and Drive is not seen by human reviewers, used by Bard to show you ads, or used to train the Bard model."

The 2026 edit, directly beneath it:

"Update, October 16, 2026: You can view the latest about how some new features work here. As we've continued to make Google products more personalized and helpful, we've added features that enable users to choose to connect Workspace apps to other Google services. If users choose to enable these new features, data from Workspace Apps will be processed to personalize other Google experiences, and depending on a user's settings, that same subset of data can be used to train generative AI models. It can also be subject to human review in limited circumstances."

Two things worth noting about how this was done. The update was added to a 2023 blog post, which is standard practice and makes the change findable. But it was placed inside the original paragraph, so a reader arriving from a search result and reading the bolded 2023 sentence in isolation gets the outdated commitment. The current Help documentation, by contrast, states the human review position directly with no historical framing.

What the Help centre now says

Help Answer 16836988, "About personalization with Connected Apps", states plainly: "Data from Connected Apps is used and human reviewed per the Gemini Apps Privacy Notice." It also says the data is used to "improve Google services, including training generative AI models, for everyone."

The part that makes this a story rather than a policy footnote is a warning in the same document: "Important: Please don't connect your apps to Gemini Apps if they contain confidential information that you wouldn't want a reviewer to see." And a sentence that follows it: "In some cases, for example, where the email or file is brief or particularly relevant to respond to the prompt, the summary may just be the email or file."

That is Google documenting the risk and telling users to avoid it. It did not stop it.

The Gemini Apps Privacy Hub, last updated 26 October 2026, adds the retention terms. A subset of chats are reviewed by human reviewers, including Google's trained service providers, and reviewed chats are retained for up to three years. Chats are disconnected from the account before being sent to service providers. Turning off Keep Activity stops future chats being reviewed to improve Google services, but even with Keep Activity off or temporary chats, Google still uses chats to protect Google, its users and the public, including with help from human reviewers.

So the obvious mitigation does not eliminate the exposure, and it is not obvious from the setting's name.

The part that is new: ambient ingestion

The documentation establishes that Connected Apps data can reach human review. A GitHub reproduction repository makes a specific claim about how it reaches the model in the first place, and that claim is what a reader should treat as a claim rather than a finding.

The reproduction says that when you chat with consumer Gemini with Connected Apps enabled, ambient mentions of personal topics such as trips, bills, names or reservations can autonomously trigger background Workspace lookups, without an @Drive or @Gmail tag and without an explicit request for a file search. It then describes four possible outcomes of a single test run, because tool-calling is probabilistic:

  1. Zero retrieval. No Connected Apps tool call fires. The repository notes this is especially likely when Gemini can resolve the query from model weights or prior conversation history, including in different threads.
  2. Metadata or generic summary. Gemini pulls emails and files and produces something like "You have 3 emails regarding your flight".
  3. Partial unredacted extraction. A two to four sentence exact quotation from the file, frequently including sensitive personal information, account details or specific figures.
  4. Full-file ingestion. The complete unredacted text of the document or email enters the session context.

The repository's own guidance on method is sound and worth repeating: if you test once and see state 1 or 2, you have not disproven the pipeline, you have simply observed a single draw from a nondeterministic system. Delete your conversation and try again.

The reproduction procedure requires Connected Apps active, Gemini set to Flash with high thinking or better, a subject mentioned that lives in Drive or Gmail without an @ tag, and then asking Gemini to print the exact text and metadata block the retrieval tool returned. That last step is the smart part. Rather than relying on the model's summary, it asks for the tool payload itself, which is the part that would carry the unredacted content.

What this does not establish, and what no one has established: the rate at which ambient ingestion fires, whether it is more likely for particular phrasings, and whether Google has a detection mechanism. Those are the numbers a serious investigation needs and the repository does not have them.

The scope distinction that matters

The most useful comment on the story was the one that drew the correct scope distinction:

"Note that this is specifically Consumer Gemini with Connected Apps; Workspace Gemini (and Workspace Intelligence, the RAG thing for enterprise/Workspace) still claims not to be subject to human review."

That distinction matters and the repository itself added it as a clarification heading on 10 November, the same day as the reproduction. A story that said "Google reads your email" would be wrong for every business user with a Workspace account. The correct statement is narrower: consumer Google accounts that connect Gmail or Drive to Gemini's Personal Intelligence feature.

The 2023 commitment was also scoped to Bard Workspace extensions. It was never a general claim about all Google products. A reader who compares the 2023 sentence to the 2026 update without reading the 2023 context will overstate the reversal. The accurate statement is that a specific, prominent commitment about a specific product was made, and the current behaviour of a differently-named successor feature is inconsistent with the natural reading of it.

The community's read

Engagement from a last30days run: 35 evidence items across Hacker News, Reddit, YouTube and GitHub. Hacker News returned 9 stories with 3,980 points and 2,230 comments. Reddit returned 8 threads with 2,917 upvotes and 579 comments across r/google, r/privacy and r/artificial.

The second comment is the one that suggests this is a real lived change rather than a policy curiosity:

"Really frustrating that our privacy eroded to the point anyone would think this is reasonable. But it does explain some conversations with Gemini when I wonder why it's talking about particular things. Like asking it about consultation p..."

That is a user describing unexplained personalisation in a Gemini conversation and now having a mechanism for it. The community reaction was largely resignation rather than surprise:

"All your data feeds the A.I. at this point. I mean we were always data sets but nothing is off limits anymore. Even this will be fed to the machine."

"Because it's not (and never has been) about the children."

"It's worse than that. Google Photos data is used to infer your interests, relationships to people in your photos, and where you've been, including by associating your face with corresponding location data and timestamps."

What would falsify this

  • Google removes the human review of Connected Apps data from Help Answer 16836988 and from the Gemini Apps Privacy Notice, or narrows the "a subset of Connected Apps data" language to exclude Connected Apps content. That would make the 2026 reversal a temporary policy rather than a structural change.
  • The Personal Intelligence feature or its Connected Apps scope is withdrawn or restricted by a regulator, or the feature is limited to specific countries or account types in a way that excludes most consumer accounts.
  • The GitHub reproduction is withdrawn, or its author publishes a retraction, or a second independent tester reproduces the same four ingestion states and confirms the ambient trigger without an explicit @ tag.
  • Google confirms that ambient triggering is intended behaviour and documents it. That would not change the fact that reviewers can see the file, but it would move the story from a documentation gap to a design choice.
  • Google's "limited circumstances" language is applied in practice such that the full-file ingestion state does not occur for Connected Apps content, for example because summaries are always generated before review.
  • A published rate for what fraction of chats are reviewed, or what fraction of Connected Apps data reaches training, replaces the current "a subset" phrasing. Any such number would settle the scale question that this dossier could not.

Where this could be wrong

This post is built on Google's own documentation, which is the best available source for what the policy says and the worst available source for what actually happens. Every claim about the policy comes from Google's own pages, read directly, including the warning sentence and the enumeration of what reaches reviewers. The one thing that is not Google's is the reproduction repository's claim that an ambient mention, with no @ tag, triggers the retrieval. That is a single third-party test, and the repository itself is careful about the single-draw problem. If it does not replicate, the story reduces to a documented policy that users opt into and a warning they have to read.

Keep Activity off does not stop human review entirely. The Privacy Hub is explicit: even with Keep Activity off or temporary chats, Google still uses chats to protect Google, its users and the public, including with help from human reviewers. The obvious mitigation does not eliminate the exposure.

Training use is a separate exposure from review. The Help page says Connected Apps data is used to "improve Google services, including training generative AI models, for everyone". That is a distinct consent from human review, and the user toggles are described as settings-dependent without the page enumerating the mapping. The granularity of the actual controls is not something the documentation makes clear.

"Limited circumstances" is doing a lot of work in the blog edit. The Privacy Hub says "A subset of chats" without publishing the subset rate. The repository claims that in the observed case the payload reaching the reviewer is the file or the email, not a summary. The tension between "a subset of chats" and "the file itself" is the part that a reader should find unresolved.

When Personal Intelligence with Connected Apps first shipped to consumer accounts is not established in this dossier. The community reaction on 9 and 10 November suggests a recent change, but that is inference. The Help page's last-updated date for the Privacy Hub is 26 October 2026, and the blog edit is 16 October 2026.

No published figure exists for what fraction of chats are reviewed, what fraction of Connected Apps data reaches training, or how often ambient ingestion fires. Google does not publish these. Anyone claiming a rate is guessing. The privacy hub has an FAQ on legal bases for EU and UK data protection law. The tension between a 2023 no-human-review commitment, a 2026 reversal, and automated decision-making obligations is obvious, but I have not read Google's legal-basis answer or any regulator's view. A post making a legal claim needs that section read and probably a lawyer.

On this page

Sources

  1. Our responsible approach to building guardrails for generative AIGoogle, 2023
  2. About personalization with Connected AppsGoogle, 2026
  3. Gemini Apps Privacy HubGoogle, 2026
  4. thisisme6598/gemini_files reproduction repositorythisisme6598, 2026

Frequently asked questions

Did Google start reading everyone's email?

No. The 2026 change applies to consumer Google accounts that opt in to Personal Intelligence with Connected Apps, which connects Gmail, Drive, Docs and other services to Gemini. Google Workspace commercial accounts operate under separate Cloud Data Processing Addenda that contractually exclude human review and external generative training by default.

What did Google promise in 2023?

In October 2023 Google's VP of Trust and Safety wrote that if you chose to use the Workspace extensions in Bard, your content from Gmail, Docs and Drive was not seen by human reviewers, used by Bard to show you ads, or used to train the Bard model.

What does the 2026 edit say?

The edit, added inside the original 2023 paragraph on 16 October 2026, says that as Google has added features letting users connect Workspace apps to other Google services, that same subset of data can be used to train generative AI models depending on a user's settings, and can be subject to human review in limited circumstances.

Can reviewers see the whole file?

Help Answer 16836988 states that in some cases, where the email or file is brief or particularly relevant to the prompt, the summary may just be the email or file. Google also says reviewers are specially trained teams who can access the content only for the purposes described, and that chats are disconnected from the account before being sent to service providers.

Does turning off Keep Activity stop human review?

No. The Privacy Hub states that even with Keep Activity off or temporary chats, Google still uses chats to protect Google, its users and the public, including with help from human reviewers.