Skip to main content
    Back to Blog
    12 min readLast reviewed:
    PII
    PHI
    CCPA
    GDPR
    Glossary
    AI Compliance

    PII vs PHI vs Personal Data (PI): Definitions and Which Law Applies

    T

    Team Sonomos · Sonomos

    The Sonomos research team writes about AI privacy, data protection, and how to use generative AI safely at work.

    PII (personally identifiable information) is information that can distinguish or trace a person's identity, on its own or linked with other data. PHI (protected health information) is identifiable health information held by a HIPAA covered entity or its business associate. PI (personal information) is California's broader CCPA term, and personal data is the GDPR's.

    Every item of PHI is also PII in the ordinary sense, because it identifies someone, but most PII is not PHI. PI and personal data reach further than PII: both cover anything that relates to an identifiable person, including inferences drawn about them, and the CCPA also covers households. Which term applies depends less on the data than on who holds it and whose data it is. A diagnosis in a hospital's records is PHI. The same diagnosis typed into a consumer fitness app is generally not, though it is still personal data under the GDPR and sensitive personal information under the CCPA.

    PII vs PHI vs PI vs personal data at a glance

    PIIPHIPI (personal information)Personal data
    SourceNIST SP 800-122, adopting the federal OMB definitionHIPAA, 45 CFR 160.103CCPA, Cal. Civ. Code 1798.140(v)GDPR Article 4(1)
    Core definitionInformation that can "distinguish or trace an individual's identity" or is "linked or linkable" to one"Individually identifiable health information" in any form or mediumInformation that identifies, relates to or "could reasonably be linked" with a consumer or household"Any information relating to an identified or identifiable natural person"
    Who it bindsFederal agencies; elsewhere, whoever a contract or policy saysHIPAA covered entities and business associatesBusinesses subject to the CCPAControllers and processors within the GDPR's scope
    Health dataPII when linked or linkableIts defining featureSensitive PI when "collected and analyzed concerning a consumer's health""Data concerning health", a special category under Article 9
    Main exclusionsData that cannot be linked to a personFERPA education records, an employer's employment records, people dead more than 50 years, de-identified dataPublicly available, deidentified or aggregate informationAnonymous information
    Covers householdsNoNoYesNo

    PII: the security and contracting term

    The definition most US organisations use comes from NIST SP 800-122, published in April 2010, which adopts the federal government's wording: PII is "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."

    NIST explains the two verbs. To distinguish someone is to identify them: a name, passport number or fingerprint. To trace someone is to work out something about their activities or status, as an audit log of user actions can. A list of credit scores with nothing else attached, NIST notes, distinguishes nobody. "Linkable" is what makes PII wide: a date of birth and a postcode are harmless alone and identifying together.

    Outside federal agencies, PII is mostly a contracting and security word. No single US statute regulates "PII" in general. FERPA defines personally identifiable information for student records, the Gramm-Leach-Bliley Act uses nonpublic personal information for financial customers, and state laws mostly say "personal information". When a vendor contract or security policy uses "PII", read its own definition, because that is the one you will be held to.

    PHI: identifiable health information under HIPAA

    HIPAA builds PHI in two steps in 45 CFR 160.103. Individually identifiable health information is health information, "including demographic information", that is created or received by a health care provider, health plan, employer or health care clearinghouse; that relates to a person's past, present or future physical or mental health, to the provision of care, or to payment for care; and that identifies the person or gives "a reasonable basis to believe" it could. Protected health information is that information when "transmitted or maintained in any form or medium", minus four exclusions: education records covered by FERPA, certain student treatment records, "employment records held by a covered entity in its role as employer", and information about a person dead for more than 50 years.

    The rules attach to the holder. Under 45 CFR 160.102, HIPAA's standards apply to health plans, health care clearinghouses, providers who transmit health information electronically in standard transactions, and, where stated, their business associates. So a hospital's appointment list is PHI, an employee's sick note in the same hospital's HR file is not, and a step count in a consumer app is generally not, unless the app is acting for a covered entity.

    PHI stops being PHI when it is de-identified under 45 CFR 164.514, either by an expert's determination using "generally accepted statistical and scientific principles" or by removing 18 listed identifiers of the person and their relatives, employers and household members, with no "actual knowledge" that what remains could identify anyone.

    PI and personal data: the broad definitions

    The California Consumer Privacy Act, in the consolidated text effective 1 January 2026 published by the California Privacy Protection Agency, defines personal information in section 1798.140(v) as "information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular consumer or household". Its list runs from names and IP addresses to geolocation, browsing history and "inferences drawn" to build a profile. The current text also says PI can exist in "artificial intelligence systems that are capable of outputting personal information". Publicly available, deidentified and aggregate information are excluded.

    Within PI, "sensitive personal information" in section 1798.140(ae) covers government ID numbers, account log-ins with passwords, precise geolocation, racial or ethnic origin, citizenship or immigration status, religious or philosophical beliefs, union membership, the contents of mail, email and texts, genetic data, neural data, biometric identification, and information about health, sex life or sexual orientation. Consumers can limit how a business uses it.

    The GDPR's Article 4(1) is shorter and wider: "'personal data' means any information relating to an identified or identifiable natural person", identifiable "directly or indirectly", including by "an online identifier". Article 9 adds special categories, including health data, that need an extra legal condition before they can be processed.

    Pseudonymised data is where the GDPR is most often misread. Recital 26 says data that "could be attributed to a natural person by the use of additional information" is still personal data. In September 2025 the Court of Justice added a qualification in EDPS v SRB, decided under Regulation 2018/1725, the EU institutions' counterpart to the GDPR: pseudonymised data must not be regarded as personal data "in all cases and for every person", because a recipient without the key may be unable to identify anyone. For its duty to inform people, though, the controller must judge identifiability at the time of collection and from its own point of view.

    Examples: one fact, four labels

    DataPIIPHIPI (CCPA)Personal data (GDPR)
    Patient name with a diagnosis in a hospital's recordsYesYesPHI collected by a covered entity or business associate is exempt from the CCPA (section 1798.146)Yes, and health data under Article 9
    Heart-rate history in a consumer fitness appYesGenerally noYes, sensitive PIYes, health data
    A named person's email addressYesOnly inside a covered entity's health recordsYes, a listed identifierYes
    A dynamic IP addressLinkableOnly inside health recordsYes, a listed identifierCan be, as the Court of Justice held in Breyer
    Flu cases counted by countyNoNoNo, aggregateNo, if truly anonymous

    Which law applies: a short decision list

    Work through these questions in order. Most datasets trigger more than one.

    1. Is it health information that identifies someone, held by a HIPAA covered entity or a business associate working for one? Then it is PHI. The HIPAA Privacy and Security Rules apply, and sending it to an AI vendor requires a business associate agreement first.
    2. Is the processor or controller established in the EU, or is it offering goods or services to, or monitoring, people in the EU? Then Article 3 brings the data under the GDPR as personal data, which needs a lawful basis, and health data needs an Article 9 condition as well.
    3. Does it relate to a California resident or household, held by a business the CCPA covers? Then it is PI under the CCPA, with extra rights over sensitive PI. PHI held by a covered entity is carved out.
    4. Is it financial customer data at a US financial institution, or a student's education record? Then GLBA's nonpublic personal information or FERPA's definitions apply.
    5. Does a contract, a security policy or a federal system use the word PII? Then apply that document's definition, usually modelled on NIST SP 800-122.

    Where several apply, meet the strictest rule for each obligation rather than picking one regime.

    What the labels mean when data goes into an AI tool

    The labels decide which contract you need before anything is pasted into a chatbot. PHI needs a business associate agreement; our guide to whether ChatGPT is HIPAA compliant shows what that looks like in practice. Personal data under the GDPR needs a data processing agreement and a lawful transfer mechanism, as the GDPR and AI guide explains. PI under the CCPA calls for a written service provider contract. PII in a contract means whatever the contract says.

    All of them become easier to handle when the identifying parts never leave. De-identification and pseudonymisation at the point of use reduce what reaches the vendor, and What Is PII Redaction? covers how that is done in prompts.

    Sources and primary references

    Reviewed 18 November 2026. Statutes and regulations are cited to official or standard legal sources.

    Frequently asked questions

    Is all health information PHI?

    No. Health information is PHI only when it identifies a person and is held by a HIPAA covered entity or a business associate acting for one. The same information held by a consumer app, an employer's HR file or a search engine is not PHI, though it can still be sensitive personal information under the CCPA or health data under the GDPR.

    Is an email address PII?

    Yes. It usually identifies one person, so it is PII, personal information under the CCPA's list of identifiers, and personal data under the GDPR. It becomes PHI only when it sits in a covered entity's health records, where email addresses are one of the 18 identifiers HIPAA's safe harbor method removes.

    Is an IP address personal data?

    It can be. In Breyer (Case C-582/14, 19 October 2016), the Court of Justice held that a dynamic IP address is personal data for a website operator that has the legal means to identify the visitor using information held by the internet access provider. The CCPA lists IP addresses among its identifiers outright.

    Is pseudonymized data still personal data under GDPR?

    For the controller that holds the key, yes: Recital 26 treats data that can be re-attributed with additional information as personal data. After the Court of Justice's 2025 judgment in EDPS v SRB, a recipient that cannot reverse the pseudonymisation may hold data that is not personal data from its own point of view, but the controller's duties are judged from the controller's side.

    What's the difference between SPI and Special Category Data?

    SPI (sensitive personal information) is the CCPA's list in section 1798.140(ae), including government ID numbers, account log-ins, precise geolocation and neural data. Special category data is the GDPR's Article 9 list. The lists overlap on race, religion, health, sex life and biometrics, but the consequences differ: the CCPA gives a right to limit use, while the GDPR requires an Article 9 condition before processing.

    The bottom line

    PII is the security and contracting term, PHI is HIPAA's term for health data held by health care organisations, and PI and personal data are the broad legal definitions of California and the EU. The useful question is not which label is correct but which rules a dataset triggers, and the answer is often several at once. Get the classification right before data goes into an AI tool, because the contract you need follows from it.

    The simplest way to keep every label out of the prompt is to remove the identifying parts before it is sent. That is the job Locke does: it runs on your device, detects names, account numbers and other sensitive values in the AI tools it screens, and swaps them for placeholders before the prompt leaves, and the unmasked content is never sent to Sonomos. Download Locke and try it on the next prompt that contains a name.

    Sonomos publishes this blog and makes Locke, which detects and masks sensitive information on your device before it reaches an AI model. How Locke works

    This article is general information about privacy and AI, not legal advice, and reading it does not create a solicitor–client or attorney–client relationship. Regulatory requirements turn on your specific facts and jurisdiction and change over time. Consult qualified counsel before relying on anything here, and check the publication and last-reviewed dates above. We may revise posts, but we do not undertake to keep any post current as the law changes.

    Reference pages for this post