Founder pricing — only 4 of 50 seats left at $49/yrthen $149Claim yours

Analytics Definitions

What is GDPR Compliance in Web Analytics?

Meeting the privacy and consent requirements of the General Data Protection Regulation when tracking website usage.

The General Data Protection Regulation (GDPR) regulates how organizations collect and process the personal data of individuals inside the European Union. Under GDPR and the ePrivacy Directive, any service that writes cookies to a device or processes personal identifiers (such as static IP addresses) requires explicit user consent.

Many analytics tools default to writing tracking cookies and streaming visitor data into global ad-targeting networks. This makes displaying a cookie consent banner legally mandatory for any EU traffic.

TrackWhy is engineered to be GDPR-compliant by default. We do not set cookies, never write to local storage, truncate and hash visitor IP addresses instantly, and process zero personal identifiers. All analytics data is stored securely in compliance with EU regulations, meaning you do not need to display a cookie consent banner for TrackWhy.

Start tracking analytics14-day free trial. No card required.

FAQ

Frequently Asked Questions

Do I need a DPA to use TrackWhy?
Yes. Under GDPR, you should execute a Data Processing Addendum (DPA) with your analytics processor. TrackWhy provides a standard, pre-signed DPA that you can review and bind to your account instantly.
Does TrackWhy track users across different sites?
No. TrackWhy does not set cross-site IDs or track user identities across different domains. All analytics metrics are strictly isolated to your individual site domain.

Related definitions