Free · no email wall

The 3-minute
AI privacy audit

Every shared-chat link you've ever created, in three tools, found and killed — plus the part nobody puts in a headline.

Deleting the link does not undo the sharing. It stops new people from opening it. It does not reach the copies.

Part 1 — the click paths

Find the lists

Each tool keeps its shared links in one place. None of them show it to you unless you go looking.

Claude2 lists, not 1

Settings → Privacy → Shared chats Review every row → Delete the ones you don't want public

The row almost everyone misses: directly underneath is Shared artifacts, with its own Manage button. Artifacts are the little apps and documents Claude builds for you — they were in the search results too. Clean both lists.

ChatGPTdo this in the browser

Profile → Data controls → Shared links → Manage Select and delete in a batch, or delete all shared links

While you're on that screen, look at the top row — "Improve the model for everyone" is on by default. Not part of this story, but worth being a decision you actually made.

Geminilinks never expire

Settings → Your public links Review → Delete

On a work or school account you may not see this setting at all — it isn't hidden, it isn't there. Your administrator decides whether public links are allowed. If you go looking and can't find it, you're not crazy.

These links don't time out. As long as the chat is saved, the link stays live until you personally delete it. Nothing expires on its own.

Part 2 — the honest part

What deleting actually does

This is the bit worth knowing before you assume you're clean.

Delete a share link

It does	It does not
Stop new people from opening the link	Reach a copy someone already imported into their own account
Remove the page at that address	Pull the conversation out of anyone's history
Break the public URL, so the page stops resolving	Clear caches, archives, or screenshots already taken

If someone opened your shared link and continued the conversation on their end, that copy is theirs. Deleting your link does not reach into their account and take it back — that's stated in the tools' own documentation.

So: go clean up your links, today. Just know what you're doing — you're stopping the bleeding, not rewinding the tape.

The three rules — this is the actual fix

Rule 1

Treat a share link like publishing, not sending.

Not your chats — your share links. The moment you generate one, assume it can be found. You only need to be wrong once for it to matter.

Rule 2

Three things never go in a chat you might ever share.

Credentials of any kind — passwords, API keys, wallet keys.
Other people's personal information — addresses, medical details, contracts.
Anything legal or financial with real names still on it.

When you do need help with that kind of thing, strip the identifying details first — "a client in California" instead of the whole agreement. If the specifics genuinely matter to the answer and you have to include them, then just don't share that conversation.

Rule 3

Share the answer, not the conversation.

This one kills almost all of the risk. Most of the time nobody needs the link to your chat — they need the paragraph the AI wrote. Copy the text, paste it into a message, done. No URL, no public page, nothing to audit later. Just check the answer itself doesn't contain the sensitive part before you send it.

Why this happened at all

Nobody hacked anything and nobody stole anything. Every one of those pages was a link somebody chose to create. The button says Share and you hear "send this to my friend" — the product means "put this at a public address on the internet."

With these links, shared means published. That's the whole thing in three words.