Remove PII from JSON Online
Detect and remove PII from JSON logs in your browser so you can share data safely without exposing secrets.
Learn more Browser-first developer tools
Remove or replace sensitive fields before sharing logs, dumps, exports, or sample datasets.
What to expectPaste JSON, CSV, or SQL, scan for likely PII, choose what to mask or replace, and generate a safer output copy.
Good to knowDetection is heuristic, so it is a strong first pass but not a substitute for final human review.
How it works
- Paste JSON logs, CSV exports, or SQL dumps containing potential PII into the input panel.
- Run Auto-detect PII, choose which field types to scrub, and pick a replacement strategy for each.
- Click Scrub Data to generate anonymized output, then copy or download it before sharing downstream.
All detection and scrubbing happens in your browser. Source data and scrubbed output never leave your device.
Detected PII
0 field types9 of 9 field types active
Scrubbed output appears here
Paste data on the left and click Scrub Data
Frequently Asked Questions
Is this PII scrubber GDPR compliant?
The tool processes data entirely in your browser and never sends it to any server, which aligns with GDPR's data minimization principles. You're still responsible for choosing appropriate masking strategies and handling any exported files according to your organization's compliance policies.
What PII types does this tool detect?
The scrubber can detect and replace emails, phone numbers, SSNs, credit card numbers, postal addresses, full names, dates of birth, API keys, and IP addresses in structured JSON or log-like text. You can toggle each category on or off and choose how it should be replaced.
Does this tool support custom PII patterns?
Yes. In addition to the built-in rules, you can define custom patterns and replacement strategies for fields that are unique to your data model or log format, giving you fine-grained control over what counts as sensitive.
Is the scrubbed output safe to share with vendors or teammates?
Once sensitive values have been replaced according to your rules, the output is much safer to share for debugging, analytics, or support. You should still spot-check the result for edge cases and follow any internal guidelines around sample data.
Can I use this tool for one-off incident response log scrubbing?
Yes. The scrubber is designed for quick, browser-based workflows where you need to anonymize logs before pasting them into tickets, chat, or code review. Nothing is persisted once you close or refresh the tab.
Will the scrubber preserve the overall structure of my JSON or CSV?
Yes. The tool focuses on replacing sensitive values while preserving keys, nesting, and general formatting so that downstream tools can still parse the scrubbed data as valid JSON, CSV, or SQL. That makes it useful for reproducing issues in lower environments.
How to use this tool
Paste JSON, CSV, or SQL containing sensitive data. Click Auto-detect PII to scan, then enable or disable each field type and choose a replacement strategy. Click Scrub Data to generate the scrubbed output.