How to anonymize json to create gdpr-compliant test data
- Step 1Export a small sample from production — Export 100-500 records from production as JSON. Small samples are sufficient for test data generation — anonymize a sample set and multiply it rather than processing the entire production dataset.
- Step 2Configure field detection — Review the detected PII fields. Add any custom field names specific to your data model (nationalId, taxNumber, passportNumber) to the custom field list.
- Step 3Run anonymization — Run the anonymizer. Each detected PII field is replaced with a realistic synthetic value: real email →’ [email protected], real name →’ 'James O'Brien', real phone →’ '+1-555-0100'.
- Step 4Validate and distribute to dev environments — Verify the anonymized output is structurally valid and contains no remaining real values. Load into development and staging databases as test data safe for all team members.
Frequently asked questions
Is anonymization sufficient for GDPR compliance, or do I need pseudonymization?+
True anonymization (where re-identification is impossible) removes records from GDPR scope. Pseudonymization (replacement with tokens that can be reversed with a key) is still personal data under GDPR. This tool performs replacement with synthetic values that cannot be reversed — which is closer to true anonymization. However, anonymization is sufficient for test data purposes as long as the original personal data is not retained alongside the anonymized set.
What personal data fields does the tool detect automatically?+
The tool detects fields by name pattern: fields containing 'email', 'mail' →’ email format; 'name', 'firstName', 'lastName', 'fullName' →’ person name format; 'phone', 'mobile', 'tel' →’ phone number format; 'address', 'street', 'city', 'zip', 'postcode' →’ address components; 'ip', 'ipAddress' →’ IP address format.
Is the production data transmitted to JAD Apps?+
No. Anonymization runs entirely in your browser. Production data with real personal information is never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.