Protecting Personal Data with Django (because it's the law)
summary
GDPR becomes enforceable on 25 May 2018 and requires systems to answer data access/rectification/erasure/portability requests within 30 days and report breaches within 72 hours. Django already helps: auth, admin and serialization cover basic access and rectification, but teams must implement per-field encryption or crypto‑shredding for deletion, build data‑portability exports (structured, machine‑readable), proxy external resources to avoid leaking IPs, tag personal fields in models, and plan for automated‑decision and anonymization risks.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:30What is GDPR
- 6:43Overview
- 7:10Legal Terms
- 7:35Personal Data
- 8:20Processing
- 11:15Profiling
- 11:40Transparency
- 13:22rectification
- 13:54erasure
- 16:44by design and default
- 23:30Deleting personal data
- 24:15Preventing discrimination
- 30:02Breach notification
- 32:29Questions
related talks
48mThe impact of the GDPR
49mPractical privacy: GDPR explained
23mdev.privacy: GDPR in a nutshell
56mPractical privacy - GDPR explained
12mEnforcement of Data Protection Laws in Africa: Implications for Privacy Engineers
01h 00mPrivacy and GDPR: What all developers should know
40mHow will the new EU data protection laws affect your work?
23mThe GDPR impact in database project
