PII SENSITIVITY TIERS

Most organizations sort data into four labels, Public, Internal, Confidential, and Restricted, and attach handling rules to each. This guide maps those labels to the 2pii Tier 0 to 3 identifiability scale and to the NIST SP 800-122 confidentiality impact levels, then lists practical handling rules for each label. The labels are a common organizational convention, not a NIST or legal standard, so adapt them to your own policy.

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

Loading the PII tools.

About this guide

What Are the Four Sensitivity Labels?

Label2pii tierTypical NIST impactExamples
PublicTier 0: not identifyingNot applicable (no PII)Published statistics, press releases, aggregate counts
InternalTier 1: linkableLowWork email directories, IP addresses in logs, ZIP codes alone
ConfidentialTier 2: directly identifyingLow to moderateCustomer lists with names, emails, phones, and addresses
RestrictedTier 3: sensitive or high impactModerate to highSSNs, card and bank numbers, medical records, credentials, children's data

The NIST column is a typical outcome, not a rule. NIST SP 800-122 sets the impact level from six factors, so a small Confidential set can be low impact and a large one can be moderate or high.

How Does the 2pii Tier Scale Work?

The Tier 0 to 3 scale is 2pii's own way of describing how identifying and how harmful a data set is. NIST does not define tiers, and the classifier always shows the two scales separately.

  • Tier 0, not identifying: no element relates to an identifiable person, such as aggregate statistics.
  • Tier 1, linkable: quasi-identifiers such as date of birth, ZIP code, IP address, or job title that identify people only in combination.
  • Tier 2, directly identifying: a name, personal email, phone, or home address, or a combination such as date of birth, ZIP code, and sex that singles people out.
  • Tier 3, sensitive or high impact: SSNs, government IDs, financial account data, medical, genetic, or biometric data, credentials, special categories such as religion or sexual orientation, and any data about children.

How Do NIST Impact Levels Fit In?

NIST SP 800-122 asks organizations to assign each PII set a confidentiality impact level of low, moderate, or high, the levels defined in FIPS 199. It lists six factors to weigh: identifiability, quantity of PII, data field sensitivity, context of use, obligation to protect confidentiality, and access to and location of PII.

NIST publishes the factors but no point values. The classifier gives each factor transparent points and shows its working, so you can see why it estimated low, moderate, or high and override it where your organization disagrees.

What Handling Rules Apply to Each Label?

Public

  • No PII handling rules are needed for the data itself.
  • Check that aggregates cannot be re-identified: small cells of fewer than about 10 people can be.

Internal

  • Share inside the organization on a need-to-know basis.
  • Keep out of public repositories, tickets, and AI prompts unless masked.
  • Delete when the business purpose ends.

Confidential

  • Limit access to named roles and review access at least yearly.
  • Encrypt in transit and at rest; no personal email or unmanaged devices.
  • Mask before using in tickets, logs, test data, or AI prompts, for example with the masking tool.
  • Log access and keep a retention schedule.

Restricted

  • Strict need-to-know access with MFA; record every access.
  • Encrypt at rest and in transit; keep off laptops and removable media unless encrypted and approved.
  • Never put in email, chat, tickets, logs, test data, or AI prompts; use masked or tokenized copies.
  • Minimize: collect and keep only what is required, and have a breach response plan ready.

How Do You Classify a Data Set Step by Step?

  1. Scan a sample of the data with the PII scanner to see which elements it actually contains.
  2. Send the findings to the classifier, then add anything a pattern scanner cannot see, such as health details or the purpose of the list.
  3. Choose how many people the set covers and answer the context questions.
  4. Read the tier, the NIST estimate, the suggested label, and the laws that may apply.
  5. Record the final label in your data inventory and apply its handling rules.

When Should You Raise a Label?

Raise the label when the context makes the data more sensitive than its fields suggest. A list of names is usually Confidential, but a list of names of people enrolled in an addiction treatment program, or under internal investigation, deserves Restricted handling. Raise it as well when the volume is large, when the data sits on portable media or internet-facing systems, or when a law such as HIPAA, GLBA, or GDPR attaches specific duties. When in doubt, choose the higher label; the cost of over-protecting is small next to a breach notification.

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

Are Public, Internal, Confidential, and Restricted a legal standard?

No. They are a common organizational convention. Laws and NIST guidance describe what must be protected, and each organization defines its own labels and handling rules.

Does NIST define PII sensitivity 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 scale, shown next to the NIST estimate.

Which label should SSNs get?

Social Security numbers belong in the most protected label, usually Restricted, because their exposure enables identity theft and triggers state breach notification laws.

Can a small data set be high impact?

Yes. Quantity is only one factor. A few records with highly sensitive fields, or a list whose purpose reveals something sensitive, can still warrant a moderate or high impact level.

Is the classifier result final?

No. It is a transparent estimate for education and triage. Your organization sets the final category and impact level.

Was this helpful?