DeepSeek User Conversations Appear in Google Search Results via Publicly Shared Links
Conversations between home users and the Chinese AI service DeepSeek, including many in Russian, have been discovered in Google search results. Accessing another person’s dialogue with the model requires only a specially crafted search query.
The pages in question are Shared Conversations — dialogues that users voluntarily published via public links. Every question, answer, and the titles of any uploaded documents are visible on these pages, as verified by a TASS correspondent. Journalists were unable to download the actual files, even by inspecting the page source code.
Representatives of MWS AI stated that no new data leak has taken place. They noted that search engines had already indexed thousands of publicly shared chatbot dialogues more than a year ago. No reports of a compromise of DeepSeek or unauthorized access to private conversation histories have emerged.
Most likely, the indexed pages are either old conversations or ones that users deliberately made public. It remains impossible to obtain access to a user’s account or private chats through these links. In effect, DeepSeek did not open doors to personal accounts; users themselves left certain conversations publicly accessible, and Google simply catalogued them.
In parallel, Yandex confirmed that links to dialogues with its Alice AI assistant are blocked from search-engine indexing. Such links are created only at the user’s initiative, remain valid for 14 days, and can be revoked at any time. Attached files are never transmitted to the recipient, and continuing another user’s conversation stays private.
Related articles
Maximizing iPhone Privacy: Essential Settings to Enable, Disable, and Verify Immediately
The article provides a detailed guide on strengthening iPhone privacy by limiting unauthorized access to messages, location data, photos, and cloud backups. It explains how to set a strong alphanumeric passcode, enable Stolen Device Protection, and restrict lock screen notifications and widgets. Users are advised to review Apple ID security, enable Advanced Data Protection for iCloud, and minimize app permissions for location, contacts, and camera. Additional steps include turning off cross-app tracking, using private Wi-Fi addresses, and activating Lockdown Mode for high-risk scenarios. The guide emphasizes regular updates, encrypted local backups, and periodic audits of shared access and active sessions to maintain long-term protection.
Top 10 Secure DNS Servers for Privacy, Threat Blocking and Ad Filtering in 2026
Public DNS resolvers differ significantly in their ability to block malicious domains, filter advertising and tracking, respect user privacy, and support modern encryption protocols. The guide evaluates ten services including Quad9, Cloudflare, AdGuard DNS, NextDNS, Control D, CleanBrowsing, Mullvad DNS, DNS4EU, Google Public DNS and DNS.SB, providing IPv4 addresses, DoH and DoT endpoints, and recommended use cases. Key distinctions include Quad9’s focus on phishing and malware blocking without logging, Mullvad’s strict no-logs policy requiring encrypted protocols only, and DNS4EU’s EU-based infrastructure with mandatory court-ordered blocks. The article explains why DNSSEC and encryption alone are insufficient and outlines four practical selection criteria: threat filtering quality, data-handling practices, encryption support, and network stability. Detailed configuration instructions cover Windows 11, Android, iOS, and home routers, along with verification methods and warnings against mixing providers with conflicting policies.
WebRTC IP Leaks Explained: Why Disabling the Protocol Harms Anonymity in Anti-Detect Browsers
The article from Aurorium details how WebRTC technology can leak real IP addresses even when users route traffic through proxies. It explains the peer-to-peer mechanics of WebRTC, the role of STUN servers in generating ICE candidates, and why standard TCP proxies fail to handle UDP traffic. Disabling WebRTC via flags or JavaScript extensions creates detectable anomalies that anti-fraud systems flag as non-standard environments. The recommended approach involves native emulation inside the browser kernel so that STUN requests return proxy IPs while preserving full API integrity across workers. Additional leaks through local network addresses, mDNS candidates, and IPv6 are also covered with practical verification methods using tools like BrowserLeaks and CreepJS.
Docx Anonymizer: Open-Source Chrome Extension Uses Fine-Tuned rubert-tiny2 to Anonymize Personal Data Before AI Uploads
A Russian developer has released Docx Anonymizer, a browser extension that automatically detects and replaces personal data in documents using a lightweight NER model before they reach public AI services such as ChatGPT. The tool was created to help organizations comply with Russia’s 152-FZ personal data protection law while avoiding the risks of uploading contracts and other sensitive files to cloud-based LLMs. It runs entirely locally via ONNX Runtime and WebAssembly, requires no network calls, and supports any AI chat interface. The underlying model, rubert-tiny2, was further trained through knowledge distillation on WikiANN, factRuEval, and synthetic business documents, reaching strong F1 scores for person and organization entities after int8 quantization. The extension intercepts text on the fly, performs named-entity recognition in under two seconds for typical contracts, and replaces detected entities with placeholders. The project is fully open source and designed for minimal user friction, addressing the growing problem of employees inadvertently leaking corporate and personal data to public AI platforms.