Skip to content
faker.tools
All 79

Plate VIII · Localization, Edge Cases & Data Sanitizers

Data Anonymizer & PII Stripper

Find and replace emails, phone numbers, card numbers, SSNs and IPs in text you paste — without uploading it.

text
Ticket #4821 — customer Priya Raman (alice.lopez@example.com, +1 583 555 0726)
reports a failed charge on card 4111 1111 1111 1111 from 88 Ashbury Street, San Francisco.
Account SSN 902-48-0377. Server 192.0.2.53 logged the error at 2025-11-02T09:14:00Z.

---
Replaced 5 value(s) — EMAIL: 1, PHONE: 1, CARD: 1, NATIONAL_ID: 1, IP: 1.
6 lines · 337 BGenerated in your browser · Data Anonymizer & PII Stripper

A PII redaction tool finds personal data in text and replaces it before the text goes anywhere else. Paste a log excerpt, a support ticket or a CSV sample, choose what to detect — emails, phone numbers, card numbers, national IDs, IP addresses, names, dates, URLs — and choose how to replace each one. It all runs in your browser: nothing you paste is uploaded.

The most common way production data ends up in a bug tracker, a Slack thread or a test fixture is a copy-paste. This is the step between the copy and the paste.

How to use it

  1. Paste your text into the box. The sample shows a typical support ticket.
  2. Tick the kinds of data to detect. Names and dates are off by default because they produce the most false positives.
  3. Pick a replacement: a type label ([EMAIL]), a mask, a realistic fake, a stable hash, or removal.
  4. Keep the summary on to see how many of each type were replaced, then copy the result.

What you can control

  • Eight detectors: email addresses, phone numbers, card numbers, US SSN-format national IDs, IPv4 addresses, capitalised names, ISO 8601 dates and URLs.
  • Five replacement strategies: type label, mask, realistic substitute, stable hash, or remove entirely.
  • Realistic substitutes from reserved ranges: example.com mail, 555-01xx phone numbers, 192.0.2.x addresses and 9xx SSNs.
  • A summary of what was found, by type.
  • Overlap handling: each span is claimed once, by the most specific pattern, so a card number is never re-detected as a phone number and a date is never mistaken for one.

Choosing a replacement

Strategy Example Use it when
Type label [EMAIL] Sharing a log or ticket where the value itself does not matter
Mask •••••@••••.••• The shape matters — testing a UI with redacted data
Realistic substitute susan.baker@example.com Making a fixture or demo that should read naturally
Stable hash email_3f9a1c07 You need to see that two lines refer to the same person
Remove (empty) Producing the smallest possible excerpt

Testing ideas

  • Build fixtures from real shapes. Take a real but sensitive payload, replace identifiers with realistic substitutes, and commit the result as a fixture. You keep the structure without the liability.
  • Test your own redaction. If your application masks data in logs, generate known PII with the identity generators, run it through your logger, and paste the output here with detection on. Anything found is a leak.
  • Check analytics events. Paste a captured analytics payload and see whether emails or phone numbers are hiding in URLs and custom properties.

What this is not

This is a pattern matcher, not a guarantee. It does not understand context, does not detect postal addresses or free-text descriptions, and its name detection is a rough heuristic. For regulated data, use it as a first pass before a human review — and read Production data in test environments for why generated data is safer than redacted data in the first place.

Questions

Is my text uploaded anywhere?

No. Detection and replacement run in JavaScript in your browser tab. Nothing is sent to a server, logged or stored. You can disconnect from the network after the page loads and the tool keeps working.

Is the output anonymous under GDPR?

Not automatically. Replacing direct identifiers is a strong first step, but GDPR treats data as anonymous only when nobody can reasonably re-identify a person from it, including by combining what is left. Free text often still contains names, addresses or details that identify someone. Treat the output as reduced-risk, and review it before sharing.

What is the difference between masking, fake values and stable hashes?

Masking replaces characters with dots, keeping the shape. Fake values swap in realistic substitutes — example.com emails, 555 numbers — so the text still reads naturally. A stable hash replaces each value with a token that is the same every time that value appears, so you can still see that two log lines involve the same user.

Is a stable hash safe?

It is pseudonymisation, not anonymisation. The hash is not cryptographic and is not salted, and inputs such as phone numbers come from a small enough space to brute-force. Use it to correlate within a document you control, not to publish.

Why was something not detected?

Detection is pattern-based. It finds well-formed emails, phone numbers with 7–15 digits, 13–19 digit card numbers, US SSNs in 123-45-6789 form, IPv4 addresses, ISO dates, URLs and pairs of capitalised words. Postal addresses, unformatted IDs and names in lowercase will slip through, which is why a human review still matters.

Next in Edge cases

All 7 →