Your prompts, minus the secrets.
Keys, seed phrases and contact details are swapped for stand-ins on your machine. The answer comes back with the real values.
Fix my deploy. The .env has the Stripe key key 1sk_live_7Hq2mX9vLr4TzB8nK3wY and the AWS key key 2AKIA4QX7Z2LMRP9TB3KD. Reply to email 1dana.ruiz@quillmail.dev or call phone 1+44 7700 900123.
They get look-alikes. You keep the real ones.
Never leaves your machine: key, secret, wallet, seed, card, iban, email, phone, term. See the list
One message, three states.
Draft a refund e-mail to Maria. She paid with card 4539 1488 0343 6467 and wants the money on IBAN NO93 8601 1117 947. Her address is maria.k@fjordmail.no and her phone is +47 412 55 309.
Draft a refund e-mail to Maria. She paid with card 4242 4297 1375 7590 and wants the money on IBAN NO09 1609 9990 717. Her address is rixil.t@rixv.example and her phone is +47 460 65 764.
Hi Maria, the charge on 4539 1488 0343 6467 is cancelled. The refund goes to NO93 8601 1117 947 within 3 working days. We will text +47 412 55 309 when it lands, and the receipt goes to maria.k@fjordmail.no.
The name stays: names are not on the list yet.
What gets hidden
01Service keys
key 1ghp_R7tQ2wX9mK4pL8vN3bY6cZ1dF5gH0jS2aE4u
About 25 known key prefixes: OpenAI, Anthropic, OpenRouter, AWS, GitHub, GitLab, Slack, Stripe, Google and more
02Secrets in config
secret 1JWT_SECRET=9f2Lk0qPz7Rw4Ns8Vb3m
.env, YAML, JSON and code values with a secret name, passwords in connection URLs, PEM private keys, JWTs, base64 that wraps a secret
03Wallet keys
wallet 10x8da4ef21b864d2cc526dbdb2a120bd2874c36c9d0a1fb7f8c63d7f7a8b41de8f
EVM 0x + 64 hex, Solana base58 or 64-number keypair
04Seed phrases
seed 1ripple canyon olive drift museum orbit valve tackle humble spray gentle lunar
12 to 24 BIP-39 words with a valid checksum, or after seed, mnemonic, recovery
05Card numbers
card 14539 1488 0343 6467
13 to 19 digits, known card prefix, Luhn check
06IBAN
iban 1NO93 8601 1117 947
Country length table and mod-97
07E-mail addresses
email 1dana.ruiz@quillmail.dev
Address syntax, Unicode allowed
08Phone numbers
phone 1+47 412 55 309
International with +, North American, French, UK formats
09Your own terms
term 1Project Larch
A file of words you add, whole words, any case
Not hidden on purpose: dates, cities, organisations, public wallet addresses, git SHAs, UUIDs, lockfile hashes, IP addresses.
What it does not do yet
- 01Names and street addresses are not found unless you put them in your terms file.
- 02Formats not on the list go out as written: unknown key formats, a password in a sentence, IP addresses, national ID numbers.
- 03A secret split across lines or string pieces is not found.
- 04URL-encoded values and e-mails written as name [at] domain are not found.
- 05If the model rewrites a stand-in in a new way, that value stays as the stand-in in the answer.
- 06Images, audio, files and embeddings are refused, not masked.
Change one line.
Start it on your machine, then send your requests through it. Nothing else in your code moves.
Run it, then point your client at the local address. Your code, your keys and your provider stay the same.
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "http://127.0.0.1:8787/v1",
apiKey: process.env.OPENROUTER_API_KEY,
});{
"model": "your-model",
"messages": [
{
"role": "user",
"content": "Reply to wexq.elwe@bexbe.example"
}
]
}{
"role": "assistant",
"content": "Done. I wrote to dana.ruiz@quillmail.dev."
}What we measured
Planted values leaked, across 80 requests from 50 agent traces.
Values put back in the answer. None left as a stand-in.
Secrets handed to a hostile tool call that tried to send them out.
Answers that used a value got it back: 156 of 156. With plain tags such as [EMAIL_1] instead of look-alikes: 67.
Tricky cases caught, from a set written before the first run.
- Missed: 3 keys split across lines or string pieces.
- Missed: 1 e-mail with an escaped @.
- Missed: 1 e-mail written as at and dot.
Added per request of about 1.5 kB, median.
p95: 0.82 ms. Measured on a quiet machine.