AI conversations indexed by Google: when was confidentiality actually broken?
Over the weekend of 26 July 2026, hundreds of conversations shared from Claude
were readable in Google results. A site:claude.ai/share query was enough to
browse them. According to press reports, they included exchanges about lawyers’
legal strategies. Anthropic de-indexed the pages by the Sunday.
No vulnerability was exploited
The “Share” button did exactly what it says: create a public page. It was
missing a noindex tag, and Google indexes what is public. That is its job.
The summer of 2025 produced the same episode at ChatGPT. Both providers fixed it quickly.
The exact moment the undertaking stops being honoured
Suppose one of those conversations contains client data you contractually swore never to disclose.
The undertaking stopped being honoured the day the file entered the prompt. Indexing, which happened weeks later, merely made it visible. Sharing and discovery belong to the same chain: they expose an exit that had already happened.
That distinction has a practical consequence. Auditing what leaked after the fact restores nothing. The only point of action sits before the send.
The trajectory matters more than the provider
Data that leaves your machine enters a chain you no longer steer: the provider’s storage, its sharing settings, its HTTP headers, indexing by a third-party engine. One missing HTML tag is enough to turn it into a public page.
None of those steps belong to you. Switching provider moves the chain without handing you control of it.
What stays in your hands
One variable remains under your control: what the prompt contains at the moment it leaves.
That is the principle of reversible redaction running on your own machine. The model receives the structure of the file, the facts, the legal question. It receives no name, no number, no address. The table linking each token to its real value stays on your computer.
If the page ever becomes public, it contains nothing to disclose.
Source: Cybersecurity News, 27 July 2026.