ToolJutsu
All tools
Data Tools

Data Anonymizer

Replace names and emails in data with safe placeholders.

Or drop a file

This input looks like delimited data — the CSV name-column picker below is available.

What to anonymise
Phone replacement:
Person names

Reliable name detection needs structure. Use the CSV column picker for tabular data, or the explicit list for free text — automatic name detection in unstructured text is not dependable.

Selected columns have every body cell replaced with a random full name. The header row is left untouched.

3
Emails replaced
3
Names replaced
3
Phones replaced
1
Cards replaced
0
IDs replaced
Anonymised output (10 values replaced)

Automatic detection is pattern-based, not perfect — always review the output before sharing it. Names embedded in free text are only replaced when you list them explicitly above.

Processed on your device. We never see your files.

How to use Data Anonymizer

What this tool does

The Data Anonymizer replaces sensitive details in your data with safe, realistic placeholders so you can share a dataset without exposing real people. Paste any text — a CSV export, a JSON payload, a log file, a contact list — or drop a file, and the tool rewrites email addresses, phone numbers, payment-card-like numbers, long ID numbers and person names. It opens with a small sample of customer-style CSV already loaded, so you can see how every option behaves immediately.

The replacements look like genuine data — names such as “Jordan Smith”, emails on example.com — because anonymised data is most useful when it still resembles the real thing. All of the replacement names come from a short word list bundled with the tool. There is no external service and no Faker.js dependency.

Why and when you’d use it

Anonymised data solves a recurring problem: you need to share data, but the data contains people. A support analyst preparing a bug report wants to attach a real export without leaking customer emails. A marketer sending a sample list to an agency needs the structure intact but the contacts fake. A developer building a demo wants believable test data that is not anyone’s actual record. An operations lead sharing a spreadsheet in a training deck needs the figures but not the names.

In every one of those cases the safe move is to anonymise before the data leaves your control — and to do it with a tool that never sees the original. A server-side anonymiser would defeat the purpose: you would be uploading the very customer list you are trying to protect. Because this tool runs entirely in your browser, the sensitive original never travels anywhere.

If you need to reshape the cleaned data afterwards, CSV to Table and the Table Generator can convert it into other formats once the sensitive values are gone.

How to use it

  1. Paste your text into the box, or drop a .csv, .txt, .json or similar file. The tool works on the raw text either way.
  2. Under What to anonymise, switch on the categories you want — emails, phone numbers, card-like numbers, and optionally long ID runs.
  3. For names: if the input is a CSV, tick the columns that hold names and they are replaced wholesale. For free text, turn on Find & replace specific names and list the exact names to anonymise.
  4. Decide on Use consistent replacements. Leave it on to keep repeated values mapping to the same placeholder; turn it off for fully independent randomisation.
  5. Read the counts to see how many emails, names, phones and cards were replaced, then Copy or Download the anonymised output.

Common pitfalls and tips

Automatic detection is pattern-based, so review the output before sharing it. A few specific things to watch: an unusual phone format — an extension, an international style the pattern does not expect — may be missed, so scan phone columns by eye. Names in free text are only replaced when you list them, so if a name appears in three spellings, list all three. The card detector looks for 13 to 16 digit runs; a longer account number could be caught as an ID instead, or a shorter one missed entirely.

Be aware too of the usual spreadsheet quirks. If your CSV has ZIP codes or SKUs with leading zeros, Excel may have already stripped them before you exported — that is a property of the file, not the anonymiser. And remember that anonymising the obvious fields is not the same as removing every trace: a free- text notes column can still mention a customer by name, so check those columns too.

Privacy

This is a privacy tool, so privacy is not a footnote — it is the design. Every step, detecting patterns, picking replacement names, masking card digits and serialising the result, happens as JavaScript on your own device. The data you paste or drop is never uploaded, never stored and never logged. That is the only honest way to build an anonymiser: the tool that strips your sensitive data should never be the tool that collects it.

Frequently asked questions

Is my data uploaded when I anonymise it?
No — and that is the whole point of a client-side anonymiser. The text you paste or the file you drop is read and rewritten by JavaScript running inside your own browser. Nothing is sent to a server, nothing is stored between visits and nothing is logged. You can confirm it in your browser's Network tab: anonymising produces no network requests. This is exactly why you can use it on a real customer list — you would never paste that list into a tool that processes it on someone else's server.
Does it find names automatically in free text?
Not reliably, and the tool is honest about that. Spotting a person's name in unstructured text needs language models, and getting it wrong both ways — missing real names and rewriting ordinary words — is common. So names are handled two dependable ways instead: for CSV data you pick which columns hold names and those whole columns are replaced; for free text you type the exact names you want anonymised into a list. Emails, phone numbers and card numbers have clear patterns, so those are detected automatically.
What does 'consistent replacements' do?
With it on, the same original value always maps to the same placeholder everywhere in the data — so if jordan@acme.com appears in five rows, all five become the same safe address. That keeps the relationships in your dataset intact, which matters when you want the anonymised sample to still behave like real data. With it off, every match gets an independent random replacement, so repeated values no longer line up.
How are credit card numbers and phone numbers handled?
Runs of 13 to 16 digits — the length of common payment cards — are masked so only the last four digits remain, shown as --****-1234. Phone numbers are detected by their format, and you choose whether to scramble the digits while keeping the punctuation, or replace them with a fixed placeholder. The original numbers are never kept anywhere.
Should I trust the output without checking it?
No. Always review the anonymised output before you share it. Pattern matching is good but not perfect: an unusual phone format might be missed, a name might appear somewhere you did not list it, or a sensitive value might sit in a field the tool does not scan. Treat the tool as a fast first pass, then read the result and confirm every sensitive value is gone before the data leaves your hands.

Related tools