Delete the name.
Delete the email address.
Delete the phone number.
The dataset may still describe somebody with uncomfortable precision.
That is the basic gap between removing obvious identifiers and making information genuinely difficult to link back to a person.
Identification can survive without a name field
Imagine a dataset containing:
- age,
- ZIP code,
- workplace area,
- timestamps,
- repeated locations,
- device type,
- and purchase categories.
None of those fields has to say Leo Blanchette or Jane Smith.
But combinations can become distinctive.
A person who repeatedly appears at one residential location overnight and one workplace during weekdays may be easier to identify when another dataset contains addresses, employment records, or public information.
The second dataset supplies the missing label.
This is re-identification by linkage.
NIST treats de-identification as risk reduction, not a magic switch
The National Institute of Standards and Technology’s De-Identification of Personal Information explains that de-identification is intended to reduce privacy risk while preserving useful data, but also notes that researchers have shown some de-identified datasets can sometimes be re-identified.
NIST’s newer SP 800-188 guidance makes the same point operationally. Agencies are advised to evaluate the goals of release, the disclosure risks, the available de-identification methods, and the possibility of re-identification using auxiliary information.
That is a much more careful claim than:
We removed the names, therefore the data is anonymous.
Risk depends on what else exists
The same dataset can have different re-identification risk in different environments.
A record containing only an age range and broad region may be hard to link today.
Add exact timestamps, unusual travel patterns, or a publicly available social-media post describing the same event, and the picture changes.
This makes anonymity contextual.
The attacker—or researcher—does not have to work with the released dataset alone.
They can combine it with public records, commercial databases, breached information, maps, social posts, or another supposedly anonymous dataset.
Pseudonymous is not anonymous either
Replacing a name with an identifier such as user_847219 can be useful.
It stops every casual reader from seeing the person’s identity immediately.
But if a company maintains the lookup table connecting user_847219 to a real account, or if the identifier can be matched elsewhere, the record remains linkable.
That is pseudonymization, not disappearance.
The useful question is measurable risk
Good de-identification asks:
- Which identifying attributes remain?
- How unique are the combinations?
- What outside datasets could be joined?
- Who receives the data?
- What technical and contractual limits exist?
- Has anyone tested re-identification risk?
The Surveillance Economy benefits whenever anonymous is treated as a comforting adjective instead of a technical claim.
Removing the name is valuable.
It is not the same thing as removing the person.