Privacy data encryption & deletion while preserving analytical integrity
summary
Claims a practical crypto shredding pipeline that encrypts PII at ingestion with AES GCM, stores per-customer keys in a separate keystore, and implements a one-step forget function that deletes keys so data becomes unreadable while keeping row counts and aggregations intact. Provides an open-source Python library GDPR Officer that demos per-customer keys, random nonces to avoid pattern leaks, and encryption-before-warehouse or raw-truncate architectures. Recommends envelope keys, master-key rotation, retention timers, and gated audited access; demo shows it works end-to-end.
AI-written summary · about
chapters (8)
- 0:00Data privacy and encryption
- 3:47Traditional deletion problems
- 8:51Crypto shredding basics
- 15:41Live demo: encryption workflow
- 21:24Encryption architectures
- 22:51Key governance best practices
- 24:16Compliance in AI attacks
- 26:10Q&A
related talks
20mWhy data privacy is critical for robust data management?
40mEat Your Vegetables Data Security for Data Scientists
37mOf Data Dropboxes and Data Gloveboxes
32mYou've got trust issues, we've got solutions: Differential Privacy
36mArchitecting Data: A Deep Dive Into the world of Synthetic Data
45mHow Decentralized Data Products are Changing GEMA from Inside Out
33mKeynote: Federated Analytics at Scale
17mOpen Source for Data Quality