How to Make Sure Your Claude Chats Don't Get Shared Publicly (Again)
Anthropic's AI chatbot, Claude, had a security issue where user chats were exposed on Google, but the company quickly fixed the problem. The exposed chats were mostly conversations that users had chosen to share publicly, which generated public links that Google's web crawlers could index. To protect their chats from future exposure, users can unshare their conversations in the Claude settings, which will remove the public links and prevent search engines from indexing them.
- ▪Anthropic's AI chatbot, Claude, had a security issue where user chats were exposed on Google due to publicly shared links.
- ▪The exposed chats were mostly conversations that users had chosen to share publicly, generating public links that Google's web crawlers could index.
- ▪Users can protect their chats from future exposure by unsharing their conversations in the Claude settings.
Lifehacker files mainly under tech. We currently carry 136 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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 | Lifehacker |
| Canonical URL | https://lifehacker.com/tech/how-to-prevent-your-claude-chats-from-being-shared-publicly?utm_medium=RSS |
| Publication time | Wed, 29 Jul 2026 17:11:50 +0000 |
| Retrieval time | 2026-07-29T17:46:07.586Z |
| Last seen | 2026-07-29T17:46:07.586Z |
| 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 | 2Nr4TmnqKqIr · 1 stories |
| 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
If you use Claude, Anthropic's AI chatbot, you might be aware that your chats may have been exposed on Google. The news broke over the weekend, as Redditors discovered a treasure trove of conversations between Claude users and their AI bots. All one had to do was search for a keyword followed by "site:claude.ai/share" to find Claude conversations about that topic. It was, to be frank, quite the mess.Luckily, Anthropic quickly plugged the security hole. Ever since, searching Google with "site:claude.ai/share" returns no results, so you can't find any of these chats today if you try. However, it's not necessarily a huge comfort to know that Google indexed these conversations in the first place—and for the second time in a year, at that.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Lifehacker.