🏠 All tools

← Using AI When It MattersEspaΓ±ol

What to Never Tell an AI

Talking to an AI usually means typing into someone else's system. Most of what you type is fine β€” but a short list of things, once sent, you can't take back.

General guidance for using any AI assistant β€” not a review of any specific tool. Practices differ between services and change often; when in doubt, share less.

When you chat with an AI, your words usually travel to a company's servers β€” where they may be stored, sampled by human reviewers for "quality," used to train future versions, or exposed in a leak. For everyday questions, none of that matters. But some information, once you've pasted it in, can't be un-pasted β€” and a simple habit about what not to send saves you from the regret.

The one idea: treat anything you type into an AI like a postcard, not a diary β€” assume it could be stored, seen by a stranger, or learned from. Some things just don't go on a postcard.

Where your words can go

Stored and sometimes reviewed

Many services keep your conversation history, and some have staff review samples to improve the product. Assume a human could read what you wrote.

Used to train future versions

Your inputs may help train the next model β€” which can, in rare cases, surface fragments to other people. What you teach it doesn't always stay yours.

Leaks, bugs, and shared devices

Stored data gets breached; chat histories have been exposed by bugs; and your history may sit in your account or on a shared/public computer for the next person.

"Free" often means you're paying in data

If a tool is free, your inputs are more likely to be part of the bargain. Read what the setting says, and assume the most data-hungry default unless told otherwise.

Don't paste these

Keep these out of any AI chat (unless it's a tool you specifically trust, and need, for exactly that):

Get the help without the exposure

You almost never have to choose between AI's help and your privacy β€” a little prep gives you both.

  1. Redact before you paste. Swap real names, numbers, and addresses for placeholders β€” "[NAME]", "[ACCOUNT]", "$X". The AI can still explain the clause or draft the letter around the blanks.
  2. Ask the general version. "How do disputes like this usually work?" gets you most of the value without uploading your whole file.
  3. Turn off history and training where offered. Many tools let you disable chat history or "improve the model" β€” do it for sensitive work, and delete sensitive chats after.
  4. Match the tool to the stakes. For sensitive tasks prefer a service that says it doesn't train on your inputs β€” but still don't paste outright secrets, even there.
  5. Clean up on shared devices. Log out and clear the history on any phone or computer that isn't only yours.
  6. When in doubt, leave it out. You can always give the one private detail to a human professional instead of typing it into a chat box.

Your "before I paste" kit

Tick before sending anything sensitive.

The close

None of this means clamming up β€” AI is genuinely useful, and most of what you ask it is harmless. It means keeping one small reflex: before you paste, glance at whether there's a password, an ID, a financial number, or someone else's secret in there, and take it out. The help you get from redacting "[NAME] owes me $X" is identical to pasting the real thing β€” minus the part you can't take back. Postcard, not diary. When you're weighing whether an answer is even safe to rely on, run the trust check.

Free and public domain (CC0) β€” copy it, translate it, share it. No accounts, no tracking; it runs entirely in your browser, and nothing you tick is saved or sent. Practical privacy judgment, not legal advice; each service's data practices differ and change β€” share less when unsure.

Last reviewed: June 2026. This is general information that can age β€” verify time-sensitive specifics (laws, numbers, programs, app menus) against current official sources.