b2KIT

Text Anonymizer

Anonymize text by replacing personal names, addresses, phone numbers, and emails with placeholder tokens.

Tested tool guide Tested browser tools Checked August 16, 2026

What Text Anonymizer does and how it behaves

This tool takes a block of pasted text and swaps the personal details in it (names, addresses, phone numbers, and email addresses) for placeholder tokens, leaving the rest of the wording intact so the result still reads like the original. Because it runs entirely in the browser, nothing you paste is uploaded, which makes it a quick way to scrub a conversation before sharing it. The thing people most often get wrong is assuming the output is fully anonymized: the scan replaces what it recognizes, and it cannot see every possible way a detail can be written.

How the result is produced

1

What the scan covers

The tool scans the pasted text for the four categories in their common written forms: email addresses, phone numbers, street addresses, and people's names. Every recognized value is replaced with a placeholder token. Anything the scan does not match, including the words and punctuation between the values, is left exactly as written, so the result stays readable as a normal piece of text with the specific details taken out.

2

What slips through

Recognition depends on the text matching the written forms the scan expects, so unusual formats (a phone number written out as words, an international address layout, a misspelled email) can stay in the output. So can anything outside the four categories: usernames, dates, and account numbers pass through unchanged. The tool only replaces strings it recognizes as one of the four types.

Good uses

  • Scrubbing a customer-support conversation before pasting it into a shared ticket, bug report, or forum thread that people outside your team will read.
  • Building demo or test data from a real email or document when you want realistic wording without real contact details in it.
  • Redacting the contact details from a testimonial, case study, or screenshot caption before publishing it or sending it to a third party.

Limits and checks

  • The scan replaces what it recognizes, so an unusual name spelling, a phone number in a non-standard format, or an address missing its street suffix can pass through. Anything outside the four categories (usernames, dates, account numbers) is never touched.
  • Token replacement is not removal and not encryption. If the same entity receives the same token across the document, the text keeps its structure, and a reader who knows one real identity can in principle infer the others. Treat the result as scrubbed for display, not as anonymous data.
  • The tool does not delete the original: the input stays in the page, and copies may sit in your clipboard or browser history, so producing a scrubbed result does not remove the source text. Clear those yourself if the original must not survive.

Common questions

Is my text uploaded to a server?

No. The tool runs entirely in the browser, and nothing you paste is uploaded. That does not make the whole chain invisible: the input text stays on screen in the page, and copies may linger in your clipboard or browser history, so close the page and clear those when you are done with sensitive material.

Can I treat the result as anonymized data?

No, not under a strict definition. Replacing values with tokens is what the GDPR calls pseudonymisation: the details the scan found are gone, but the tokens could in principle be linked back, and anything written in an unusual format survives untouched. For data that truly cannot be re-identified, review the output yourself, delete or generalize what remains, and only then rely on it.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools