IS A NAME PII?

Yes. A full name is PII: NIST lists name first among its examples of information that can distinguish an individual, and the GDPR and CCPA treat names as personal data. A name on its own is usually low risk because names are shared and widely known. The risk comes from what the name is attached to, or what a list of names reveals about the people on it.

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

Loading the PII tools.

About this guide

Why Is a Name PII Under NIST?

NIST SP 800-122 defines PII as information that can be used to distinguish or trace an individual's identity, and gives name as its first example. A common name may match many people, but together with an employer, a city, or a photo it usually points to one. In the 2pii tier scale a full name is Tier 2, directly identifying.

How Do GDPR, CCPA, and HIPAA Treat Names?

  • GDPR: a name relates to an identified person, so it is personal data under Article 4(1). See GDPR sources.
  • CCPA/CPRA: real name and alias are listed among the identifiers in California's definition of personal information. See CCPA sources.
  • HIPAA: names are the first of the 18 Safe Harbor identifiers that must be removed to de-identify health data. See HIPAA sources.
  • State breach laws: a name is the anchor of most definitions: first name or first initial and last name combined with an SSN, a driver's license or state ID number, or a financial account number with any required code. See breach sources.

When Is a Name Alone Low Risk?

A name with nothing sensitive attached, such as a staff directory, a meeting attendee list, or a byline, is usually low risk and is often published on purpose. First names alone, or initials, are lower risk still. The 2pii classifier rates names plus work contact details for a few hundred people as a low NIST impact estimate.

How Does Context Make a List of Names Sensitive?

NIST SP 800-122 names context of use as one of its impact factors. The same names become sensitive when the list itself says something about the people on it.

  • Patients of a clinic or members of a treatment program.
  • Employees under investigation or selected for layoff.
  • Donors to a political or religious cause.
  • Children enrolled in a program.

In the classifier, answer yes to "the list itself reveals something sensitive" and the impact estimate rises.

How Should You Mask Names?

  1. Remove names when the recipient does not need to know who is involved.
  2. Use initials when people need to tell records apart but not identify them.
  3. Use consistent tokens such as [NAME-1] in logs and AI prompts so the narrative still makes sense.
  4. Read free text yourself before sharing; names hide in notes, signatures, and quoted email.

The masking tool's partial style keeps initials (Jane Doe becomes J*** D**), and its token style gives the same name the same token everywhere.

How Does the 2pii Scanner Find Names?

Finding names reliably needs a language model, which would mean a large download or sending text to a server. 2pii does neither. The PII scanner finds names only when they are labelled (Name:, Customer:, Patient:), when they follow a title such as Mr., Ms., or Dr., or when they sit in a column called name, first_name, last_name, or similar. Unlabelled names in prose are not detected, and the results say so. See PII examples for other identifiers to check.

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 an email address PII?: Why a personal email address is direct PII, how work and role addresses differ, and what that means for logs and lists.
  • 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.

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 first name alone PII?

A first name alone rarely identifies anyone, so it is low risk, but combined with other details such as an employer or a photo it can point to one person.

Is a name in a public directory still PII?

Yes. Public availability does not stop information from being PII or personal data, although it usually lowers the risk of handling it.

Why does the scanner not find every name?

Reliable name detection needs a language model. The scanner runs entirely in your browser with no model, so it finds names only when they are labelled, after a title, or in a name column.

Can a list of names be sensitive data?

Yes. When the list reveals something about the people on it, such as patients of a clinic or employees under investigation, it deserves the handling of sensitive data.

Was this helpful?