Your shared Claude conversations may have ended up on Google

An important alert for Claude users: conversations and Artifacts (small projects created in chat) shared via link may have been indexed by Google. That is, something you thought only one person would see could appear in a public search. The problem happens because the 'share' button generates a public page on the internet — and public pages, without a technical block, are found and cataloged by search engines.

The sharing feature exists to make life easier: you send the link and the other person sees the conversation without needing an account. But many people use it without realizing that 'shareable link' means 'published on the web'. This isn't the first time this has happened in the sector — ChatGPT links have already gone through the same problem. With millions of people pasting personal texts into chatbots, search engines have become an accidental repository of other people's conversations.

For the Brazilian user, the risk is concrete: it's common to paste excerpts from contracts, resumes, work emails, and even personal documents into the chat to ask for a summary or correction. If that conversation is shared and indexed, data like name, CPF, and client information can be exposed — which even brushes against the LGPD, the data protection law. For those learning AI now, understanding what happens to what you type is as important as learning how to use it.

Imagine a lawyer who asked Claude to review a petition and shared the link with a colleague. Months later, when searching the client's name on Google, the conversation link appears in the results, with the case text open for anyone. To avoid this, the path is to enter Claude's settings, review the list of shared links, and delete what no longer needs to exist — old links remain live until they are deleted.

The practical rule is simple: treat the 'share' button as 'publish'. Before generating a link, remove names, documents, and client data; after using it, delete the link. It's also worth reviewing right now everything you've already shared on any chatbot. And observe the companies' next steps: the trend, after episodes like this, is to adopt indexing blocking by default — but until then, the last line of defense is your own care.