De-identified, Anonymized, or Aggregated? A Look around the Globe
summary
Regulatory definitions leave the same dataset legally protected in one jurisdiction and out of scope in another: Recital 26 ambiguity under GDPR splits courts into absolute (no reidentification risk) and relative (limited legal‑means test) camps; the FTC flags anonymization claims as often deceptive; several U.S. state laws carve out an aggregated consumer information loophole; outdated safe‑harbor health rules persist, while ISO/IEC deidentification framework and NIST drafts push practical, risk‑based assessments and differential privacy as viable tools.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:54GDPR anonymization stance
- 5:20US regulations and deidentified data confusion
- 8:11Aggregated data loophole
- 11:43De-identification approaches
- 13:29Standards and future guidance
- 14:31Resources
related talks
09mPrivacy Analytics and De-Identification
01h 17mTo be or not to be (anonymous)? Anonymyity in the age of big and open data.
10mHealth Data Anonymization and Privacy
01h 13mThe risk-based approach to privacy: How far should we go?
50mData Privacy Concerns - A Risk Based Approach to De-Identification
32mThe Dangerous Data Anonymization - Keynote
29mPersonal Data Pseudonymization Versus Anonymization In The Age Of AI & Big Data
01h 17mSECONDARY USE OF PERSONAL DATA FOR (BIOMEDICAL) RESEARCH