What Anonymize Text helps you do
Replace emails, URLs and phone-like numbers with placeholders before you share a sample. It reduces the chance of leaking personal data when you paste text into a ticket, forum or chat. It is a convenience filter, not a certified redaction tool, so review the result before publishing it.
Anonymization runs locally in your browser. The original text is not sent to Haivix.
How it works
These tools scan the pasted text in the browser with a pattern or parser and return the matches in first-seen order. Extraction is a candidate list, not a verification step: an email-shaped string may not be deliverable, a URL may not resolve, and a number may be part of a date or an identifier. Nothing is uploaded, and the source text is never changed. The result is a snapshot of the pasted text; editing the source afterwards does not update the list.
How to use Anonymize Text
- Paste the text that contains personal or sensitive values.
- Replace emails, URLs and phone-like numbers with placeholders.
- Review the result for names or other identifiers the filter does not cover.
- Copy the anonymized version to share.
When to use it
- Share a log or config sample without exposing real addresses.
- Prepare test data that resembles production but is not real.
- Remove contact details before posting an excerpt publicly.
- Sanitize a support ticket before attaching it to a bug report.
- Prepare a screenshot or text sample for documentation.
- Reduce accidental PII in a copied error message.
When not to use it
- Do not use it as the only control for regulated or confidential data.
- Do not assume names, addresses or account IDs are removed.
- Do not share the result without reading it first.
Example
A real email address becomes [email], a link becomes [url], and a phone number becomes [phone], leaving the rest of the sentence unchanged. A name or a postal address is not replaced, so the text still needs a manual review. A date that looks like a phone grouping can be caught by the phone placeholder.
What you can do with Anonymize Text
- Replace email addresses with [email].
- Replace URLs with [url].
- Replace phone-like numbers with [phone].
- Keep the surrounding text and structure.
- Copy the anonymized version to share.
- Run the replacement locally with no upload.
Example: check the matches on a sample
Paste a short sample first and count the expected matches by eye. Compare that count with the result before running a large file, because a missing match is easier to spot in a small sample.
Read a few matches in context to catch false positives. A phone-like number inside an order ID, or a URL inside a code snippet, is common and should not be treated as a contact or a live link.
Copy the list and keep the original. If the extraction feeds a mail merge or a report, verify a sample of the destinations rather than assuming every match is valid.
If the result is empty, check the input format before assuming the tool is broken. A bare domain without http, an address split across a line, or JSON with a trailing comma are common reasons for no matches.
For a list that will be contacted or published, keep the source and the extracted list side by side. The source is the only way to resolve a questionable match or explain why one was missed.
What to know before you start
- It is a convenience filter, not a certified redaction tool, and can miss unusual formats.
- It does not remove names, addresses or other identifiers, so review before sharing.
- The placeholders are plain text and do not preserve the original values.
- It can over-match numbers that look like phone numbers.
Common mistakes
- Assuming all personal data is removed.
- Sharing the result without reading it.
- Expecting names, addresses or account numbers to be replaced.
- Treating the placeholders as reversible or recoverable.
Troubleshooting
If an email remains, it may be obfuscated or split across a line.
If a harmless number became [phone], the pattern matched a phone-like grouping; edit it back if needed.
If a URL remains, it may not start with http, https or www.
If names remain, the tool does not detect them; remove them manually.
Related standards and documentation
- Email addresses follow RFC 5322, but the tool uses a practical pattern rather than a full parser.
- URLs follow RFC 3986; the extractor recognises http, https and www forms.
- Regular-expression matching is not a validation service and can miss unusual formats.
- No extraction tool can prove that a match is valid or safe; that requires a separate check.
- Test on a small sample first.
- Check false positives in context.
- Review before a mail merge or report.
- Empty output usually means the format, not the tool.