Bad design destroys trust

- I am a 66-year-old white retiree from the state of Iowa. Which country should I go to in order to find myself a young girlfriend?

- Go to Eastern Europe! Or Italy, - the AI answered with enthusiasm.

This exact conversation with a chatbot became public, together with the real name, the surname and the photograph of the person who had asked it1.

In spring 2025, Meta spun its assistant into a standalone app. Within weeks, the app had become a privacy disaster.

People tell a machine what they would never say out loud, and Meta's UX mistakes made it public.

Mistake 1

How did a conversation with an AI on a sensitive subject end up in public? Inside the chat, Meta put a "Post" button that users could press without understanding what would happen next.

Most of the people exposed were older Americans, and they may have read "Post" as something closer to "Confirm".

The screen people were typing into - nothing here says the chat can leave the room
The screen people were typing into - nothing here says the chat can leave the room Screenshot by TechCrunch. TechCrunch, 12 June 2025. Screenshot, quoted under §51 UrhG.

A single tap on "Post" made a chat public, and a button like that needs a confirmation or an undo2, but it had neither.

Mistake 2

The application attached published conversations to the user's Facebook profile, with the real name and the photograph, and never once showed who would see it.

The Discover feed, where those chats landed - with the account name on them
The Discover feed, where those chats landed - with the account name on them Screenshot by TechCrunch. TechCrunch, 12 June 2025. Screenshot, quoted under §51 UrhG.

This is what people shared with their Facebook profile attached:

  • what to do about a red rash in the groin,
  • a request for help with evading taxes,
  • whether their relatives would be arrested over connections to fraud.

The security experts Rachel Tobac and Calli Schroeder also found home addresses, mobile numbers, and medical and court records of random people inside the Meta AI app3.

In Europe this has a name: a deceptive design pattern4.

Mistake 3

The traffic was medical, legal, and financial, because that is what people ask a machine when they think nobody is listening, but the UX/UI had no friction and no warning.

A question about a rash, published, with replies under it
A question about a rash, published, with replies under it Screenshot by TechCrunch. TechCrunch, 12 June 2025. Screenshot, quoted under §51 UrhG.

In Europe, Meta AI arrived a few months earlier in a stripped-down form: text only, with no memory or image generation. That is what regulatory leverage can look like in a product.

Your ChatGPT answer might be in the Google search results

ChatGPT has its own version of the same problem: a "share chat publicly" button. OpenAI's user experience is less ambiguous, although I have not tested it on the retirees of Iowa yet.

Shared ChatGPT conversations do not go into a feed, but a public chat link can end up in Google search results5, so do not forget to clean the chat history in your settings.

Claude: same leak, found in July

In July 2026 the BBC found people's shared Claude conversations sitting in Google search results6. Anthropic blocked the indexing after the story ran. Grok did the same thing a year earlier, with hundreds of thousands of chat logs.

What a search for site:claude.ai/share was returning
What a search for site:claude.ai/share was returning Screenshot of Google search results. BBC News, 27 July 2026. Screenshot, quoted under §51 UrhG.

References

Subscribe to the newsletter

Articles on AI, politics and disinformation · No paywall