ChatGPT Users Report Cross-Account Chat Leaks Amid Security Concerns

ChatGPT Users Report Cross-Account Chat Leaks Amid Security Concerns

A growing number of ChatGPT users are reporting a baffling and unsettling phenomenon: private conversations from other accounts appearing in their own chat histories. The issue, first brought to light on Reddit by user /u/Atlasdubs, involves unsolicited chat threads—primarily centered on prenatal vitamins and women’s health supplements—that users did not initiate, nor have any connection to. These chats, often beginning with the phrase “do not update memories,” appear in real time, even after users log out of all devices, reset passwords, and revoke API keys.

According to the affected user, the chats remain visible only if the browser tab is left open; refreshing the page causes them to vanish from the history list, yet clicking on the hidden thread still displays the full conversation. This behavior suggests a synchronization or caching anomaly rather than a traditional data breach. OpenAI’s automated support initially dismissed the issue as a potential account compromise, but the user’s rigorous security measures—including two-factor authentication and no suspicious browser extensions—rule out common attack vectors. The persistence of the issue across both web and mobile platforms further indicates a systemic flaw.

While OpenAI’s official website, chatgpt.com, emphasizes user control over chat history and data privacy, it provides no public documentation addressing cross-account data contamination. The company’s Privacy Policy states that user data is not shared across accounts, yet the nature of these incidents—repeated, patterned, and unexplained—raises serious questions about backend data routing or session management vulnerabilities.

Notably, the content of the leaked chats is highly specific and non-random: each follows a scripted format suggesting automated or bot-driven interaction, possibly tied to market research or affiliate marketing campaigns. The consistent use of the phrase “do not update memories” implies an attempt to disable persistent learning or memory features, a functionality OpenAI has publicly restricted since 2023 to enhance privacy. This raises the possibility that these chats originate from a compromised or misconfigured third-party integration, or from a testing environment where user data was improperly isolated.

Despite the lack of public reports from other major outlets, the pattern described by Atlasdubs mirrors anecdotal accounts emerging in niche tech forums. While Chinese tech community Zhihu discusses ChatGPT’s general functionality and usage trends, it offers no insight into this specific security anomaly, underscoring the isolated nature of the issue—or the lack of public disclosure.

OpenAI has yet to issue a public statement regarding these reports. Internal support responses have been generic, citing standard security advice without acknowledging the possibility of a platform-level flaw. This lack of transparency is concerning, particularly as users rely on ChatGPT for sensitive personal and medical inquiries. If user data is being inadvertently routed between accounts—even in limited, non-persistent ways—it undermines the foundational trust in AI-powered services.

Security experts recommend that users avoid sharing personally identifiable information via ChatGPT until OpenAI provides a formal investigation and remediation plan. Independent researchers are now analyzing chat metadata patterns to determine whether the leaked conversations share common timestamps, IP signatures, or session IDs that could trace the origin of the leak. Until then, the phenomenon remains an unexplained glitch—one that may reveal deeper vulnerabilities in how AI platforms manage and isolate user data at scale.

As the AI industry accelerates toward mass adoption, incidents like these highlight the urgent need for verifiable data isolation protocols. Users deserve more than automated replies—they deserve assurance that their conversations remain their own.