The GDPR (General Data Protection Regulation) entered into force on May 25, 2018. It is Europe’s digital privacy regulation. It states that companies have to obtain the consent of Data subject s to store and process users’ personal data.

The European Commission prepared the GDPR, which replaced the outdated 1995 European Data Protection Directive. The idea behind GDPR is to provide individuals with full control over their personal data. It aims to strengthen and unify the rules of data collection from individuals within the European Union.

In the GDPR era, Personal data is not only name, photo, address, phone number or email address. It also includes the following data:

  • Biometric and genetic data
  • Economic status
  • Cultural and social identity
  • IP address and geolocation
  • Device ID
  • Cookies
  • Pseudonymous data

Read more about Data controller s, Data processor s or Data processing agreement s.

Visit the Piwik PRO blog to dive deeper into GDPR-related articles.


  • 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.