Understanding the GDPR and applying privacy principles in your designs
summary
Explains that GDPR covers any EU-based business or any service targeting EU individuals, defines personal data as contextual and often pseudonymous, and lists concrete obligations: pick one of six legal bases, keep a record of processing, apply privacy by design and privacy by default, minimize and delete data, and report breaches within 72 hours. Notes transfers to the US are complex after the Privacy Shield invalidation, fines reach 20 million euros or 4% of global turnover, and data portability and DPO rules have specific limits.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:08THE PRIVACY PARADOX
- 3:00WHY PRIVACY MATTERS
- 5:08WHO DOES IT APPLY TO?
- 5:57Personal data is information relating to an identified or identifiable individual.
- 8:23You have to identify of the purpose and legal basis of your processing.
- 11:34You have to apply privacy by design and privacy by default to your designs.
- 14:47You have to delete data you no longer use and you have to delete data on request.
- 16:30You have to be transparent on your data processing.
- 18:17You have to understand where and whom you transfer data to.
- 20:43You have to think about data portability.
related talks
49mPractical privacy: GDPR explained
56mPractical privacy - GDPR explained
46mDeveloping for Privacy
01h 00mPrivacy and GDPR: What all developers should know
26mData Protection Update and Tales from the Introduction of the GDPR
54mGDPR for developers
01h 15mAcademic Session I The GDPR within a continuously reforming digital environment
23mdev.privacy: GDPR in a nutshell