Security & Auth Processed locally

PII Detector & Redactor

Paste text, JSON, CSV, logs, HTTP headers, .env, XML, or a URL. The tool auto-detects the format, finds emails, phones, SSNs, cards (Luhn-checked), government IDs, JWTs, API keys, cookies, IPs, and sensitive field names, and returns a structure-preserving sanitized copy. Pick a preset for your context; the Findings tab lists every detection. Pattern-based — review before sharing. Runs in your browser; nothing is uploaded.

Auto-scans as you type. Ctrl+Enter to re-run.

How to use the PII Detector & Redactor

Paste any text, JSON, CSV, HTTP headers, .env, XML, or log snippet and pick a preset. The tool detects emails, phone numbers, SSNs, credit cards, government IDs, tokens, JWTs, API keys, cookies, internal hostnames, and sensitive field names — then produces a sanitized copy you can copy, download, or hand off to another tool. Useful for sharing logs in tickets, attaching samples to bug reports, sanitizing data before pasting into ChatGPT or Claude, and reducing accidental data leakage. Runs entirely in your browser.

How to use it

  1. Paste your text, JSON, CSV, log lines, headers, .env, or XML into the input.
  2. Pick a preset that matches your context (LLM-prompt safe, ticket/PR, log share, PCI, secrets-only).
  3. The tool auto-detects the format and applies the preset's per-category redaction (replace, mask, format-preserving, or pseudonymize).
  4. Read the verdict, then open the Findings tab to review every detection.
  5. Copy or download the sanitized output, or hand it off to another tool.

What it detects

How it redacts

Each preset chooses the strategy per category — for example the PCI preset partially masks cards, while LLM-prompt-safe pseudonymizes names and replaces secrets. JSON, CSV, HTTP-header, and .env inputs are redacted structurally so the output stays valid.

Tips & pitfalls

FAQ

Runs locally in your browser. No uploads. No analytics on pasted content.

Related guides