GDPR – How to be compliant and what that means for your company
summary
Shows concrete compliance work: a new privacy policy that lists which fields and which of ~60 demand partners get user data, contract addenda to push GDPR terms to vendors, and a consent via publishers flow so one banner handles consent for multiple ad partners. Keeps a unified data processing register of every feature that reads or stores identifiers, internal deletion procedures, and notes fines of €10M/2% or €20M/4% of global turnover and the hard deadline of May 25.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:58What is GDPR and why it matters
- 3:22Personal data under GDPR
- 4:09Who must comply globally
- 5:14Controllers vs processors
- 6:18GDPR roles in gaming
- 8:08Penalties for non-compliance
- 8:52GDPR enforcement timeline
- 9:37Steps for GDPR compliance
- 12:48Q&A
- 14:25Compliance likelihood and steps
- 16:03User consent and privacy updates
- 17:20GDPR vs global privacy laws
- 18:44GDPR in unexpected scenarios
related talks
32mGDPR Impact
47mKeynote: Are You Ready for GDPR?
43mGDPR for web development
23mdev.privacy: GDPR in a nutshell
46mGDPR Compliance Tools
44mPanel Discussion – Data Policy and Global Data Privacy Developments
49mPractical privacy: GDPR explained
22mPanel Discussion – 17 months of GDPR experience – Should we review?
