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.
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.
Loading the PII tools.
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.
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.
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.
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.
Education only, not legal advice. 2pii explains how privacy and security practitioners commonly treat personal data and points to the primary sources. Whether a law applies to your organization depends on facts only you and your counsel know. Last reviewed 2026-11-15; the law directory records the date each source link was last checked.
Everything is on the 2pii home page. Part of the 2suite.io privacy-first ecosystem.
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.
F12, or Cmd+Option+I on a Mac, and select the Network tab.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.
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.
Generally no. A shared role address that is not tied to one person does not identify an individual.
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.
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.