Conversations & context · builder
Build an AI context passport without oversharing
An AI context passport is a short profile for any chatbot. Build one here and scan it for emails, phone numbers, addresses, API keys and health details. Each finding gets a removal or safer wording. The tool never sends your text anywhere.
Try it
Everything runs in this tab. The tool's code never sends your text anywhere, and it keeps nothing in your browser unless you tick Save in this browser.
Settings
Your passport
2,000 characters per fieldBackup
A backup holds your text as you typed it, not the redacted version. Keep it private.
Findings
Output
What changed: original to redacted (Markdown)
How to use LLM Context Passport
- Fill in the passport. Describe your role, goals, expertise and how you want answers. Load the sample to see a risky profile.
- Review the findings. The scanner flags patterns of personal data and secrets. Each finding offers Remove, Generalise or Keep.
- Choose an output format. Copy the Markdown, paragraph, custom-instructions pair, system prompt or JSON version.
- Check the share-safe badge. Re-scan the output tab you have open before you paste it. Export a backup only if you need one.
What an AI context passport is
An AI context passport is a short, structured description of you that you paste at the start of a conversation with a language model. It usually covers who you are and what you work on, what you are trying to get done, how you want answers written, and the rules that should hold for the whole conversation. Once written, the same passport can be reused in a new chat instead of retyping the background each time.
The idea is simple. The risk sits in the content. A passport written for convenience tends to collect names, employers, contact details and health notes, because those facts make a profile feel complete. This tool keeps the part you choose and flags the rest. For the reasoning behind that split, read the guide on what an AI context passport is, and the guide on what not to tell a chatbot and how to redact personal data first.
A passport you write yourself is a copy you control. You can read it, edit it, and decide where it goes. Whether a product keeps what you paste, and for how long, depends on that product's settings and terms, and those change. Check them rather than assuming. The same is true of any saved memory the product keeps about you.
If you want to see how much text a passport adds to a conversation, the LLM token counter shows how many tokens a block of text costs. The context drift heatmap shows how a long conversation drifts away from its opening instructions.
What the scanner checks
The scanner runs on every field of the passport about 250 milliseconds after you stop typing, and again on the output tab you have open. Each detector is a pattern rule. Most detectors also have a second check, such as a checksum, a digit count or a cue word, that keeps false positives down. None of the detectors uses a language model, so each finding card shows the rule that produced it.
| Finding | What it matches | What keeps it precise |
|---|---|---|
| A local part, an @ sign and a domain ending in letters | The top-level domain must be at least two letters | |
| Phone | A leading + with 8 to 15 digits, or a digit run after a word such as phone or mobile | Digit count is checked; ISO-style dates and numbers after ISBN are skipped |
| Street address | A house number, one to three capitalised words and a street word, or an "I live at" phrase | Needs a capitalised name and a street word, so "3 way switch" is not matched |
| Postal code | UK, Canadian and US state-plus-ZIP shapes; Dutch and German shapes only after an address cue | The shapes are strict; a bare five-digit number is not flagged |
| National ID | US SSN; UK NINO prefix rules; Turkish TCKN; a labelled "ID number" | SSN area and serial rules and the TCKN checksum; TCKN needs a cue |
| Payment card | 13 to 19 digits | Must pass the Luhn check; a run of one repeated digit, or a number after order, invoice or tracking, is skipped |
| IBAN | Country code, check digits and a length of 15 to 34 characters | The mod-97 check must give 1 |
| IP address | An IPv4 address after a cue such as IP or server; an IPv6 address | IPv6 needs a double colon or eight groups, so clock times are not matched; an IPv4 address with no cue is not flagged |
| Link with a token | A link whose query parameter name ends in token, signature, password or similar | The parameter value must be six or more characters |
| Secret | AWS, GitHub, Google, Slack and Stripe live keys; Anthropic-style and OpenAI-style keys; JSON Web Tokens; private key blocks | Fixed prefixes and lengths; the prefix must start a word; the OpenAI-style rule also requires a digit |
| Password or key in text | password, token, api_key or similar followed by a colon or equals sign and a value | Placeholders such as <token> are skipped; short ordinary words are not flagged |
| Date of birth | A date after "born on", "DOB" or "date of birth" | Dates with no such cue, such as a meeting date, are not flagged |
| GPS coordinates | A latitude and longitude pair with four or more decimal places | Latitude must be within 90 and longitude within 180 |
| Salary or financial amount | An amount with a currency code or k, after words such as salary, earn or debt | Plain numbers with no currency sign, code or k are not flagged |
| Employer or organisation | "I work at" or "my company is" plus a name, or a name ending in Inc, LLC, Ltd, GmbH, Corp, AG, BV, SA or Co | Needs the cue phrase or the suffix; a lowercase phrase such as "work at home" is ignored |
| Named person | A relation word such as my manager, My manager, my wife or my client, plus a capitalised name; or Mr, Ms, Mrs, Dr or Prof plus a name | The relation word and the capitalised name are both required |
| Sensitive detail | Phrases such as "I was diagnosed with", "I am a Christian" or "I am a member of the X Party" | Matched by phrase only; the scanner never guesses a sensitive category from vocabulary alone |
How severity and the actions are decided
Every finding gets a severity from its category and the trust level you choose. You set the trust level, which sets each finding's severity, and you can change the action on any finding. The same detail can be high risk for a public chatbot and low risk for a model that runs on your own device. Secrets are high in every case.
| Category | Public chatbot | Trusted workspace | Local model |
|---|---|---|---|
| Secrets (keys, tokens, private keys) | High | High | High |
| National and labelled IDs | High | High | Medium |
| Payment card and IBAN | High | High | Medium |
| Date of birth | High | Medium | Low |
| Named person | High | Medium | Low |
| Sensitive detail (health, belief, politics, sexuality, union, immigration, criminal record) | High | Medium | Low |
| Contact (email, phone, street, postal code, IP address) | Medium | Medium | Low |
| Location (GPS) | Medium | Low | Low |
| Money (salary, debt, income) | Medium | Low | Low |
| Employer or organisation | Medium | Low | Low |
The redaction mode sets the default action for each finding. Strict removes medium and high findings and generalises low ones. Balanced removes high findings, generalises medium ones and keeps low ones. Warn only keeps everything and lists the findings. You can change the action of any single finding, and changing the mode clears those choices.
Remove replaces the text with [removed], or for a named person with, for example, my manager [name removed]. Generalise uses a marker such as [email] or [phone], or a neutral phrase such as 'a company', 'a city' or 'a personal belief'. Keep leaves the text alone. A generalisation keeps some meaning, so read it before you paste.
When two findings overlap, the more severe one is kept. If they are equally severe, the longer one wins. The share-safe check re-scans the output tab you have open with the same trust level, so a Keep choice still shows up there.
Limits and what it cannot tell you
The scanner misses things it has no rule for. It will not find a name written without a relation word, an employer written without a cue, an address in a format it does not know, a key in a new format, or a sensitive fact stated without one of the listed phrases. It can also flag harmless text. A bug-report line such as "I was diagnosed with a race condition" matches the health phrase, and a pair of decimal numbers in a data table can match the coordinate rule.
The tool does not know your contracts, your employer's rules or the law that applies to you, so it cannot decide what you are allowed to share. It can only show you what it found and why.
The token count is a heuristic estimate, not a tokenizer. The character limit on each custom-instruction box is a placeholder you can edit, because each vendor sets its own limit and the limit can change. The tool limits each field to 2,000 characters and the whole passport to 60,000 characters; above that total the scan stops and nothing is cut from your text. Each list keeps its first 30 rows: rows beyond 30 are not scanned or exported, and the status line says so.
The tool cannot see how a product stores or uses what you paste. That is set by the product's terms and settings, and the next section gives some examples.
Privacy: what happens to your input
The tool's code analyses your text in this browser tab with JavaScript. It never sends your passport, your findings or your output to a server, and nothing you type goes into the address bar. The tool's code never sends your text anywhere, and it keeps nothing in your browser unless you tick Save in this browser. Untick the box to delete that copy. A backup file is a download; it stays where you save it. The site-wide promo banner is separate from the tool and never receives your text.
Once you paste a passport into a chatbot, that product's rules apply. These are examples from sources checked on 17 October 2026. Anthropic's update to its Consumer Terms and Privacy Policy is dated August 28, 2025. It says it "will train new models using data from Free, Pro, and Max accounts when this setting is on", and that "if you delete a conversation with Claude it will not be used for future model training". It also says "these updates do not apply to services under our Commercial Terms", a list that includes its API and Claude for Work. If you do not allow training, the existing 30-day retention period continues. If you do, the five-year period applies only to new or resumed chats and coding sessions. The deadline for existing users, October 8, 2025, has passed. See Anthropic's update on consumer terms.
Claude's memory has its own defaults. Its help centre says that "by default, Claude does not store topics related to personal or sensitive subject matter, like your health". That default can be changed. It also says "Reset memory: Permanently deletes all memories including project memories." See Anthropic's help article on chat search and memory.
Google's Gemini privacy hub asks users not to enter "confidential information that you wouldn't want a reviewer to see or Google to use to improve our services, including machine-learning technologies", and says "don't enter login or payment information into Gemini chats." See Google's Gemini Apps privacy hub.
Two public references explain why the scanner treats some details differently. The NIST guide to protecting personally identifiable information calls information "linked or linkable to an individual, such as medical, educational, financial, and employment information". That is a US federal definition used in NIST guidance. It is not the legal definition under the GDPR or any US state law. The UK GDPR lists "data concerning health" among special categories in Article 9. The scanner's health flag is a phrase cue, not a legal test, and it does not classify what you paste. This is general information, not legal advice.
The UK Information Commissioner's Office describes data minimisation as the requirement to "identify the minimum amount of personal data you need to fulfil your purpose". That guidance is under review, so treat it as current thinking rather than a final rule. The practical version is to remove each detail the task does not need, then scan what is left.
Questions
Is my data uploaded?
No. The tool's code analyses your text in this tab with JavaScript and never sends it to a server. It keeps nothing in your browser unless you tick Save in this browser. The site-wide promo banner is separate from the tool and never receives your text. Nothing you type goes into the address bar.
How accurate is this?
The scanner uses rules, not an AI model. It matches patterns such as email shapes, phone digit counts, card numbers that pass the Luhn check and known key prefixes. It misses personal data that has no recognisable pattern, such as a unique job title in a small town, and it can flag harmless text. Read every finding before you paste.
Does deleting a chat clear what I told the chatbot?
Check each product's settings rather than assume. On consumer Claude plans (Free, Pro and Max), Anthropic says that if you delete a conversation it 'will not be used for future model training'. Claude's Reset memory permanently deletes all memories, including project memories. The consumer-terms update does not apply to Commercial Terms services such as Claude for Work and the API.
Should I paste my API keys into a chatbot?
No. Remove the key and describe the setup in words instead. The sources checked for this page include no vendor statement on API keys, so this is a precaution, not a rule from a regulator. If a key has already been pasted anywhere, rotate it. This tool marks recognised key formats as high risk at every trust level.
What is the trust level for?
It changes how serious a finding is. Health details are high risk for a public consumer chatbot, medium for a trusted workspace and low for a model that runs on your own device. Secrets are always high. Pick the level that matches where you will paste the passport.
Why does the tool generalise instead of deleting?
Some context is useful but identifying. Saying a manager is involved, or that a company is mid-size, keeps the reason for a request without the name. Generalise replaces the exact detail with a neutral phrase you can edit.
Can I rely on the token estimate?
It is a heuristic estimate, not a tokenizer. Use the model vendor's own tokenizer or pricing page when exact numbers matter. The custom-instruction limit is an editable field, because each vendor sets its own limit and the limit can change.
What does the share-safe check prove?
It runs the same scanner on the output tab you have open. Zero high-risk findings means the scanner found no high-risk pattern in that text. It does not prove the text is safe, because the scanner can miss what it was not built to recognise.
Read more about this
Two plain-language guides that go deeper than this page can, with sources.