Ask Claude to Sanitize Data by Replacing Real Values with Realistic Fakes
You need to share a database dump, paste a JSON response into a bug report, or create test fixtures from real data — but it's full of real names and emails. Claude sanitizes it while keeping everything structurally identical.
"Sanitize this data — replace all personal information with realistic fakes
but keep the structure, types, and relationships intact:
[paste your data]"
Claude replaces PII while preserving everything that matters for debugging or testing:
// Before:
{"id": 1, "name": "John Smith", "email": "john@realcompany.com", "phone": "555-0123"}
// After:
{"id": 1, "name": "Sarah Chen", "email": "sarah@example.com", "phone": "555-0198"}
This works for any data format:
# SQL dumps
"Sanitize this SQL insert — replace customer names, emails, and
addresses with fakes. Keep the order totals and dates real."
# API response samples
"Anonymize this API response for our documentation — remove any
real user data but keep the response structure exactly the same"
# Log entries
"Sanitize these log lines — replace IP addresses, user IDs, and
email addresses with fake values so I can share them in the bug report"
# CSV exports
"Replace all PII in this CSV with realistic fake data. Keep numeric
columns like amounts and quantities unchanged."
You can control what gets sanitized:
# Keep some fields real
"Sanitize names and emails but keep dates, amounts, and status
values unchanged — those are needed for debugging"
# Maintain relationships
"Sanitize this data but make sure the same original user always
maps to the same fake name — so relationships stay consistent"
# Match the locale
"Replace with Japanese names and addresses — this data is for
testing our i18n support"
Claude can also write a sanitization script for repeated use:
"Write a script that sanitizes a database export — I'll need to
run this every time I pull production data for local development"
Real data is for production. Sanitized data is for everything else — let Claude strip the PII while keeping the structure that makes it useful.
via Claude Code
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.