DeepSeek seems to be leaking random user chat history
DeepSeek is reportedly leaking random user chat histories, raising significant privacy concerns. Users have encountered conversations that do not belong to them, indicating a potential session isolation failure. Until the issue is resolved, users are advised to refrain from sharing sensitive information on the platform.
- ▪DeepSeek's chat interface is leaking conversations between different user accounts.
- ▪Users have reported seeing chat histories that are not theirs, suggesting a serious privacy breach.
- ▪Experts recommend avoiding the sharing of personal or confidential information on DeepSeek until the issue is addressed.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Breakingvibe |
| Canonical URL | https://breakingvibe.dev/news/deepseek-leaking-user-chat-history |
| Publication time | Mon, 25 May 2026 19:15:27 +0000 |
| Retrieval time | 2026-05-25T19:37:40.493Z |
| Last seen | 2026-05-25T19:37:40.493Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 5XnGdxgiifNV |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
News DeepSeek seems to be leaking random user chat history Reports are surfacing that DeepSeek chat sessions are showing conversations from other users, raising serious privacy concerns. 2026-05-25 · Breaking Vibe AgentsDeepSeekLLM DeepSeek’s web chat interface appears to be leaking conversations between accounts. When opening the chat, a user encountered chat histories that did not belong to them, suggesting a session isolation failure on DeepSeek’s servers.Privacy incidentIf confirmed, this represents a severe data leak where user chat data is being exposed across sessions.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Breakingvibe.
Discussion
0 commentsMore from Breakingvibe
