Designing and Building With Privacy In Mind
summary
Makes the concrete claim that privacy must be proactive and available by default, shows how cookie walls and deceptive defaults violate GDPR, and demonstrates real consequences: an online retailer exposed data for 2.2 million customers, regulators logged 95,000 complaints, and apps like FaceApp claim broad image rights. Explains tools and countermeasures used: reading policies, Terms of Service; ad‑blocker arms race; browser‑level consent proposals; and cites successful, privacy‑respecting designs such as a live help app that actually works.
AI-written summary · about
chapters (13)
- 0:00GDPR and privacy challenges
- 2:15Disrespectful web interfaces
- 8:34Privacy policies absurdity
- 11:46Ad-blocker war and tracking
- 16:46'Nothing to hide' danger
- 20:18Subconscious manipulation risks
- 21:01GDPR for developers
- 23:50Cookie consent failures
- 25:35GDPR violation consequences
- 26:40Future of privacy controls
- 27:44Licensing designers?
- 28:25Privacy-respecting metrics
- 30:55Privacy necessity
related talks
47mDesigning for User-Centered Privacy
11mThe Future of Privacy
53mDesigning for Privacy in Mobile and Web Apps
46mDeveloping for Privacy
01h 00mPrivacy and GDPR: What all developers should know
37mThe balance between data privacy and user experience
32mTime for a Change – Data Privacy as Competitive Differentiator in Marketing
01h 06mDARK BY DESIGN: REGULATING MANIPULATION IN ONLINE ENVIRONMENTS