03 · Use
What gets masked
Every detector runs in your tab on every keystroke. Each detected value gets a numbered placeholder, and the same value always gets the same placeholder within a request.
Detectors
| Kind | Placeholder | Matches |
|---|---|---|
| Private keys | [KEY_1] | 0x + 64 hex characters · also refused by the server if left in |
| API keys and tokens | [SECRET_1] | sk-…, ghp_…, AKIA…, Bearer … · also refused by the server if left in |
| Card numbers | [CARD_1] | 13–19 digits that pass the Luhn check · also refused by the server if left in |
| Email addresses | [EMAIL_1] | name@example.com |
| Bank account numbers (IBAN) | [IBAN_1] | GB82 WEST 1234 … |
| Wallet addresses | [ADDRESS_1] | 0x + 40 hex, or a base58 address |
| Phone numbers | [PHONE_1] | +1 415 555 0100 |
| IP addresses | [IP_1] | 203.0.113.7 |
| Words on your list | [NAME_1] | names, companies, places you add |
Overlaps and repeats
- Your word list wins over every pattern, then private keys, secrets, cards, emails, IBANs, addresses, phones and IP addresses, in that order.
- Words on your list match as whole words, ignoring case; the longest entry wins, so "Dana Reyes" is one placeholder, not two.
- A value that appears three times becomes the same placeholder three times, so the answer stays coherent.
- Cards must pass the Luhn check; IP parts must be 0 to 255; base58 addresses need digits and mixed case, so ordinary long words are left alone.
What it can miss
Pattern detection cannot understand meaning. A street described in words, a rare identifier format, a person named only by role ("my landlord on the corner") or a secret with no known shape will pass through. That is why the masked text is always shown before sending, and why the word list exists. When in doubt, edit the request.