IS AN EMAIL ADDRESS PII?

Yes, in most cases. A personal email address such as jane.doe@example.com usually points to one person, so it is a direct identifier. A work address built from a person's name is still personal data under the GDPR. Only shared role addresses such as info@ or support@, which are not tied to one person, are generally outside the definition.

Zero retention: your data never leaves this browser. Verify it yourself in DevTools.

Loading the PII tools.

About this guide

Why Is an Email Address a Direct Identifier?

Most personal email addresses are used by one person, often contain their name, and are the key that links accounts across services. Under NIST SP 800-122, information that can distinguish or trace an individual is PII, and an email address does both. In the 2pii tier scale a personal email address is Tier 2, directly identifying.

Are Work Email Addresses PII?

Under the GDPR, yes when they relate to an identifiable person: jane.doe@company.com is personal data because it identifies Jane. Many US organizations treat work contact details as lower risk, because they are shared for business purposes, and the 2pii classifier rates a work email or phone as Tier 1. That is a judgment about risk, not a statement that work emails fall outside privacy law.

  • Name-based work addresses (jane.doe@) are personal data under the GDPR.
  • Role addresses (info@, support@, billing@) usually are not about a person.
  • Aliases that one person uses (jdoe-sales@) are personal again.

How Do CCPA, HIPAA, and Breach Laws Treat Email Addresses?

  • CCPA/CPRA: email addresses are listed among the identifiers in California's definition of personal information. An account log-in made of an email address with a password is sensitive personal information. See CCPA sources.
  • HIPAA: email addresses are one of the 18 Safe Harbor identifiers that must be removed to de-identify health data. See HIPAA sources.
  • State breach laws: an email address alone rarely triggers notification, but many states include an email or username combined with a password or security answer. See breach sources.

When Is an Email Address Low Risk?

Shared role addresses, published press or support contacts, and synthetic addresses on reserved domains such as example.com carry little or no personal risk. A personal address in a marketing list is still PII, and its risk grows with context: an email list for a clinic, a support group, or a debt collection agency reveals something about everyone on it.

How Should You Mask Email Addresses?

  1. Remove the email column when the recipient does not need to contact anyone.
  2. Use partial masking when people need to recognize the account: the domain often matters for troubleshooting.
  3. Use consistent tokens such as [EMAIL-1] in logs and AI prompts so the text still makes sense.
  4. Never share email addresses together with passwords or security answers.

The masking tool's partial style keeps the first letter and the domain (j*******@example.com). The scanner matches the standard email format anywhere in text, and you can see every match in the PII scanner before sharing. See also PII do's and don'ts.

Is This Legal Advice?

What Else Is on 2pii?

  • PII scanner: Paste text or open a TXT, CSV, JSON, or Word file and see every SSN, card, email, phone, birth date, address, and labelled name.
  • PII masking tool: Make a masked copy of text: keep the last four digits, replace with labels, or use consistent tokens, per category.
  • PII tier and impact classifier: Pick the data elements and quantity to get a Tier 0-3 rating, an estimated NIST SP 800-122 impact level, and the laws that may apply.
  • What is PII?: The NIST, GDPR, CCPA, and HIPAA definitions side by side, and what "linked" and "linkable" mean.
  • PII examples list: A practitioner list of PII examples sorted into direct identifiers, quasi-identifiers, and sensitive data.
  • PII sensitivity tiers: Public, Internal, Confidential, and Restricted labels mapped to Tier 0-3 and NIST impact levels, with handling rules.
  • PII do's and don'ts: Practical rules for handling PII in email, tickets, logs, test data, spreadsheets, and AI tools.
  • PII laws and regulators: Primary-source links for GLBA, HIPAA, COPPA, FERPA, NY SHIELD, CCPA/CPRA, the state privacy laws, and GDPR, each dated.
  • Is an IP address PII?: When an IP address is personal information under NIST, GDPR, CCPA, and HIPAA, and how to handle it in logs.
  • Is date of birth PII?: Why a birth date alone is linkable PII, why it becomes identifying with ZIP and sex, and how to mask it.
  • Is a ZIP code PII?: When a ZIP code is PII, the HIPAA three-digit ZIP rule, and the combinations that make it identifying.
  • Is a name PII?: Why a full name is PII, when a name alone is low risk, and how context turns a list of names into sensitive data.

Everything is on the 2pii home page. Part of the 2suite.io privacy-first ecosystem.

How Can You Verify That Your Data Never Leaves This Browser?

You do not have to take our word for it. Browser developer tools list every request a page makes, so you can watch 2pii work and confirm that your text is never sent anywhere. The check takes about a minute.

  1. Open your browser developer tools with F12, or Cmd+Option+I on a Mac, and select the Network tab.
  2. Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. No text has been opened yet, so none of them can contain your data.
  3. Click the clear icon in the Network tab so that the log is empty.
  4. Open the PII scanner, paste some text or open a file, and download the report.
  5. Look at the Network tab again. It is still empty. Scanning, masking, classifying, and saving made no request at all. The tools also show a live counter, read from your browser's own Resource Timing records, of the requests made since your text was opened. For extra proof, turn on offline mode after the page loads: every tool keeps working.

Text you paste or open is held in this tab's memory, checked by code that is already on the page, and handed back to you as a copy or a download. It is never uploaded, never stored in the browser, and gone when you close the tab. The only other request the site can make is the feedback form, and only when you submit it.

The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint, so even a bug could not send your data elsewhere.

Frequently Asked Questions

Is a work email address personal data?

Under the GDPR, yes, when it identifies a person, as jane.doe@company.com does. Many US organizations treat work contact details as lower risk, but they still relate to a person.

Is info@ or support@ an email address PII?

Generally no. A shared role address that is not tied to one person does not identify an individual.

Does leaking email addresses require breach notification?

An email address alone rarely triggers US state breach notification, but many states include an email or username combined with a password or security answer.

How does 2pii mask an email address?

The partial style keeps the first letter of the local part and the full domain, the label style writes [EMAIL], and the token style writes [EMAIL-1], reusing the same token for the same address.

Was this helpful?