Before You Paste That Document into an AI Chat, Check These Four Things

You want help rewriting an email, understanding a document or summarising a personal problem. Uploading the original is convenient. It can also share far more information than the task needs.

Before pasting, check four things: what the document contains, which account you are using, what happens to the conversation and whether another service receives it. A setting that prevents model training does not necessarily mean no storage, no safety review or no external processing. These are separate questions.

Start with the task, not the entire document

Write down what you want the assistant to do in one sentence. Then identify the smallest amount of information needed to do it.

Suppose you want a calmer version of a complaint to a supplier. The assistant probably needs the disputed issue and your preferred outcome. It may not need your home address, account number, a complete purchase history or the names of everyone copied into the original email. You can replace these with descriptive labels before asking for a rewrite.

For a spreadsheet explanation, recreate the relevant formula using invented rows. For a presentation structure, describe the audience and argument instead of uploading a confidential strategy deck. These are editorial suggestions for reducing exposure; they do not transform sensitive data into something you are automatically authorised to share.

If removing details would make the answer useless, that is a reason to choose an approved environment, not to pretend the details do not matter.

Check the account and product

The same brand can have different rules for consumer accounts, employer-managed services and developer products. “We use this AI at work” does not establish that your personal account has the same terms or controls.

Anthropic's consumer training notice, dated March 2026, distinguishes its consumer products from commercial services. It describes model-improvement choices, safety-related exceptions and separate handling for incognito chats and feedback. Those distinctions make a blanket claim such as “Claude always trains on everything” or “Claude never uses conversations” misleading. Read the policy that matches the product and setting you actually use. Anthropic's consumer notice.

Before using an account for organisational information, confirm that it is the approved account and that the organisation permits the particular type of material. A paid subscription alone is not an adequate explanation of those permissions.

Separate training, retention and review

Ask the privacy question in parts. Will this content improve models? How long might it remain stored? Could a person review it? Does submitting feedback change its handling? What changes when activity history is disabled?

Google's Gemini privacy documentation illustrates why this separation matters. It describes human review of a subset of chats and settings that affect model improvement. It also explains that temporary chats and conversations with activity disabled can still be processed for service provision and protection, including some human review. A temporary conversation should therefore not be interpreted as a universal promise of zero processing or review. Gemini Apps Privacy Hub.

These are examples of current product documentation checked for this article, not a ranking of which provider is safest. Policies, account types and controls can change. Check the live notice when the consequences of disclosure matter.

Follow the information beyond the chat box

The assistant may be connected to a search service, document repository, browser extension or another application. Before enabling a connection, inspect what permission it requests and whether the task actually needs it.

Draw a simple route: document → assistant → connected tool → output. Add a question mark anywhere you cannot explain who receives the material. The point is not to become a security engineer. It is to notice when a seemingly private conversation is part of a larger workflow.

For example, asking for a summary of text you paste is different from granting access to an entire mailbox. A narrow task should not automatically justify broad access. Where the product supports a choice, start with the minimum relevant file or permission and expand only if there is a clear need.

Use a repeatable pre-upload check

Before submitting material, answer these questions in plain language:

• What specific result am I asking for?
• Which names, identifiers or passages can I remove?
• Is this the correct account for this kind of information?
• What do the current training, retention and review rules say?
• Will a connected service receive the content?
• If the document concerns someone else, am I authorised to share it here?

An unanswered question does not always require abandoning the task. Often you can still obtain useful help by substituting an invented example, asking for a general explanation or sharing only a short non-sensitive extract.

Make that the default first attempt. It is easier to provide one additional detail later than to undo the disclosure of an entire document. Good prompting begins with deciding what information the assistant needs, not with giving it everything you have.