Are Your Shared Claude Chats Public? How to Check and Revoke Them

Last updated: July 2026

If you have ever pressed Share on a Claude conversation, assume that conversation was publicly findable and go check it now. Between July 25 and July 27, 2026, shared Claude chats and published artifacts turned up in ordinary Google results, reachable by anyone who ran a search rather than only by people holding the link. Google has since cleared them.

The search results are gone. The pages are not. A share link stays live at its original address until its owner deletes it, and that is the only step that actually closes the exposure. This guide covers what happened, why the fix was counterintuitive, and the exact click path to audit your shares in Claude, ChatGPT, and Gemini.

What Happened, and What Did Not

This was a search indexing failure, not a security breach. No account was accessed without permission and no private conversation was pulled out of anyone's history.

On July 25, 2026, a Reddit user posted to r/ClaudeAI showing that a plain Google query restricted to the claude.ai/share path returned page after page of other people's conversations. Within a day, further posts extended the finding to published artifacts, meaning the dashboards, documents, and small web apps built inside Claude were also listed. Reported content included resumes with real names and phone numbers, API keys, internal project detail, a lawyer's working notes, and material that appeared to include Social Security numbers.

Asked about it, an Anthropic spokesperson said the company gives users control over sharing and does not supply "chat directories or sitemaps with search engines". The company's position is that share links cannot be guessed or discovered unless a user distributes them, and that publishing a conversation makes it public web content that third parties may archive. Google results had largely cleared by July 26 and 27.

Be careful with the counts circulating this week. Reported figures range from hundreds to thousands and none has been independently verified. A separate Claude incident in September 2025 drew a Google estimate of just under 600 transcripts, and that number is now being recycled into this week's coverage. Two incidents, eleven months apart.

Why "Anyone With the Link" Is Not the Same as "Not Findable"

A share link creates a public web page, and only the platform decides whether search engines are permitted to list that page. The user who clicks Share has no say in it and usually no idea the question exists.

The robots.txt trap

Two different instructions govern how a page behaves in search, and they are frequently confused. A robots.txt file tells crawlers which addresses they are allowed to fetch. A noindex rule, placed inside the page or in its HTTP headers, tells crawlers not to list it. Google's own guidance is direct on the point: robots.txt manages crawler traffic and is not the right tool for keeping a page out of search results, because a disallowed address can still be indexed when other sites link to it.

Now the part that turns a small mistake into a large one. For a noindex rule to work, the crawler has to fetch the page and read it. Google's documentation states that when a page is blocked by robots.txt, the crawler never sees the noindex rule at all, and the page can still appear in search results if other pages link to it.

That is the trap, and it is genuinely counterintuitive. Blocking the crawler feels like the stronger protection. It is the weaker one, because it removes the only channel the stronger instruction travels through. The lock was good enough to seal the instructions inside with the secret. The reported remedy this week was to stop blocking the crawl so the noindex could finally be read — which is the same fix web publishers apply to their own sites constantly, ModemGuides included.

How Google found the links in the first place

Not by guessing. Share URLs carry long random identifiers that are not realistically brute-forced. Search engines find pages by following links, so every time someone pasted a share link into a public forum, a social post, or a code repository, that address entered the crawl queue. Anthropic's account and the technical account agree: people shared the links in public, and the index did the rest.

How to Check and Revoke Your Shared AI Chats

Every major assistant keeps a list of the public links you have created, and deleting the conversation does not delete the link. That single fact is the most common misunderstanding here, and the reason people who cleaned up their history are still exposed.

Claude

1. Open Claude and go to Settings.
2. Select Privacy.
3. Open Shared Chats.
4. Review every entry and delete anything holding names, addresses, credentials, client detail, medical or legal material, or code you do not own.

Artifacts are separate. Anything published from an artifact or a design canvas carries its own visibility state, so open each one and set it back to private. Menu labels shift between updates; if a heading here does not match what you see, look for "shared" or "published" inside Settings.

ChatGPT

1. Open Settings.
2. Go to Data Controls.
3. Open Shared Links, then Manage.
4. Delete links individually, or clear the whole list.

OpenAI removed its "make this chat discoverable" checkbox in August 2025 after the same problem, its security chief calling the option "a short-lived experiment" and the company working with search engines to pull the indexed pages. Links created before that change still exist until you remove them.

Google Gemini

1. Open Gemini in a browser. The control lives in the web app rather than the phone app.
2. Click Settings and help, or your profile picture, then Settings.
3. Open Your public links.
4. Delete each link you no longer want live.

Google's own documentation on sharing Gemini chats spells out the same trap: switching sharing off does not retract links you already made. They stay reachable until deleted from the app.

Everything else

The same rule applies wherever a share button produces a URL. Grok, Copilot, Meta AI, and Perplexity each keep some equivalent list under a different label, so search settings for "shared," "public links," or "published." If a product mints public URLs and gives you no list of the ones you have made, learn that before you use the feature, not after.

Deindexing Is Not Deletion

A page disappearing from Google does not mean the page is gone. Three separate things were in play this week and only one of them is finished.

• Google stopped listing the pages. Largely complete by July 27, 2026.
• Other engines run their own recrawl schedules. Reporting through the week indicated Bing was slower to clear.
• The pages themselves stayed live at their original addresses, readable by anyone holding the link, until their owners deleted them.

On top of that, anything publicly reachable during the exposure window could have been copied. Screenshots, bookmarks, caches, and third-party archive collections were assembled while the pages were listed, and none of that is recallable by Anthropic or by Google. So the order of operations matters: revoke the link at source first. Search results are downstream of the page, and they resolve themselves once it is gone.

The Same Mistake, Four Products, Five Times

This is not a Claude defect. It is a category defect, and Claude is the fourth product to hit it and the only one to hit it twice.

Status as of July 27, 2026. Counts reported for the July 2026 incident range from hundreds to thousands and none has been independently verified.

The Rule That Actually Protects You

Treat a share link as publishing, because that is precisely what it is. Sending a file and publishing a web page feel identical inside a chat window — one click, one URL either way — and they are not the same act at all. One puts a copy on your recipient's device. The other creates a document on a company's server that any holder can read and reshare, for as long as that company keeps it up.

Three habits follow from that:

• Assume every share link is permanent. You can revoke access. You cannot revoke what was already read.
• Never share a conversation containing anything you would not post. Start a clean chat and paste in only the part meant to be seen.
• Audit quarterly. Share lists accumulate the way bookmarks do, silently and past the point of memory.

Underneath the habits sits the structural point. A cloud assistant is private by policy. That policy is usually written in good faith, and it can still be undone by a configuration change, an acquisition, a subpoena, or one line in a robots.txt file that nobody outside the company will ever read. A model running on your own hardware is private by architecture. There is no share URL because there is no server-side page, and nothing to index because nothing was ever published.

The honest limit, stated plainly: a local model does not replace a frontier assistant for most daily work, and anyone claiming otherwise is selling something. What it does is delete the publishing surface entirely for work that should never have left the building — contracts, client files, patient notes, credentials, code you do not own. A machine with 24GB of video memory handles that class of work today, and our guide to the best hardware for running local AI models covers what that costs at every budget tier.

For everything you keep doing in the cloud, the fix is the habit rather than the hardware. To reduce how much AI runs on your devices in the first place, our walkthrough on turning off AI features across Windows, Samsung, Google, Meta, and Alexa handles the prevention side of the same problem.

The wider pattern is worth keeping in view. Indexed share links are one way conversational data escapes; hidden trackers are another, as the class action filed against Perplexity over user data sharing alleges. The common thread is not malice. It is that convenience features get built faster than the controls that would make them safe, and the person carrying the risk is never the person who shipped them.

Frequently Asked Questions

Was this a data breach?

No. A breach means someone gained unauthorized access to systems or accounts, and nothing like that happened. Every conversation that appeared in Google was one whose owner pressed Share, which creates a public web page by design. The failure was that those pages became findable by search rather than only by link. That distinction changes what you should do about it.

Are my Claude chats private if I never used the share button?

Yes. Conversations stay private to your account by default and were not involved. Only chats and artifacts a user explicitly published were affected. If you have never pressed Share or published an artifact, there is nothing to revoke. Checking anyway takes a minute and is worth doing, since share links accumulate quietly over months of ordinary use.

Does deleting a conversation delete the shared link?

No, and this is the most common misunderstanding of the whole episode. On Claude, ChatGPT, and Gemini alike, a share link points at a published snapshot that exists independently of your chat history. Deleting the conversation, or switching off activity history, leaves the public page live. You have to delete the link itself from the shared-links list inside settings.

Can I get an indexed page removed from Google search?

Google offers a removal request tool, but it is built for pages you control, and you do not control the host of a shared AI chat. The durable move is deleting the share link. Once the underlying page stops resolving, the result drops out at the next recrawl. Requesting removal without deleting the link leaves the page live for anyone holding the URL.

Does a VPN protect me from this?

No. A VPN encrypts traffic between your device and a VPN server. It has no bearing on a page you chose to publish on somebody else's website. Once a conversation exists as a public URL it is an ordinary web page, and any visitor can read it regardless of how either of you reached it. VPNs solve a real problem, but not this one.

Is ChatGPT or Gemini safer than Claude here?

Not meaningfully. All three turn a share button into a public web page, all three keep that page live until you delete the link, and versions of this indexing problem have now hit Bard, ChatGPT, Grok, and Claude twice. Treat the share feature identically in every product: as a publish button wearing a friendlier label.