De-identification and privacy

What is De-identification?

How it works

NIST, the U.S. standards agency, calls de-identification “a general term for any process of removing the association between a set of identifying data and the data subject”. Its guidance, SP 800-188, written by experts at NIST and the U.S. Census Bureau, was released in September 2023 and updated in February 2025. The goal is to limit disclosure risk to people and organizations while still allowing meaningful statistical analysis.

It is a family of techniques, not one tool. NIST lists removing identifiers, transforming quasi-identifiers and generating synthetic data. A quasi-identifier is a detail such as a birth date or job title that is harmless alone but can point to one person when combined with others. NIST also warns that tools that merely mask personal information may not be enough. The international standard ISO/IEC 20889 classifies these techniques and applies to organizations of every type and size.

You will see both spellings. NIST uses “de-identification” and “deidentification”, and California’s statute uses “deidentified”.

Where the rules differ

Each law sets its own bar for when data stops counting as personal.

This is general information, not legal advice; ask counsel how it applies to you.

The limits

De-identification reduces risk; it does not erase it. FTC staff say hashing does not make data anonymous, because the same input always yields the same hash. A 2019 study found 99.98% of Americans would be correctly re-identified in any dataset using 15 demographic attributes. ISO’s preview notes that de-identification does not always guarantee the desired result, and that its techniques focus on table-like data, so they may not apply to free-form text, images, audio or video.

Why it matters when selling data

Business data such as messages, documents and tickets is largely free-form text. ISO notes its table-focused techniques may not apply to that kind of data, so names and identifiers buried in sentences need careful handling, alongside a rights review of contracts and policies.

SellMyData, for example, explains what it removes and replaces with consistent placeholders, and the limits of that process, on its de-identification page. Buyers see only a redacted sample before purchase, a licensed lab receives the de-identified dataset rather than raw data, and company exports are deleted within 30 days of the de-identified dataset being approved. Placeholders keep a conversation readable; whether a given dataset meets a particular legal test is a question for counsel.

Before licensing any dataset, ask which legal standard the buyer expects and what re-identification risk remains.

Frequently asked questions

What is de-identified data?

It is data that has been processed to remove the association between identifying information and the person it is about. Under California's CCPA, deidentified information falls outside the definition of personal information if the business meets the law's conditions. This is general information, not legal advice; ask counsel how it applies to you.

Is de-identification the same as anonymization?

Not always. EU regulators (the EDPB) say pseudonymised data that can be linked back to a person with extra information, such as a key or lookup table, is still personal data. Separately, FTC staff in the U.S. have said data is only anonymous when it can never be associated back to a person; this is general information, so ask counsel how it applies to you.

Does hashing de-identify data?

Not by itself. FTC staff have said hashing does not make data anonymous, because the same input always produces the same hash.

Can de-identified data be re-identified?

Sometimes. A 2019 study in Nature Communications found that 99.98% of Americans would be correctly re-identified in any dataset using 15 demographic attributes, and said this challenges the 'release-and-forget' model (publishing de-identified data and assuming it stays safe forever). Standards such as ISO/IEC 20889 describe de-identification as reducing re-identification risk, not guaranteeing it.

Sources

  1. NIST SP 800-188: De-Identifying Government Datasets: Techniques and Governance, National Institute of Standards and Technology
  2. NIST SP 800-188 release information, National Institute of Standards and Technology
  3. NIST SP 800-188, U.S. Census Bureau
  4. ISO/IEC 20889:2018 Privacy enhancing data de-identification terminology and classification of techniques, ISO
  5. ISO/IEC 20889:2018 preview, ISO/IEC
  6. Guidance Regarding Methods for De-identification of Protected Health Information, U.S. Department of Health and Human Services
  7. HIPAA Privacy Rule guidance, U.S. Department of Health and Human Services
  8. California Civil Code §1798.140, California Legislative Information
  9. Guidelines 01/2025 on pseudonymisation (summary), European Data Protection Board
  10. EDPB adopts pseudonymisation guidelines, European Data Protection Board
  11. No, hashing still doesn't make your data anonymous, Federal Trade Commission
  12. Estimating the success of re-identifications in incomplete datasets using generative models, Nature Communications (via PubMed Central)

Find out what your data is worth.

Book a callValue my data