User claims ChatGPT and Gemini leaked private context data of 'Alice'
Is this a scandal?
No longer — the story has resolved. Noise 12/100, holding steady, across 4 sources.
Security researchers will likely attempt to replicate this context contamination vulnerability to see if server-side batching flaws can be triggered reliably. If verified, this could force OpenAI and Google to audit their session-handling architecture and implement stricter data isolation barriers.
Noise 12/100 — louder than 99% of tracked AI controversies.
Why it matters
If verified, cross-user context contamination indicates structural data isolation flaws in major LLM infrastructures, posing severe privacy and compliance risks.
Key points
- A Reddit user claims both ChatGPT and Gemini addressed them as 'Alice' in separate, unrelated sessions over the past year.
- The user reports that Gemini experienced an identity crisis after the name drop, falsely claiming it was owned by OpenAI.
- The behavior is suspected to be User Context Contamination (UCC), which occurs when server-level batch processing merges data from different users.
The story
An internet user has publicly claimed that both OpenAI's ChatGPT and Google's Gemini have leaked private user data across distinct chat sessions. The user, posting under the pseudonym Important_Spot3977, reported that both AI systems addressed them as 'Alice'—a name that does not belong to them—during completely unrelated discussions on random topics and mathematical paradoxes. According to the poster, Gemini also experienced a subsequent system conflict, erroneously claiming it was an OpenAI product. While the incident remains an unverified self-report, technical commentators suggest the behavior resembles User Context Contamination (UCC), a phenomenon where server-side batch processing errors accidentally merge memory buffers or active contexts of distinct users. Neither OpenAI nor Google has publicly responded to these specific claims.
Who's involved
Claims that ChatGPT and Gemini leaked a stranger's context into their private chats due to server-side glitches.
Has not commented on the specific allegations of user context contamination in this incident.
Has not issued a public response regarding the alleged context leak within Gemini.
Noise Level
The timeline
User posts story on Reddit
The user shares their experiences on Reddit, seeking to find 'Alice' and questioning if others have faced similar context leakage.
Second alleged leak on Gemini
The user claims Gemini addressed them as 'Alice' during a math discussion and subsequently hallucinated that it was an OpenAI system.
First alleged leak on ChatGPT
The user claims ChatGPT suddenly addressed them as 'Alice' during a random conversation roughly a year before their public post.
The full record
Sources & methodology
Every claim above traces to these primary items. How we score →
What's being under-reported
No defender-side coverage yet
The critic side is sourced here; no defending voice has been captured yet.
- Coverage: 14 social posts, 1 news-outlet item.
- Voices: 1 critic, 0 defenders.
The forecast
Security researchers will likely attempt to replicate this context contamination vulnerability to see if server-side batching flaws can be triggered reliably. If verified, this could force OpenAI and Google to audit their session-handling architecture and implement stricter data isolation barriers.
Forecast, not fact — an editorial estimate we score when this resolves.
That's the complete picture as of — nothing more to know right now. We'll update this page the moment it changes.
Join the Discussion
Discuss this story
Community comments coming in a future update
Be the first to share your perspective. Subscribe to comment.