An indie developer says Google’s AI-powered Search gave a player the exact name of an unreleased Operation Octo character, a name the developer says existed only in a private Google Doc.
That sounds like a privacy breach.
The evidence available so far does not establish one. The result has not been independently reproduced, Google says private Docs are not used to train its foundational AI models, and no evidence shows how the Search system produced the name.
Evidence does not confirm a private-document leak
Klub Kofta Studio’s developer wrote on Reddit that a player asked Google’s AI-powered Search about future content from the game Operation Octo and received the name “Vantage Tripod.” The developer said the name had never been shared publicly, was not yet stored in the game’s serialized data, and existed in a Google Doc.
The player reportedly used an incognito browser session.
The developer later said the AI claimed it had made the name up when asked for a source. Attempts to reproduce the result also failed. The same player could not get the system to reveal the information again, and TechRadar said its own attempt produced only information from the public Reddit discussion.
Google also pushed back on the explanation. A spokesperson told TechRadar that information in private Google Docs is not scanned to train foundational AI models such as Gemini. Google said publicly shared Docs may be indexed if their links are exposed to search crawlers.
The company's Workspace privacy documentation similarly says Workspace data is not used to train or improve the underlying generative AI models that power Gemini, Search, and other systems outside Workspace without permission.
Google separately documents an opt-in Personal Intelligence feature for AI Mode that can use connected Google content to personalize responses. That confirms Google Search can use private account data in some circumstances, but it does not show that one user’s private document can appear in another person’s incognito search.
What teams should take from the claim
Several explanations remain possible. The name may have appeared somewhere public that the developer overlooked, the system may have inferred or hallucinated the exact phrase, or some sharing or integration path may have exposed information. The developer also said the length and context of the original conversation may have affected the response.
For organizations using Google Docs, this is not evidence of a confirmed Workspace breach. A sensible response is to review sharing permissions on sensitive files, check connected apps and AI personalization settings, and preserve the full prompt, response, citations, and access logs if a similar incident occurs.
Without a reproducible result or evidence linking the Search response to the developer’s private file, the Operation Octo case remains an unusual and unresolved AI output, not proof that Google leaked a private document.
Also read: xAI’s Grok Build was found sending complete Git repositories to cloud storage before a server-side change stopped the uploads.