WHAT IS PII?

Personally identifiable information (PII) is information that can identify a specific person, either on its own or when combined with other data. The exact boundary depends on which framework you are working under: NIST, the GDPR, the CCPA, and HIPAA each draw it differently. This guide puts the definitions side by side so a security or privacy team can decide what to protect, and how hard.

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

Loading the PII tools.

About this guide

How Does NIST Define PII?

NIST SP 800-122, the federal guide to protecting the confidentiality of PII, defines it as any information about an individual maintained by an agency, including (1) any information that can be used to distinguish or trace an individual's identity, such as name, Social Security number, date and place of birth, mother's maiden name, or biometric records; and (2) any other information that is linked or linkable to an individual, such as medical, educational, financial, and employment information.

"Distinguish" means telling one person apart from others; "trace" means following a person's activity or status across records. The definition is broad on purpose: it covers data that identifies nobody on its own today but could be connected to a person tomorrow. NIST then asks agencies to rate each PII set with a confidentiality impact level of low, moderate, or high, the same levels used in FIPS 199. See the frameworks sources.

What Is the Difference Between Linked and Linkable Information?

Linked information is already logically associated with other information about the person in the same system, such as a diagnosis stored in the same record as a patient name. Linkable information could be associated with a person if someone combined it with another source, such as a birth date and ZIP code in an anonymous survey that can be joined with a voter roll.

For security teams, the practical point is that removing names does not end the obligation. A data set of birth dates, ZIP codes, and sex is linkable: research by Latanya Sweeney (2000) estimated that about 87% of the US population is likely uniquely identified by five-digit ZIP code, sex, and date of birth together. The ZIP code and date of birth answer pages go deeper.

How Do GDPR, CCPA, and HIPAA Define Personal Data?

  • GDPR. Article 4(1) defines personal data as any information relating to an identified or identifiable natural person. Online identifiers such as IP addresses and cookie IDs can qualify (Recital 30). The scope is wider than most US definitions. See GDPR sources.
  • CCPA/CPRA. California defines personal information as information that identifies, relates to, describes, or could reasonably be linked with a consumer or household, and lists examples including names, email addresses, IP addresses, and unique identifiers. A separate category, sensitive personal information, covers items such as SSNs, account log-ins, precise geolocation, and health data. See CCPA sources.
  • HIPAA. HIPAA protects protected health information (PHI): individually identifiable health information held by a covered entity or business associate. The Safe Harbor de-identification method lists 18 identifiers that must be removed. See HIPAA sources.
  • State breach laws. Every US state has a breach notification law. Most define personal information narrowly, as a first name or initial and last name combined with an SSN, a driver's license or state ID number, or a financial account or card number with any required code. See breach sources.

What Are Direct Identifiers and Quasi-Identifiers?

A direct identifier points to one person by itself: a full name, an SSN, a personal email address, a phone number, a passport number, a full-face photo. A quasi-identifier does not identify anyone alone but narrows the field: date of birth, ZIP code, sex, job title, employer, or an IP address. Several quasi-identifiers together often single a person out, which is why de-identification has to look at combinations, not single fields.

Sensitive data is a third axis. An SSN, a bank account number, a diagnosis, or biometric data causes serious harm when exposed, whatever else is in the record. The PII examples list sorts common fields into these groups.

Is PII the Same as Personal Data or PHI?

Not exactly. "PII" is the US federal and industry term and tends to focus on identifiability. "Personal data" (GDPR) and "personal information" (CCPA) are broader legal terms that include anything relating to an identifiable person, such as preferences or behavior. PHI is narrower in scope (health information held by HIPAA covered entities and business associates) but includes identifiers such as dates and device numbers that many teams would not think of as PII.

In practice, a program that protects data to the broadest standard it is subject to avoids arguments about which label applies. Treat anything that relates to a person as in scope, then decide how much protection it needs.

Why Does the Definition Matter to Security Teams?

The definition decides what lands in scope for encryption, access control, logging, retention, incident response, and breach notification. A team that only protects names and SSNs will miss IP addresses in web logs, birth dates in test data, and email addresses in support tickets, all of which can be PII under one framework or another.

  1. Inventory where PII lives: databases, exports, logs, tickets, chat, file shares, and AI tools.
  2. Classify each set with the PII classifier to get a tier, an estimated NIST impact level, and the laws that may apply.
  3. Apply handling rules from the sensitivity tiers guide.
  4. Scan text before it leaves a controlled system with the PII scanner, and share masked copies made with the masking tool.

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.
  • 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.
  • 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

What does PII stand for?

PII stands for personally identifiable information: information that can be used to distinguish or trace a person's identity, alone or when combined with other information.

Is a name alone PII?

Yes, a full name is PII under NIST because it can distinguish an individual, although a name by itself is usually low risk. Context, such as a list of names of people in a treatment program, can make it sensitive.

Is anonymized data PII?

Data that has been truly de-identified, so that it cannot reasonably be linked back to a person, is generally not PII. Removing names alone is not enough, because quasi-identifiers such as birth date, ZIP code, and sex can re-identify people.

Does NIST define PII tiers?

No. NIST SP 800-122 defines PII confidentiality impact levels of low, moderate, and high. The Tier 0 to 3 scale on 2pii is its own identifiability and sensitivity scale, shown alongside the NIST estimate.

Is PII the same as personal data under GDPR?

They overlap but are not the same. GDPR personal data is any information relating to an identified or identifiable person, which is usually broader than how US organizations use the term PII.

Was this helpful?