Support ticket exports
Customer email addresses appear throughout ticket threads and agent replies.
Strip email addresses from logs, forms, and exportsβwith optional replacement text for redacted placeholders.
Remove Emails
Remove, mask, extract, or redact email addresses with live domain analysis.
Detected domains
Paste or type text containing email addresses to clean.
Your text stays in your browser β nothing is uploaded.
Email list β Masked output
Before
john@example.com sales@example.com support@gmail.com
After (mask)
***@example.com ***@example.com ***@gmail.com
Customer email addresses appear throughout ticket threads and agent replies.
Contact dumps mix names, emails, and notes that need redaction before sharing.
Mailing list exports contain thousands of addresses requiring privacy cleanup.
AI-generated text may include placeholder or real email addresses in examples.
Form submission logs store submitter emails inline with message content.
Spreadsheet columns pasted as text carry email fields mixed with other data.
Delete every detected address while keeping surrounding text intact.
Swap each email for a placeholder like [email] or [redacted].
Output a list of every address found β useful for audits and mailing list review.
Replace full addresses with domain only β e.g. example.com.
Hide usernames while keeping domains visible β ***@example.com.
Show how often each address appears β john@example.com (3).
| Scenario | Before | After |
|---|---|---|
| Simple remove | john@example.com |
β |
| Replace | john@example.com |
[email] |
| Mask | john@example.com |
***@example.com |
| Preserve domain | john@example.com |
example.com |
| Extract only | text john@example.com text |
john@example.com |
| Frequency view | repeated emails |
john@example.com (3) |
Email addresses are personally identifiable information. Removing or masking them protects privacy when sharing logs, datasets, and exports publicly.
Redact personal data before publishing documents or sharing with third parties.
Sanitize research and open-data releases so no contact details leak through.
Prepare ticket excerpts for training, documentation, or bug reports.
Clean Slack, Discord, and team chat dumps before archiving or sharing.
Create demo-safe copies of contact records without real customer emails.
Strip PII from corpora used for model fine-tuning and evaluation sets.
Consumer addresses on Gmail, Outlook, Yahoo, and iCloud.
john@gmail.com
Tags after the local part for filtering and tracking subscriptions.
john+news@gmail.com
Company domain addresses used for sales, support, and team inboxes.
sales@company.com
Clickable mailto: URLs embedded in HTML and rich text exports.
mailto:support@company.com
Addresses on mail subdomains or regional company hosts.
admin@mail.company.com
Forwarding addresses and role-based inboxes like info@ or hello@.
info@company.com
The workspace counts how many addresses appear on each domain β useful for spotting consumer vs. business email patterns in your paste.
Most common consumer provider in mixed exports and chat logs.
Microsoft personal and work addresses from Office 365 users.
Legacy consumer addresses still common in older subscriber lists.
Apple ecosystem addresses from mobile and macOS users.
Custom domains like company.com indicate business contacts.
Notes & Limitations
The tool detects standard addresses with a local part, @ symbol, and domain β including plus-addressed emails like user+tag@domain.com and subdomain hosts.
Yes. Select Extract emails only mode to output a list of every address found. Enable Remove duplicates or Frequency view for refined lists.
Yes. Preserve domains mode replaces john@example.com with example.com so you keep provider context without exposing usernames.
Yes. Select Replace with custom text and enter your placeholder such as [email] or [redacted] in the replacement field.
Yes. Addresses with plus tags like john+newsletter@gmail.com match the standard email pattern and are processed like any other address.
Yes. Select Remove mailto links mode to strip mailto: URLs. Other modes also transform emails found inside mailto links.
Yes. Mask local part mode converts john@example.com to ***@example.com, hiding the username while keeping the domain visible.
Yes. Enable Frequency view in extract mode to see counts like john@example.com (3) for repeated addresses.
Yes. Use extract mode to build your list, then copy the output or download it as a .txt file.
No. All email detection and redaction runs entirely in your browser using JavaScript. Your text never leaves your device.