1. Home
  2. Spreadsheet & data tools
  3. Anonymize CSV Data

Anonymize CSV Data

Share a dataset with a vendor, a student or a support team without handing over names, emails and phone numbers. Choose what happens to each column and keep the file usable.

Free, no sign-up. Runs in your browser: nothing is uploaded.

How to use Anonymize CSV Data

  1. Drop the CSV or Excel file.
  2. Check the suggested action for each column and adjust it.
  3. Download the masked file.

Features

  • Actions per column: remove, redact, mask, hash, pseudonym, generalize, shuffle
  • Sensitive columns detected from headers and values
  • Keyed HMAC-SHA-256 hashes: the same value always gives the same token
  • Dates reduced to year or month, numbers rounded, ZIP codes shortened
  • Processed entirely in your browser

Supported formats

You can open

  • CSV
  • TSV
  • TXT
  • XLSX
  • Pasted data

You get

  • CSV
  • XLSX
  • TSV

Private by design

Your files are opened and processed by your browser on this device. They are never uploaded to openWorkstand or anyone else, so the Anonymize CSV Data is safe for contracts, IDs, photos and work documents. After you have used it once while online, it also works without an internet connection. How local processing works

Good to know

  • Masking names, emails and IDs is pseudonymization, not full anonymization: combinations of the remaining columns can still identify people.

Guide

Masking personal data in CSV and Excel files before sharing them

Sharing a dataset is often necessary: a vendor needs a customer export to debug an import, a student needs realistic data for a thesis, a support team needs an example file. Sending real names, emails and phone numbers along is risky and often against data protection rules. This tool masks personal data column by column so the file stays useful while the people in it are protected.

A suggestion for every column

When you open a file, each column gets a suggested action based on its name and values. Email columns are masked with the domain kept, phones and account numbers keep their last digits, name columns get consistent pseudonyms, birth dates are reduced to the year, street addresses are redacted, ZIP codes are shortened, IP addresses are hashed and salaries rounded. Columns that look harmless are kept. Review every suggestion, since you know your data best.

Removing and redacting

“Remove the column” drops it from the output entirely, the safest choice for anything the recipient does not need. “Replace with [REDACTED]” keeps the column but hides its content, useful when a template requires the column to exist.

Masking

“Mask, keep the last characters” replaces letters and digits with dots but keeps the last few characters and all punctuation, so a phone number still looks like a phone number and a card number shows its last four digits, as on a receipt. “Mask email, keep the domain” shows the first letter and the domain, like a•••••@example.com, which keeps domain statistics possible.

Hashing with a secret key

Hashing replaces each value with a token computed by HMAC-SHA-256. The same value always gives the same token, so counts, joins and duplicate checks still work. Because the token depends on a secret key, nobody without the key can recompute tokens from a list of known emails. A random key is created for you; keep it if you need to mask more files consistently, or discard it for one-off sharing.

Pseudonyms

Pseudonyms replace each distinct name with a label like Person 01, Person 02, consistently throughout the file and ignoring upper/lower case. They read naturally in reports and demos.

Generalizing

“Year only” and “Year and month” coarsen dates of birth or visit dates. “Round to a step” turns salaries or ages into bands, such as 48,250 into 48,000. “Keep only the first characters” shortens ZIP codes to a region, such as 02134 to 021. Generalizing keeps data useful for statistics while making individuals harder to recognize.

Shuffling

“Shuffle the values between rows” keeps every value but moves them to other rows, which preserves the overall distribution of a column while breaking the link to each person.

Not anonymous by default

Masking direct identifiers is pseudonymization. Under laws like the GDPR, pseudonymized data is still personal data. Remove what is not needed, generalize what remains, and follow your organization’s rules.

Before you send the file

Open the masked file and read a few rows as if you were the recipient. Free-text columns such as notes or comments often contain names, phone numbers or addresses typed by staff; remove or redact them unless they are essential.

Generate realistic fake data instead with the Mock Data Generator. For one-off hashes, use the Hash Generator; for documents, Redact PDF removes text permanently.

Checked against the current version of the Anonymize CSV Data on .

Troubleshooting

The file does not open

Check that it is one of the supported formats above and opens in another app. Damaged files and password-protected PDFs cannot be read until they are repaired or unlocked.

It is slow or stops on a very large file

Everything runs on your device, so speed depends on its memory. Close other tabs, use a computer rather than a phone, or split the file into smaller parts first.

The download did not start

Look for your browser’s download bar or icon. Some browsers ask once before a site may download files; allow it and click the button again.

Frequently asked questions

Can masked data be traced back to people?

Sometimes. Direct identifiers like names and emails are hidden, but combinations of other columns, such as birth year, ZIP code, job title and gender, can still single out a person. Remove or coarsen those quasi-identifiers too, and share only the columns the recipient needs.

How can two files masked separately still be joined?

Use the same secret key for both. Hashes of the same email or ID are then identical in both files, so they can be matched without revealing the original values. Keep the key private.

Is the result anonymous?

Not automatically. Masking direct identifiers is pseudonymization; people can still be re-identified from combinations such as birth year, ZIP code and job. Remove or generalize those columns too, and follow your data protection rules.

Why does hashing need a secret key?

Without a key, anyone could hash a list of known emails and match them. With a secret key, only someone who knows it can recompute the tokens. Keep the key private, or use a new random one each time.

Keep working with the result

After you download, choose “Save to Workstand” to keep the result in a folder on your computer, attach it to a project and create a follow-up task. It is saved by your browser, not uploaded.