How to strip pii fields from json for gdpr compliance
- Step 1Identify the PII fields to remove — List the field names containing personal data: email, firstName, lastName, phoneNumber, dateOfBirth, ipAddress, postalCode, streetAddress, and any domain-specific identifiers.
- Step 2Paste the JSON records — Paste the JSON array of records. Each element is processed and the specified keys are removed from every object, regardless of nesting level.
- Step 3Configure key removal — Enter the PII field names in the removal list. Enable 'Recursive removal' to strip the key at any nesting depth, or leave it off to only remove top-level keys.
- Step 4Download and verify the de-identified output — Download the stripped JSON file. Verify that the PII fields are absent using the JSON Path Extractor to search for removed fields and confirm no values are returned.
Frequently asked questions
Does removing PII fields from JSON satisfy GDPR right-to-erasure requests?+
Removing PII fields satisfies data minimization for new processing flows, but a right-to-erasure request requires deletion across all storage systems — databases, backups, third-party processors, and log archives. This tool helps prepare de-identified datasets for analytics, but right-to-erasure requires a comprehensive deletion process covering all data stores where the individual's data exists.
How should I handle pseudonymization instead of full removal?+
For analytics use cases where you need consistent per-user signals without storing the actual identity, replace PII values with a hashed or tokenized identifier rather than removing the field entirely. Replace the email with SHA-256(email + salt) using a script, or use the JSON Key Renamer to rename fields before applying a separate anonymization step.
Does the original JSON with PII leave my browser?+
No. All processing runs entirely in your browser. The original records, including all PII fields, are never transmitted to JAD Apps servers. Only your local browser memory processes the data.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.