How to anonymize json for safe use in development environments
- Step 1Export records for development seeding — Export the records you want to use as development seed data from production — enough to represent realistic data volume and variety.
- Step 2Anonymize the export — Paste the JSON and run anonymization. PII fields are replaced with consistent synthetic values that preserve referential integrity: the same user ID always maps to the same fake name across all records.
- Step 3Commit as development seed data — Save the anonymized JSON to your development seed data files. These files are now safe to commit to version control and share with the full development team.
- Step 4Load into development database on setup — Add the anonymized seed data to the development environment setup script: Prisma seed, Docker init scripts, or database migration fixtures. Every new development environment starts with the same realistic anonymized data.
Frequently asked questions
Is it okay to commit anonymized development data to a public GitHub repository?+
Anonymized data (with all PII replaced with synthetic values that cannot be reversed) is generally safe to commit publicly, but review the data before committing. Ensure no real email addresses, real names, or other identifiable information remains. Be cautious with data that could be re-identified through combination — for example, a rare medical condition plus a specific city may still be identifying even without a name.
How do I maintain foreign key relationships when anonymizing related tables?+
Use consistent anonymization: the same input email always produces the same output email across all records. This preserves joins between related tables — if user records have email '[email protected]' and order records reference '[email protected]', both are consistently replaced with '[email protected]', maintaining the join.
Is the production export data transmitted to JAD Apps?+
No. Anonymization runs entirely in your browser. Production data 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.