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.
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.
Loading the PII tools.
| Label | 2pii tier | Typical NIST impact | Examples |
|---|---|---|---|
| Public | Tier 0: not identifying | Not applicable (no PII) | Published statistics, press releases, aggregate counts |
| Internal | Tier 1: linkable | Low | Work email directories, IP addresses in logs, ZIP codes alone |
| Confidential | Tier 2: directly identifying | Low to moderate | Customer lists with names, emails, phones, and addresses |
| Restricted | Tier 3: sensitive or high impact | Moderate to high | SSNs, 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.
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.
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.
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.
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.
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.
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.
Social Security numbers belong in the most protected label, usually Restricted, because their exposure enables identity theft and triggers state breach notification laws.
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.
No. It is a transparent estimate for education and triage. Your organization sets the final category and impact level.