Paste chat logs into AI tools without leaking personal details

The most useful thing you can paste into an AI tool is often the thing you must not paste: a support ticket with the customer's email in it, a chat export full of phone numbers, a bug report quoting a user's address. The AI needs the story, not the identities. Masking separates the two before anything leaves your hands.

What to cover

PII is any detail that points to a real person: names, email addresses, phone numbers, home addresses, dates of birth, ID and account numbers, passwords and keys. In a support thread these hide in signatures, quoted replies, screenshots of forms, and order numbers that double as account identifiers. Usernames count when they identify someone, and so do combinations: a first name plus a workplace narrows to one person fast. When in doubt, cover it. An over-masked ticket still tells its story; an under-masked one leaks.

The workflow

Paste the thread into the PII masker. It runs entirely in your browser, so the unmasked original never travels anywhere in this step. Read the detected types as pills: each kind found gets a count. Switch to the highlights view to see every value where it sits, which is where you catch the one the shapes missed. Copy the masked version and paste that into the AI tool instead of the original. Close the tab and the original is gone; nothing was uploaded at any point.

Teach it your own shapes

Every support desk has IDs only it uses: order numbers, badge codes, tenant slugs. Describe them in plain English under the tool, for example also mask order numbers like ORD-88231 as account_number, and the pattern compiles instantly in your browser. Those rules persist in the same browser for next time. This is the highest-value minute of the workflow, because custom IDs are exactly what generic checkers cannot know.

The honest caveat

A local checker is fast and private, not perfect. It catches clear shapes like emails and phones reliably and misses details with no clear shape, like a school name dropped into a sentence. The highlights glance before you copy is the whole safety net: ten seconds of reading beats any claim of completeness. For structured exports rather than prose threads, read how to mask PII in a JSON export and keep it valid next.