Log Anonymizer / PII Scrubber

Paste a log, scrub IPs, emails, and API keys locally, then copy or download the result. Processing never leaves this page.

Log Anonymizer / PII Scrubber

Strip IPs, emails, and API keys from logs in this browser. Nothing is uploaded.

Privacy: scrubbing runs only in your browser. Close the tab when you are done if the paste was sensitive.

Why scrub before you share

Support threads, Slack pastes, and “can you take a look?” emails often include more than the stack trace: a client IP, the user’s email, a Bearer token, or an AWS key that someone logged at DEBUG. Once that text is in a ticket, you do not control the copies.

This tool is a first pass, not a compliance product. It uses patterns. It will miss odd formats and can over-redact. Read the output.

What it redacts

  • Emails — typical user@host.tld addresses.
  • IPv4 and IPv6 — including compressed IPv6 and IPv4-mapped forms.
  • API keys and tokens — AWS AKIA…, GitHub ghp_ / github_pat_, Slack xox*, Stripe sk_live_ / sk_test_, Google AIza…, Authorization: Bearer …, JWT-shaped strings, and api_key= / secret= style assignments.
  • Phone numbers — E.164 and local forms: +919876543210, +91 98765 43210, 9876543210, (415) 555-2671, +1-415-555-2671, and phone= / mobile= / tel= fields. Compact 10-digit unix timestamps (starting with 1) are left alone.

Stable replacements ([EMAIL:a3f2]) hash the original in the browser so the same value maps to the same token. That helps you follow “user X hit this twice” without keeping the address.

What it will not promise

  • It does not find every secret (custom headers, cookies, national IDs, street addresses, rare key formats).
  • It does not talk to a server. If you need a pipeline scrubber, run something like that on the collector, not after the fact in a paste box.
  • Closing the tab is the cleanup. The page does not persist the log.

For JWT inspection (not redaction), use the JWT Decoder. For pulling fields out of a line, the Regex Tester is the better fit.