Getting your privacy notices ready for GDPR
summary
GDPR requires privacy notices to state who you are, every category of personal data collected, the legal basis for each item, retention schedules and named third parties (example: PayPal lists ~600), user rights and a contact address, DPIAs where done, breach procedures and international transfer safeguards. Notices must be layered with just-in-time explanations and offer granular opt-ins (telemetry must be off by default). WordPress is adding a default Privacy page, plugin metadata for data flows, and guidance so sites can generate editable, accurate notices.
AI-written summary · about
chapters (14)
- 0:00Intro
- 2:15What is changing and why
- 5:48Who needs a privacy notice
- 7:11Where can I get a template
- 9:23How do you approach it
- 10:25Essential facts
- 15:24Additional information
- 19:06Language
- 22:34UX Design
- 26:14What happens if I dont include a GDPR compliant privacy notice
- 28:08How to make privacy notices happen in the WordPress ecosystem
- 32:15What to think about if you develop plugins
- 34:01Practical advice
- 36:26Where to learn more
