The fastest route to a realistic test fixture is a production record with the personal data taken out. Paste it here and the replacement runs entirely in your browser — nothing is uploaded, nothing is logged, and the tab can be offline while it works.
What you can control
- Eight detector types covering the identifiers that most often leak into logs and tickets.
- The realistic-substitute strategy keeps the text readable, which matters when the sanitised version still has to be reviewed.
- Stable hashing replaces each distinct value consistently, so relationships between records survive.
- A summary reports what was found and replaced, so you can see whether a detector missed something.
What this is not
Pattern matching finds common formats and will miss anything unusual — an unformatted ID, a name in a script the pattern does not cover, a free-text description. Always review the output before treating it as safe to share.
Questions
Does my text get uploaded anywhere?
No. Detection and replacement run in JavaScript in your browser. The page makes no network request with your input, and it works with the network disconnected.
Which replacement strategy should I use?
Realistic substitutes when the sanitised text still has to be read by a person. Stable hashing when you need to keep track of which records referred to the same value.
Is this enough to make data safe to share?
It is a first pass, not a guarantee. Pattern matching misses unusual formats and free-text mentions, so review the output before sharing it outside your team.