Privacy Design Flaws

on YouTube ↗17m

" summary

Examines concrete architecture mistakes: a contact‑tracing app that continuously sends location+Bluetooth to a government cloud, Netflix’s 500,000 ratings deanonymized by correlating IMDb, Facebook Graph API scope abuse that enabled Cambridge Analytica profiling, and Android logs leaking contact‑tracing data to privileged apps. Explains why encryption or trusted hosts don’t fix design flaws, shows threat‑modeling, logging‑policy and data‑minimization fixes actually used, and argues for enforceable API scopes, data classification, and shared privacy design patterns.

AI-written summary · about

" chapters (8)

1. 0:00Start
2. 1:58Motivation
3. 3:39Two types of risks
4. 6:06Mistaking data protection for privacy
5. 9:20False anonymity
6. 12:23Data leakage
7. 14:41The problem, summarized
8. 16:06Solutions - Principles to abide by

" related talks

• 53mDesigning for Privacy in Mobile and Web AppsAmber Case · ConveyUX 2017
• 38mDeveloping Mobile Apps with Privacy as a Baseline NeedNoble Ackerson · Android Summit 2018
• 04mDeep Dive: Identity, Privacy, and Informed Consent in the...Tim O'Reilly · Gov 2.0 Summit 2010
• 33mTechnosolutionism and human rightsLucie Krahulcova · PyConline AU 2020
• 31mPanel on PrivacyHeather Burns, Trine Falbe · SmashingConf Live 2020
• 01h 02mWeaponizing Technology: Examining the Importance of Privacy...Sapna Khatri · SOUPS 2023
• 47mDesigning for User-Centered PrivacyVenetia Tay · UXSEA Summit 2019
• 41mFundamentally Flawed: Privacy, People and the Age of DataRizqi Djamaluddin · Laracon EU 2018