Skip to content

Are humans reading ChatGPT chats? Set boundaries, don't panic

The Project Lily report says human reviewers see real ChatGPT conversations. This is not a mass data leak, but it is a useful reminder that a chat box is not a vault.

Sourceverified
  1. [01]404 Media — Inside Project Lily2026-09-22
  2. [02]TNW — Contractors reportedly reading ChatGPT conversations2026-09-22
  3. [03]OpenAI — How your data is used to improve model performance2026-09-22
  4. [04]OpenAI — Data Controls FAQ2026-09-22
  5. [05]OpenAI — Temporary Chat FAQ2026-09-22

A Project Lily investigation by 404 Media says hundreds of contractors rate model responses using real ChatGPT conversations. According to the report, reviewers do not see usernames and a privacy filter attempts to remove personal information first. Some sensitive details and user memory summaries may still reach reviewers.

The distinction matters: this is not a report that every ChatGPT conversation was dumped onto the public internet. There is no public database of everyone's chats. The reported issue is controlled human access inside a model-improvement process reaching conversations that users may have assumed were more private. That is different from a mass breach, but it still deserves attention.

Should this surprise us?

A little. Not completely.

Assuming that text sent to a consumer cloud service stays sealed between your device and an algorithm was always optimistic. Email, cloud storage, social platforms, support tickets, and error logs have long passed through automated systems, service providers, and sometimes authorized people. AI chat feels different because people tell it things they would never type into a search box.

We use the same interface as an editor, tutor, therapist, doctor, lawyer, colleague, and confidant. The box looks the same, so every conversation starts to feel equally safe. It isn't.

OpenAI's own help pages say eligible content from personal ChatGPT accounts may be used to improve model performance, and users can opt out for new conversations. Human review is uncomfortable, but the broader idea that consumer conversations may support model improvement is not entirely new or hidden. The sharper question is whether the process was explained clearly enough and whether human access matches what users reasonably expected.

"Everything is already online" is not a privacy policy

There is some truth in that phrase. Phone numbers sit in company databases, shopping history lives with retailers, location data goes to apps, and private messages live on messaging services. Leaving no digital trace is not realistic.

That does not make every disclosure harmless. Risk compounds. Age, city, job title, a health condition, and a family detail may look ordinary on their own. Put them in one conversation and they can form a useful identity profile without a password or passport number ever appearing.

I do not see this as a reason to abandon the internet or AI. Wearing a seat belt does not require hating cars. The useful move is to match the data you provide to the value you receive.

What I would and would not paste

ChatGPT is still useful for lower-risk work: simplifying a draft, organizing ideas, building a general learning plan, discussing a problem after removing personal details, or generating example code.

I would not paste:

  • Passwords, API keys, card details, or identity documents
  • Customer names, phone numbers, addresses, or order-level personal data
  • Unreleased company financials, contracts, or access credentials
  • A complete private conversation that belongs to someone else
  • Identifying details around health, legal, or family matters

Most tasks survive abstraction. Instead of naming a person, hospital, employer, and diagnosis, ask which questions an adult with a certain symptom could raise with a doctor. Replace real company names, figures, and customer details with placeholders. You keep most of the utility without exporting unnecessary context.

I use the same boundary logic in my coding-agent permissions guide: do not decide whether to trust a tool in absolute terms. Give it the access and data the task requires. As I wrote in my 2026 AI notes, the real skill is knowing what to delegate and what to keep with yourself.

A two-minute settings check

On a personal ChatGPT account, check Settings > Data Controls > "Improve the model for everyone." OpenAI says turning it off prevents new conversations from being used for model improvement.

Temporary Chat is a better fit for a one-off conversation that needs less persistence. OpenAI says temporary chats do not appear in history, do not create memories, and are not used to improve models, although a copy may be retained for up to 30 days for safety purposes.

Neither option is an invisibility cloak. Any online service can retain operational, legal, or security-related traces. Still, disabling optional training, cleaning old history, and removing sensitive details before sending them materially lowers the risk.

A calmer conclusion

The Project Lily report is not a reason to delete ChatGPT tonight. It is a reminder that a warm, personal chat interface is still a product running on somebody else's servers.

Treating every sentence like a state secret would make the tool useless. Treating the box like a private vault creates avoidable risk. The sensible middle is to use it for ordinary thinking, writing, and building while keeping irreversible secrets, other people's data, and directly identifying sensitive details out whenever possible.