Log & Data Privacy SanitizerRedact · Tokenize · Restore
● 100% CLIENT-SIDE · NO DATA LEAVES THIS MACHINE
0Lines Processed
0Unique IPs Replaced
0Unique Hosts Replaced
0Unique GUIDs Replaced

Raw Logs Input

✦ select text to sanitize 0 lines
What to Sanitize
External IPs are off by default — useful to keep visible as IOCs. Toggle anything, then re-run Sanitize.
Custom Regex Patterns 0 🔒 PRO
One per line: <regex> => TOKEN. The token becomes the prefix. Matches are case-insensitive. Examples:
EMP-[0-9]{5} => USER · srv-[a-z0-9]+ => HOST · ACC[0-9]{6} => ID
Custom Redaction Terms
Optional — the engine already auto-detects labelled fields (Source Host Name -, Source User Name -, etc.). Use this only for extra terms it can't infer. One per line, case-insensitive, matches inside compound strings too (so ACME also cleans ACME_SvcMonitor). Optional token label after =, e.g. ACME = ORG. List longest variants first (contoso-corp before contoso).
Host Name Patterns — optional 🔒 PRO
Most hosts are caught automatically: DESKTOP-/LAPTOP- names, and any name containing a role code as a segment (rkfd-nu-sql, NYC-DT-0234, SQL-01, SRV-CTX-GW01). Use this box only for a convention with no role word and no number pattern the engine can recognise — e.g. an asset tag like IT2412-380. A plain word is a prefix (so IT catches IT2412-380 but not the word ITEM); or wrap a regex in slashes, e.g. /[A-Z]{3}\d{4}-\d{2,4}/.

Sanitized Logs Output

✦ select to sanitize 0 lines
Original ValueAnonymized TokenCategory
No mappings yet — load or paste logs, then click Sanitize Logs.