Veil — Auto PII Blur

Auto-blurs emails, cards, SSNs & API keys on any page so you don't leak data when sharing or recording your screen.

New: Exposure Scan. Click once to see a local report of exactly what sensitive data the current page would leak if you shared it — counts by category and a risk level — then blur it all with one button. New: developer-secret detection. Veil now spots API keys, tokens, JWTs, .env values, connection strings, private keys, and internal/localhost URLs — not just personal data. Smarter reporting: numbers that look sensitive but fail a checksum (like an order number shaped like a card) are shown as "ignored, left alone" instead of being blurred — so the report is honest, not noisy. Still 100% local: no accounts, no servers, no analytics, and nothing leaves your browser. Same permissions as before. Run a 5-second exposure scan before you share your screen. Before you hop on that call, demo, or recording — click Scan Exposure. Veil reads the current page locally and shows you exactly what sensitive data it would leak if you shared it: a count by category and a risk level, in one glance. Then blur it all with a single button. It's the pre-share safety check for anyone who screen-shares real data. ## The scan tells you, in plain language • How many emails, cards, SSNs, phone numbers, and bank numbers are on the page • How many developer secrets are exposed — API keys, tokens, JWTs, .env values, connection strings, private keys, internal URLs • A risk level (from "no common patterns detected" up to Critical) • What it checked and deliberately left alone — e.g. an order number shaped like a card that fails its checksum is reported as "ignored," not blurred. No crying wolf. ## Then hide it — in one click Hit "Blur Everything Now" and every detected value is blurred on the page. Need to check one yourself? Click it to reveal — only you see it, and only when you choose. Leave protection on and Veil keeps blurring new values as the page loads. ## What Veil detects Personal & financial: • Email addresses • Credit / debit card numbers (Luhn + brand validated, so random digits aren't flagged) • Social Security numbers (SSNs) • Phone numbers • Bank / IBAN numbers (checksum validated) Developer secrets: • API keys & tokens — Stripe, AWS, GitHub, Slack, Google, and generic high-entropy keys • JWTs and Bearer tokens • .env-style secrets (PASSWORD, API_KEY, JWT_SECRET, …) • Database / service connection strings (with embedded passwords) • Private key blocks (-----BEGIN PRIVATE KEY-----) Network: • Private IPs (10.x, 172.16–31.x, 192.168.x, 127.0.0.1) • Internal / localhost / staging URLs • Public IP addresses (optional) ## Who it's for • Engineers & DevOps — demo dashboards, terminals, and consoles without flashing a key • Customer support & success — co-browse without exposing customer PII • Sales engineers — demo on real accounts without leaking data • Creators & educators — record tutorials without pausing to censor • Consultants & agencies — record client walkthroughs without exposing their data • Anyone posting a screenshot for a bug report or question ## Copy a clean report The scan can copy a plain-text summary to your clipboard — handy for a quick "here's what was on screen" note to a teammate. It contains counts only; the actual sensitive values never leave your browser. ## Private by design Veil runs 100% in your browser. It does not collect, store, or transmit any page content or personal data. There are no accounts, no servers, and no analytics. Your settings are saved locally on your device. ## Good to know Veil detects structured patterns (emails, cards, SSNs, numbers, keys, tokens, URLs) using local pattern matching and validation; it does not detect free-form names or street addresses, and detection is best-effort — it reports what it finds, not a guarantee of what's absent. Run the scan and turn protection on before you share so you can see and hide what's there.