PII EXAMPLES

This is a working list of personally identifiable information, sorted the way a security or privacy team uses it: what identifies a person on its own, what identifies people in combination, what causes serious harm when exposed, and what is usually not PII by itself. Use it to build a data inventory, write a classification policy, or decide what a scanner should look for.

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

Loading the PII tools.

About this guide

Which Data Elements Are Direct Identifiers?

Direct identifiers point to one specific person without any other data. If any of these is present, the record is PII under every framework covered on this site.

  • Full name, and maiden name or alias when tied to a person.
  • Social Security number, ITIN, and other taxpayer identification numbers.
  • Driver's license, state ID, passport, and military ID numbers.
  • Personal email address and personal phone number.
  • Home street address.
  • Full-face photographs and other images that show a recognizable person.
  • Biometric records such as fingerprints, face geometry, or voiceprints.
  • Account numbers, employee IDs, student IDs, medical record numbers, and health plan member numbers.
  • Usernames and online account handles linked to a real person.

Which Data Elements Are Quasi-Identifiers?

Quasi-identifiers, also called indirect identifiers, do not identify anyone alone but narrow the field. Two or three of them together frequently single out one person. Sweeney's research (2000) estimated that about 87% of the US population is likely uniquely identified by five-digit ZIP code, sex, and date of birth.

  • Date of birth, and age when combined with other details. See is date of birth PII?
  • ZIP code and city. See is a ZIP code PII?
  • Sex or gender, race, and ethnicity (race and ethnicity are also sensitive).
  • Employer, job title, and work location.
  • IP address, device ID, cookie ID, and advertising ID. See is an IP address PII?
  • Vehicle license plate and VIN.
  • Rare attributes, such as an unusual job title in a small town.

Which PII Is Sensitive or High Impact?

Sensitive PII causes serious harm, such as identity theft, financial loss, discrimination, or embarrassment, when it is exposed. These fields usually drive a data set to the top of any classification scheme and to a moderate or high NIST impact level.

  • SSNs, government ID numbers, and taxpayer IDs, which are central to most state breach notification laws.
  • Payment card numbers and bank account numbers, especially with a PIN, security code, or password. Card data also falls under PCI DSS.
  • Medical records, diagnoses, health insurance numbers, and genetic data, which are PHI when held under HIPAA.
  • Biometric data used to identify a person.
  • Online credentials: a username or email with a password or security answer.
  • Precise geolocation.
  • Racial or ethnic origin, religious beliefs, sexual orientation, union membership, citizenship or immigration status, and criminal history.
  • Information about children, which COPPA and many state laws protect more strictly.

What Is Usually Not PII on Its Own?

Some data relates to no identifiable person, or to an organization rather than a person. It is usually not PII, although the caveats matter.

  • Aggregate statistics with no individual rows, such as monthly totals. Small counts (a cell with one or two people) can still identify someone.
  • Business entity data such as a company name, EIN, or main office number. A sole proprietor's EIN or business address can be personal, though.
  • Role email addresses such as info@ or support@ that are not tied to one person.
  • Truly de-identified data that cannot reasonably be linked back to a person.
  • Device or system data with no link to a user, such as a server's own hostname.

How Do You Find These Examples in Real Data?

  1. Start with structured sources: database schemas, CSV exports, and column names such as dob, ssn, or email.
  2. Then check unstructured places where PII leaks: support tickets, chat, logs, spreadsheets on file shares, and AI prompts.
  3. Paste or open a sample in the PII scanner, which detects SSNs, ITINs, EINs, card numbers, bank numbers, emails, phones, labelled birth dates, street addresses, IP addresses, and labelled names, all in your browser.
  4. Record which elements each system holds and classify the set with the classifier.

Pattern scanning will not find everything: unlabelled names, health details written in plain language, and ID formats that vary by state need human review.

Why Does Sorting PII Into Groups Help?

Groups turn a long list into decisions. Direct identifiers tell you whether a data set is PII at all. Quasi-identifiers tell you whether "anonymous" data really is. Sensitive fields tell you how much protection the set needs and which laws are likely to apply. The sensitivity tiers guide maps these groups to Public, Internal, Confidential, and Restricted handling rules, and the what is PII guide explains the underlying definitions.

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 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 are the most common examples of PII?

Full names, Social Security numbers, email addresses, phone numbers, home addresses, dates of birth, driver's license numbers, and financial account numbers are the most common examples.

Is an employee ID number PII?

Yes. An employee ID is assigned to one person and can be traced back to them through HR records, so it is a direct identifier inside the organization.

Is a company EIN PII?

Usually not, because it identifies a business. A sole proprietor's EIN can relate to a person, so treat it with care in that case.

Are aggregate statistics PII?

Generally no, as long as they contain no individual rows. Very small counts can identify a person, so suppress or combine cells that describe only a few people.

Which PII is most sensitive?

SSNs and government ID numbers, financial account numbers with access codes, medical and genetic data, biometric data, online credentials, and data about children are generally treated as the most sensitive.

Was this helpful?