Filling the gap between DPOs and developers
summary
Developers must detect privacy issues early and a practical pattern emerges: assign one privacy-aware developer per team, involve DPOs at the project start to give high‑level constraints, then let devs iterate; use wireframes to discuss UI behavior (checkboxes, delete flows) and build lightweight tooling like a data‑lifecycle sensor to trace records. Treat privacy as technical debt to budget for, focus first on retention, security and access rights, and keep the DPO as independent advisor while leadership accepts calculated risk.
AI-written summary · about
chapters (9)
- 0:00Privacy gap between DPOs and devs
- 3:43Developers and GDPR
- 10:30Building privacy culture
- 14:51Bridging communication gap
- 21:15Privacy training for devs
- 27:58Privacy vs business goals
- 36:08DPOs in tech companies
- 43:42Privacy principles for devs
- 49:18Future of privacy roles
related talks
42mPrivacy as a Brand Differentiator
28mBuild Privacy into Your Products and Gain User Trust
21mHow Software is Developed for Privacy Professionals
10mEvaluating Privacy Perceptions, Experience, and Behavior of Software Development Teams
40mLessons Drawn From Cybersecurity In The Rise of Privacy Tech
15mTurning Privacy Risk Assessment Into 20 Questions for Developers
12mA People-First Approach to Introducing Process and Tools for Technical Privacy Review
40mExtreme Makeover: Privacy Edition