GDPR Design for Websites, Apps and (Ro)Bots
summary
Explains concrete compliance steps: which technical and organisational measures reduce risk, why regulators issue fines for request-to-delete failure and sloppy retention settings, how anonymisation often fails and when logs or backups become reidentification hazards, and what APIs/SDKs and consent flows must actually record. Covers enforcement patterns, live-demonstration requests from DPAs, the portability structured machine-readable format debate, and migration choices that force architecture changes or provoke penalties.
AI-written summary · about
chapters (9)
- 0:00GDPR design challenges
- 5:46Privacy engineering beyond compliance
- 10:26GDPR technical impact
- 16:06Your role in compliance
- 21:06Data retention conflicts
- 26:05Privacy by design
- 33:16GDPR beyond cookie banners
- 40:02App development pitfalls
- 43:12Q&A on AI and enforcement
related talks
01h 00mPrivacy and GDPR: What all developers should know
43mGDPR for web development
33mDesigning and Building With Privacy In Mind
40mUnderstanding the GDPR and applying privacy principles in your designs
49mPractical privacy: GDPR explained
46mDeveloping for Privacy
32mGDPR Impact
01h 15mExploring the lands of GDPR, DSA and DMA: Using the consent umbrella when it’s raining with data