JSON Anonymizer

// HOW TO USE

1. 01Paste a JSON document. PII detection is key-name based — fields like email, phone, ssn, cardNumber, etc. get replaced with safe placeholders.
2. 02Toggle off any category that doesn't apply to keep its values untouched.
3. 03The tool only matches by key name and only redacts primitive values — nested objects keep their structure so the shape of fixtures stays intact for tests.

// WHEN TO USE

Use this before sharing a real API response or database record in a bug report, Slack thread, or pull request — any context where real user data would be visible to people who shouldn't see it. Also use it to turn a production-like payload into a reusable test fixture: the structure stays intact but the values are safe to commit. Not a replacement for server-side data masking, but ideal for ad-hoc QA workflows where you handle real data briefly.

// WHAT BUGS THIS FINDS

• PII leakage in bug tickets

  A real user's email or phone number gets pasted into a Jira ticket or Slack message — anonymize the payload first to eliminate the exposure.

• Committed PII in test fixtures

  A fixture file generated from a production response contains real names and card numbers that end up in git history — anonymize before saving to the repo.

• Mismatched placeholder detection

  A field named 'userEmail' passes detection but 'contactMail' doesn't — reviewing the redacted output before sharing confirms which fields were missed.

• Nested structure collapse

  Naive string-replace tools flatten nested objects while anonymizing; this tool preserves shape, so fixture-dependent assertions on nested paths still work.

// QA USE CASES