Data etiquette in a regulated world
summary
GDPR and similar laws force engineering work not just policy changes: companies had to build end-to-end deletion and consent flows that actually purge user records from warehouses, email tools and dozens of downstream systems, and one implementation saw 100× more deletion requests than expected. The practical fixes are consolidation of pipelines, centralized identity, and tooling to push deletes to every destination; evidence favors first-party data only strategies and confirms IDC’s finding of 10 copies of a typical database as the root engineering headache.
AI-written summary · about
chapters (9)
- 0:00Introduction to data regulation
- 1:11Business impact of GDPR
- 3:21First-party data and trust
- 6:32Positive uses of customer data
- 9:19Risks of overregulation
- 11:47Consumer deletion requests surge
- 12:29Technology’s role in compliance
- 15:39Modernizing legacy systems
- 17:47Future of data protection
related talks
50mPrivacy by design
55mTechnical Consequences of the Data Subject's Rights #bbuzz
39mdev.privacy: GDPR in a nutshell
23mdev.privacy: GDPR in a nutshell
22mDoes Your Privacy Scale?
23mThe GDPR impact in database project
48mThe impact of the GDPR
23mTransitioning GDPR from a Compliance Checklist to “Business as Usual”