Skip to content
Module
Module 4 of 6Lesson 2 of 2~17 min

Collect by the rules, consent, CNIL and minimization

Choosing an analytics tool and writing a tracking plan both bear on your product's GDPR compliance. This lesson helps a PM know when consent is required, in which narrow cases the CNIL allows audience measurement without it, and which data to leave out or delete in time. You reach your DPO with a file ready for discussion.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to say, for each tool and each event in a tracking plan, whether it needs the user's consent or may fall under the audience measurement exemption, remove unnecessary personal data and set a retention period, before validating everything with your DPO.

Questions this lesson answers

  • When does a product analytics event require user consent?
  • What is the audience measurement exemption under French CNIL rules?
  • How do you minimize personal data inside a tracking plan?

Topics covered

  • consent
  • GDPR and analytics
  • audience measurement exemption
  • CNIL
  • data minimization
  • data retention

Where it fits

Reliable, compliant data

How do I know my numbers are right, and that I collect them by the rules?

Lessons in this module

  1. QA and monitor data collection
  2. Collect by the rules, consent, CNIL and minimization (this lesson)

What you will learn in this module

This lesson is part of the course Instrument a product and use data to make decisions

  • QA and monitor event collection to get reliable data, and know what to do when it is not.
  • Collect usage data in line with the GDPR and the CNIL rules (consent, audience measurement exemption, minimization, retention period).

Related courses