Generate Synthetic Test Data Preserving Referential Integrity
Naive pseudonymization (replacing emails with random UUIDs) breaks referential integrity. If customer_id 847291 appears in both orders.csv and subscriptions.csv, random replacement breaks foreign key relationships. This workflow builds a deterministic mapping table via SHA-256 hashing, ensuring that customer 847291 always maps to the same synthetic email (e.g., [email protected]) across all related tables. Safely clone production databases into staging.
Why this matters?
A DevOps team used a simple REPLACE() script to mask emails for load testing. The import passed, but a misconfigured staging cron job processed 4,200 abandoned cart emails using the original domain portion, sending real customers emails with broken staging links. Each accidental email triggers a GDPR Article 33 breach notification requirement—costing an estimated $1.05M in legal administration. Deterministic hashing prevents this entirely.
The 3-Step Solution
Don't waste hours fighting spreadsheet crashes or writing custom Python scripts. Here is the exact workflow to solve this locally. All processing happens instantly in your browser via Wasm. We will use the GDPR Anonymizer to execute this without touching a cloud server.
💡 Privacy Note: Disconnect your Wi-Fi right now—the tool will still work.
Ready to clean your data?
100% local processing. Zero uploads. Blazing fast.
Recommended Tools
Related Workflows
How to Anonymize Customer Data Before Sharing with ChatGPT or Claude
Your raw customer CSV contains toxic PII. Pasting it into ChatGPT sends that data to OpenAI's servers—risking a Samsung-style corporate leak. This SOP local-masks names, emails, phones, and IPs using browser-based hashing. It preserves column types and statistical structures for LLM analysis, rendering the output completely untraceable to real users.
How to Convert Stripe Payout Reports into QuickBooks Import Format
Stripe's balance detail export dumps charges, refunds, and fees into a flat CSV (gross, fee, net). None of this maps to QuickBooks Online's rigid 3-column schema (Date, Description, Amount). While Stripe admits IIF files only work for QBD, SaaS connectors like A2X charge $49/mo to bridge the gap. This workflow splits your transaction types into specific Chart of Accounts buckets (Revenue, Merchant Fees), converts ISO 8601 timestamps to MM/DD/YYYY, and generates a CSV that passes QuickBooks import validation with zero reconciliation errors.
Sanitize Email Lists Before Klaviyo Import
Importing a dirty contact list into Klaviyo is how brands torch their sending reputation in 48 hours. Suppression lists from legacy ESPs (Mailchimp, Omnisend) ship with invisible zero-width joiners (U+200D), malformed addresses (user@@domain), and role-based emails (info@, admin@) that act as spam traps. This workflow cross-references your prospect list, strips non-printable Unicode (U+200B - U+200F), and validates RFC 5322 formatting—entirely inside your browser tab.
Clean CRM Data for Facebook Offline Conversions API Upload
Uploading offline conversions to Meta's CAPI requires identifiers hashed with SHA-256. Meta's hashing is violently case- and whitespace-sensitive: ' [email protected] ' produces a completely different hash than '[email protected]', causing the match to fail silently. CRM exports from Salesforce also frequently contain invisible zero-width joiner characters (U+200D) copied from web forms, producing hashes that match zero Facebook profiles. This workflow normalizes emails to lowercase, strips invisible Unicode, and reformats phones to the E.164 standard (+1XXXXXXXXXX).
Sample Datasets
Apollo.io B2B Leads Export Sample CSV (Dirty + Clean)
A realistic Apollo.io lead list (300 contacts) engineered with the exact data quality issues that destroy cold email deliverability. The 'dirty' version includes: duplicate emails from overlapping searches, role-based addresses (info@, admin@) that trigger spam filters, catch-all domains falsely marked as 'verified', and mixed-case names resulting in 'Hi jOHN' personalization disasters. The 'clean' version shows the output after deduplication and name normalization. Ideal for testing cold email platform imports (Instantly, Smartlead) to protect domain reputation, or CRM deduplication workflows in HubSpot and Salesforce. All processing happens locally — your lead data stays private.
Salesforce Leads Export Sample CSV (Dirty + Clean)
A production-realistic Salesforce lead export (6,200 rows) engineered to expose validation errors that crash Data Loader bulk imports. The Salesforce quirk: strict validation on fields like LeadSource means even a single invisible character triggers INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST errors. The 'dirty' version includes LeadSource values with zero-width spaces (U+200B) invisible in Excel, malformed 15-character Lead IDs missing the checksum suffix (causing upsert failures), and embedded commas in company names. Perfect for testing API integrations, Data Loader workflows, and Marketing Automation migrations. Process everything locally — your lead data never touches a server.