GDPR for web development
summary
Overview of concrete GDPR tradeoffs and fixes for web teams: require TLS/HTTP2 everywhere, use static analysis and dependency scanning, track per-use consent and retention periods, and treat backups and DR replicas as regulated copies. One publisher runs weekly user research Jan–May to iterate consent UI and ends up refusing Google over liability; targeted ads account for >50% revenue there. Expect messy controller/processor splits across dealerships and data centers and note only ~20% of firms report feeling compliant.
AI-written summary · about
chapters (10)
- 0:00Introduction to GDPR talk
- 2:10What is GDPR
- 10:21GDPR in web development
- 13:14Security and data handling
- 18:34Designing compliant applications
- 21:29Symfony’s GDPR implementation
- 24:49Case study: Automotive manufacturer
- 32:49Case study: Schibsted Media Group
- 39:27Post-GDPR enforcement and compliance
- 40:29Q&A session
related talks
21mGDPR – How to be compliant and what that means for your company
32mGDPR Impact
48mGDPR Design for Websites, Apps and (Ro)Bots
01h 00mPrivacy and GDPR: What all developers should know
43mE-Privacy & GDPR
01h 02mThe GDPR and New Technologies: Enough, or do we need more?
23mdev.privacy: GDPR in a nutshell
22mPanel Discussion – 17 months of GDPR experience – Should we review?
