PII CLASSIFIER

Tick the data elements in a data set, say how many people it covers, and answer a few context questions. The classifier gives a 2pii tier from 0 to 3, an estimated NIST SP 800-122 confidentiality impact level with every factor shown, a suggested classification label with handling rules, and the laws that may apply, each linked to its primary source.

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

Loading the PII tools.

About the PII tier and impact classifier

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. Tick some data elements in the classifier above and copy the summary.
  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.

What Do the 2pii Tiers Mean?

  • Tier 0, not identifying: nothing in the set relates to an identifiable person, such as aggregate statistics.
  • Tier 1, linkable: quasi-identifiers such as a birth date, ZIP code, IP address, or job title that point to a person only when combined with other data.
  • Tier 2, directly identifying: a name, personal email, phone number, or home address, or a combination that singles people out, such as birth date with ZIP code and sex.
  • Tier 3, sensitive or high impact: Social Security and government ID numbers, financial account and card data, credentials, health, biometric, and genetic data, and other special categories, and any personal data about children under 13.

The tiers are 2pii's own scale, not a NIST model. They map to the common Public, Internal, Confidential, and Restricted labels explained in the sensitivity tiers guide.

How Is the NIST Impact Level Estimated?

NIST SP 800-122 asks organizations to set a PII confidentiality impact level of low, moderate, or high, using the FIPS 199 categories, and lists six factors to weigh. The classifier scores each one and shows the points:

  1. Identifiability: can the data identify specific people directly, or only when linked?
  2. Quantity of PII: how many people are in the set?
  3. Data field sensitivity: are there fields such as SSNs, financial accounts, or health data?
  4. Context of use: does being on the list reveal something sensitive by itself?
  5. Obligations to protect confidentiality: do specific laws or contracts apply?
  6. Access to and location of PII: is the data on laptops, reachable from the internet, or shared with third parties?

A total of 0-3 points is estimated as low, 4-6 as moderate, and 7 or more as high. Sensitive fields always raise the estimate to at least moderate, and to high for more than 1,000 people. NIST publishes the factors, not point values, so treat the result as a reasoned starting point for your own categorization. The publication itself is NIST SP 800-122 on the NIST website.

Which Laws Can the Classifier Flag?

Based on the elements and your context answers, the classifier flags laws and standards that may apply and says why: GLBA for customer financial data at a financial institution, HIPAA for health information at a covered entity or business associate, COPPA for children under 13, FERPA for student education records, the GDPR for people in the EU or EEA, state breach notification laws for the identifier combinations they define, state privacy laws for sensitive data, the CCPA/CPRA for California's sensitive personal information, and PCI DSS for card numbers. Each flag links to the primary sources in the laws directory.

Can You Classify What the Scanner Found?

Yes. After a scan, press Classify what was found on the PII scanner. The classifier opens on the same page with the detected categories already ticked: SSNs, ITINs, card and bank numbers, birth dates, emails, phones, addresses, names, and IP addresses. Then add what the scanner cannot see, such as health details or the context questions. The handoff happens in the page's memory only.

What Does the Result Not Decide?

The classifier does not know your contracts, your industry's rules, the states your data subjects live in, or the exemptions that may apply to your organization, and it does not decide whether you have a reportable breach. It gives a consistent, explained starting point that a privacy, security, or legal reviewer can confirm or adjust. The copied summary states its assumptions so the reviewer can see them.

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

Frequently Asked Questions

Is the NIST impact level official?

No. NIST SP 800-122 lists the factors and leaves the level to each organization. The classifier gives an explained estimate from those factors, which your organization should confirm.

Why are there two ratings, a tier and an impact level?

The tier describes how identifying and sensitive the data elements are. The impact level also weighs how many people are affected, the context, legal obligations, and exposure, as NIST SP 800-122 describes.

Does the classifier send my answers anywhere?

No. The answers stay in your browser tab. Copying or downloading the summary happens locally too.

Why does data about children rate as Tier 3?

COPPA and most state privacy laws give personal data about children extra protection, so any personal data collected online from children under 13 is treated as sensitive.

Can I use the result as legal advice?

No. It is an education tool. Whether a law applies depends on facts the tool does not ask about, so confirm with your privacy or legal team.

Was this helpful?