In 2019, the French Data Protection Authority (CNIL) fined Google €50 million for violating GDPR. The ruling, known as Google v. CNIL (2019), proved that GDPR is not simply an abstract text – all companies, including corporations and market monopolists, must obey its provisions.

Decisions of high courts, such as this one, also prove useful in enforcing data privacy. Even if the decisions are made in a particular case between two entities or individuals, these rulings often explain legal provisions and are used as an additional set of legal principles. Historically, court decisions have had more impact in the US, which follows the case law system.

You may also like:

Data privacy laws in the United States and how they affect your business

11 new privacy laws around the world and how they’ll affect your analytics

Facebook Inc. v. Duguid

EU-US data privacy framework


  • Privacy by design in practice: How “just enough” data beats “just in case” collection

    While collecting more data “just in case” feels safer, according to Matt Gershoff, it’s also one of the biggest sources of unnecessary compliance risk, analytical noise, and wasted organizational resources in the analytics industry today. His approach of “just enough” data collection is more intentional, more aligned with privacy regulation, and often more analytically effective.

  • 4 ways to make your analytics HIPAA-compliant: Implementation guide

    Healthcare organizations have four main approaches to achieving HIPAA-compliant analytics. Each has different trade-offs in cost, technical complexity, and analytics capabilities. This guide compares all four implementation methods – from using Google Analytics with workarounds to deploying fully HIPAA-compliant analytics platforms – so you can choose the right approach for your organization’s needs and resources.