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.
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.
Loading the PII tools.
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.
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.
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.
In the classifier, answer yes to "the list itself reveals something sensitive" and the impact estimate rises.
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.
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.
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.
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.
Yes. Public availability does not stop information from being PII or personal data, although it usually lowers the risk of handling it.
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.
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.