Developing for Privacy
summary
Practical checklist: adopt Privacy by Design (the seven principles), run a privacy impact assessment (PIA) documenting what is collected, legal basis, retention and deletion, and staff training; follow the ICO quick‑check questions; prepare for GDPR plus the incoming ePrivacy rule and CCPA (enforceable July 2020; applies at $25M revenue or 50k+ California household records). Example: WordPress privacy enhancements already ship to ~34% of sites. Focus on data minimization, lifecycle deletion, and auditing third‑party processors.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:40What you will learn today
- 1:06What you will do with what you learn
- 2:58Europe's privacy overhaul
- 4:33Who is subject to GDPR and ePD?
- 7:17GDPR: what is personal data?
- 8:50How is that different from PII? PII = Americanism
- 9:38What might be PII?
- 10:24America is legislating privacy
- 11:19California Consumer Privacy Act (CCPA)
- 21:16What's the result of that?
- 22:12We're going to shift our thinking.
- 22:47What is Privacy by Design?
- 27:34Checking your project on PBD Questions from the UK ICO
- 29:12PBD: Privacy Impact Assessments
- 31:22PIA questions: Personnel, staff, and contributors
- 35:5911 universal privacy principles
- 37:02More design libraries and guides
- 38:29What have you learned today?
related talks
49mPractical privacy: GDPR explained
01h 00mPrivacy and GDPR: What all developers should know
52mDeveloping privacy
40mData Privacy and Security by Design
40mUnderstanding the GDPR and applying privacy principles in your designs
55mBattle for online privacy
33mDesigning and Building With Privacy In Mind
22mDoes Your Privacy Scale?