What counts as personal data
In this guide, personal data means information about an identifiable person. That working definition is ours, not a quoted legal text. The US federal guidance in NIST Special Publication 800-122 includes information that is “linked or linkable to an individual, such as medical, educational, financial, and employment information.” The sheet does not treat it as the legal definition under GDPR or any US state law.
For the UK version of the GDPR, Article 9(1) says “data concerning health or data concerning a natural person’s sex life or sexual orientation shall be prohibited” for processing, subject to the exceptions in Article 9(2). The extract the sheet verified names those two categories. The full list is longer and was not checked for this guide. The EU text was not verified.
This is general information, not legal advice.
A three-tier list: never paste, generalise, share
Sort every detail into one of three tiers before you paste. The tiers are a practical rule built from this guide’s sources, not a legal classification. The LLM Context Passport scanner works the same way. For each finding, Remove replaces the match with [removed] (or [name removed] for a person), and Generalise uses a marker such as [email] or [phone], or a neutral phrase.
| Item | Tier |
|---|---|
| API key or token | Never paste |
| Password or login | Never paste |
| Card or bank number | Never paste |
| National ID number | Never paste |
| Email address | Generalise |
| Phone number | Generalise |
| Street address | Generalise |
| Employer or client name | Generalise |
| Health detail | Generalise |
| Salary or money figure | Generalise |
| The task itself | Fine to share |
Never paste. Google’s Gemini Apps Privacy Hub says: “Don’t enter login or payment information into Gemini chats.” The sheet found no regulator or vendor statement about API keys, so the rule for keys is this guide’s own. Card numbers belong here too, because Google’s wording covers payment information. National ID numbers also belong here. That is this guide’s own rule, not a quoted one.
Generalise. Replace the identifier with a description that does the same job. The tool suggests wording such as “[email]” for an address, “a company” for an employer, “a manager” for a named person, and “I have a chronic condition” for a health detail. For pay, leave out the figure or use a range.
Fine to share. The goal, the error text with secrets removed, the code without credentials, and the format you want. The UK Information Commissioner’s Office says that data minimisation “requires you to identify the minimum amount of personal data you need to fulfil your purpose”.
What vendors say about training and retention, with dates
Training and retention rules belong to each product, and they change. The sheet verified statements from two vendors only, so this guide gives no rule for any other vendor. Each rule below applies only to the product named, as dated.
- Anthropic, consumer Claude (Free, Pro and Max), page dated 28 August 2025. The page says “We will train new models using data from Free, Pro, and Max accounts when this setting is on.” It also says that if you delete a conversation with Claude, it “will not be used for future model training.” On consumer plans, five-year retention applies only if you allow training, and only to new or resumed chats and coding sessions. If you do not allow training, the existing 30-day period continues.
- Anthropic, Commercial Terms. The same page says these updates “do not apply to services under our Commercial Terms”, and it lists Claude for Work and the API among those services. The sheet does not give the rules for those services.
- Anthropic, turning the setting off. Anthropic says it will not use new chats and coding sessions for future model training, and that it will stop using your previously stored chats and coding sessions in future training runs. Data already included in training that has started, and in models already trained, is still included.
- Google, Gemini Apps Privacy Hub, no date shown. Google asks you not to enter “confidential information that you wouldn’t want a reviewer to see or Google to use to improve our services.” Turning off Keep Activity stops future chats being reviewed to improve Google services. Temporary chats are “not used to improve Google AI with help from human reviewers.”
- Google, reviewed chats. The Privacy Hub says chats reviewed by human reviewers, and related data such as language, device type, location information or feedback, “are not deleted when you delete your activity” and are “retained for up to three years.” That rule covers chats that reviewers have seen, so it does not describe every chat.
Why pattern-based redaction misses in both directions
A pattern-based redactor misses some personal details and flags harmless text. The sheet has no verified accuracy figure for any redaction tool, so the points below are reasoning, not measured rates.
It misses context. A combination of facts, such as a job title, a city and an unusual project, can identify someone, and no single pattern catches it.
It also over-flags. The scanner can flag a ticket number that happens to pass the card check as a card number, and it flags “I was diagnosed with a race condition” as a health detail. A flag is a prompt to read the text, not a verdict. The check catches the easy cases; you catch the context. The LLM Context Passport scanner is pattern-based too, so a clean result from it is not a guarantee.
Safer habits: placeholders, temporary chats and separate accounts
- Use placeholders that keep the shape of the problem. Write [client], [email] or [secret] in place of real values, so the structure stays visible.
- Use a temporary or incognito chat for a one-off question. On Enterprise or Team accounts, Claude’s help page says incognito chats “are included in standard data exports and follow your organization's data retention policies.” The sources here do not say whether an incognito chat changes Claude’s training rules, so do not assume that it does.
- Turn off Keep Activity in Gemini if you do not want future chats reviewed to improve Google services.
- Use the account your organisation approves for client data. Anthropic’s 2025 consumer update does not apply to Commercial Terms services. Which account to use is your organisation’s policy decision.
- Use a local model for text you would never send to a vendor, and check where the app sends your text, because the sheet did not verify local model apps.
A worked example: one message, redacted
Everything below is invented. The key is a GitHub-style fake, and 555-01xx numbers are commonly used for fiction.
I’m Alex, operations lead at Acme Freight GmbH. Email [email protected] or call +1 (555) 555-0142. My manager Pat Example says the route report is late. Can you fix this SQL?
The message also includes a GitHub-style deploy key, shortened here to ghp_EXAMPLE because the full token is too wide for a phone. The tool’s sample profile has the full token.
With the tool’s default settings, a public chatbot in balanced mode, high-severity findings are removed and medium ones are generalised. The scanner therefore proposes this version:
I’m Alex, operations lead at a company. Email [email] or call [phone]. My manager [name removed] says the route report is late. Can you fix this SQL? The deploy key is [removed].
Remove uses [removed], or [name removed] for a person. Generalise uses markers such as [email], or a phrase such as “a company”. For this query none of the identity is needed, so paste this instead:
I’m an operations lead. My manager says the route report is late. Can you fix this SQL?
If the deploy key were real, revoke it and create a new one, because a pasted key should be treated as exposed.
The context passport guide shows how to keep the stable background in one short, redacted text.
Common mistakes and what this cannot tell you
- Redacting after you send. Remove details before you send. A sent message has already left your device.
- Treating an opt-out as a deletion. Turning off the training setting does not remove data already included in training that has started, according to Anthropic.
- Assuming one deletion removes every copy. The sources describe different retention for different kinds of data. Check each product’s deletion and retention pages.
This guide reports what the cited sources said when they were checked on 17 October 2026. Some pages carry no date, and the sheet did not verify OpenAI or other vendors. Rules change, so read the current terms before you rely on them. For a longer look at reading terms, see the terms of service guide.
Common questions
Is it safe to paste an API key into a chatbot to get help?
Treat it as never-paste. The sheet found no vendor or regulator statement about API keys, so this rule is this guide’s own. The closest verified line is Google’s “Don’t enter login or payment information into Gemini chats.” If a key has already been pasted, revoke it and create a new one.
Do chatbots use my conversations for training?
It depends on the product, the account type and the settings. For consumer Claude, Anthropic’s page dated 28 August 2025 describes a training setting that you control, and says its update does not apply to Commercial Terms services. For Gemini, Google says turning off Keep Activity stops future chats being reviewed to improve its services. Google asks you not to enter confidential information it would not want used to improve its services, “including machine-learning technologies.” The sources here do not show whether Google trains on chats.
Does deleting a conversation remove my data everywhere?
Only in part. On consumer Claude plans, Anthropic says a deleted conversation will not be used for future model training. Google says chats reviewed by human reviewers, and related data, are not deleted when you delete your activity, and are retained for up to three years. Those statements do not cover every copy a product might keep, so check the product’s own pages.
Is a phone number personal data?
Under the NIST definition, information linked or linkable to a person counts as personal information. In this guide’s judgement, a phone number is usually linkable, which is why it sits in the generalise tier. Whether it is personal data under GDPR or a US state law is a legal question this guide does not settle. Generalise it unless the task needs the number.
What are special category data under the UK GDPR?
Article 9(1) of the UK GDPR, as published on legislation.gov.uk, lists special categories. The extract the sheet verified names data concerning health and data concerning sex life or sexual orientation. The full list is longer and was not checked here, and the EU text was not verified. Treat health details, and any other sensitive category you meet, as items to generalise.
Sources and further reading
- Updates to our consumer terms and privacy policy — Anthropic, 28 August 2025
- Use Claude’s chat search and memory to build on previous context — Anthropic Help Center, undated, viewed 17 October 2026
- Get personalization with memory of your past Gemini chats — Google Gemini Apps Help, undated
- Gemini Apps Privacy Hub — Google, undated
- NIST SP 800-122: Guide to Protecting the Confidentiality of Personally Identifiable Information — NIST, April 2010
- Regulation (EU) 2016/679 as applied in the UK, Article 9 — legislation.gov.uk, UK version as amended
- How should we assess security and data minimisation in AI? — UK Information Commissioner’s Office, updated 15 March 2023, under review