Privacy by Design?
summary
Claims that Article 25 GDPR creates a binding duty to embed data protection early, not a soft recommendation; controllers must adopt state‑of‑the‑art technical and organisational measures, processors must update contracts and instructions, and DPIAs are required for large‑scale high‑risk processing with supervisory authorities able to issue binding opinions. Concrete measures include privacy by default settings, lifecycle encryption and timely deletion, and certification schemes as a demonstrable but non‑delegating proof of compliance.
AI-written summary · about
chapters (9)
- 0:00Privacy by Design intro
- 3:22Seven principles
- 7:10User-centered design & transparency
- 10:24GDPR Article 25
- 15:13Technical & org measures
- 18:37Privacy by default & impact
- 22:18Certification & compliance
- 25:48Future challenges
- 27:18Conclusion
related talks
01h 16mSecurity meets data protection: risk assessment, standards and certification
44mEmbedding GDPR into the SDLC
01h 15mDATA PROTECTION ENGINEERING: WHAT IS THE ROAD AHEAD?
49mPractical privacy: GDPR explained
40mData Privacy and Security by Design
40mUnderstanding the GDPR and applying privacy principles in your designs
02m"3 Questions to"
16mThe Importance of Data Protection Compliance and Cyber Security