PII Scrubber

Personal data does not ask for permission to be in your logs — it just shows up. A customer email in a signup line, a phone number in a support record, a social security number an applicant uploaded, an IP address on every request. Under GDPR, CCPA and similar regimes, every one of those values is personal data, and the way you handle logs scattered with it affects storage, retention, deletion rights, and breach reporting. PII Scrubber is the fast, private way to strip it back out before a log goes anywhere it shouldn’t.

Two jobs, one tool. In Mask values mode, every email, phone number, social security number, card number, date of birth or IP address your enabled patterns catch is replaced by a fixed mask, so each line keeps its shape — still readable, still greppable, but devoid of personal detail. In Remove whole lines mode, any line containing a PII match is dropped entirely; that is the mode to choose when your goal is a log with no trace of the individual at all, for example before exporting to an archive or handing a sample to a third-party analyzer or vendor.

Every pattern has its own toggle, so you scrub exactly what your policy dictates and nothing more — leave IPs on for an internal audit but off for a public bug report, for instance. The IPv4 and IPv6 patterns are deliberately built to avoid matching ordinary bare timestamps (like 10:00:01) that share a superficial colon-separated shape with a shortened IPv6 address, so enabling IP scrubbing does not accidentally chew through every clock reading in the file. Custom regular expressions cover anything bespoke — internal IDs, taxpayer numbers, custom customer codes — and the summary tracks exactly how many of each type were scrubbed, so you can show your compliance process that the job was done. All of it happens in your browser, which is fitting: the whole point is that personal data should stop where it started.

• Email scrubber — masks or removes email addresses.
• Phone scrubber — international and US-style numbers.
• SSN scrubber — social security number shapes.
• Card scrubber — credit/debit card patterns.
• Birthday scrubber — dates of birth in common formats.
• IP scrubber — IPv4 and IPv6.
• Custom regexes — add your own PII patterns.
• Two modes — mask values in place or drop whole lines.
• Per-type toggles — scrub only what policy requires.
• Count summary — how many of each type were scrubbed.
• Copy / Download / Print — retrieve the clean result.
• 100% local — data never leaves the browser.

1. Paste your log. Drop the text containing personal data into the box.
2. Pick the PII types. Toggle emails, phones, SSNs, cards, birthdays and IPs on or off, and add custom regexes if your data has special shapes.
3. Choose a mode. Mask values to keep the lines readable, or Remove whole lines when the log must be completely free of the individual.
4. Run. The summary counts how many values of each type were scrubbed.
5. Review the untouched lines — always sanity-check the output, then copy or download it.

Example 1 — Support export. A support ticketing log contains email=jane.doe@example.com phone=+1 (555) 123-4567. Run with emails and phones enabled and the export your analyst receives has both values masked, while the surrounding message text stays intact.

Example 2 — Archiving for deletion. Before moving old logs to cold storage, run Remove whole lines mode. Records containing SSNs or DOBs (the most sensitive class) are dropped entirely, so the archive no longer retains that personal data at all — a much smaller deletion-rework surface later, since there is nothing left to find when a deletion request comes in.

Example 3 — Custom patterns. Your logs carry driver_licence=D1234-567-8901, a format none of the built-in patterns recognize. Add the matching pattern to the custom box and it is scrubbed like everything else, counted in its own row of the summary.

Example 4 — Timestamp-heavy logs. A service log timestamps every line as 10:00:01 style clock readings alongside real IPv4 and IPv6 addresses. Scrubbing with IPs enabled masks the genuine addresses only — the timestamps are left untouched because the pattern requires a shape no plain clock reading produces.

• GDPR-ready output — personal data minimized before it spreads.
• Deletion-friendly archives — less personal data retained.
• Fine control — per-pattern toggles and modes.
• Extensible — custom regexes for your shapes.
• Private — all processing stays local.