Skip to content

Privacy fundamentals

GDPR and website analytics: practical starting questions

A GDPR assessment starts with why data is processed, which data is necessary and how the processing is explained. Technical properties of an analytics tool are inputs to that assessment, not an automatic compliance guarantee.

The European Commission lists lawfulness and transparency, purpose limitation, data minimisation and storage limitation among the principles for processing personal data. In practice, document the measurement purpose first and then each data field needed for that purpose.

Separate request processing from event storage

An analytics request can process network or device data transiently even when every input is not stored in an analytics event. Examine processed inputs, stored fields, retention periods and recipients separately.

Verified technical boundaries in Haimoo Analytics

  • The tracker does not set analytics cookies.
  • A temporary browser-session identifier may be in sessionStorage.
  • The request IP is processed transiently, but a raw IP address is not stored in analytics event records.
  • Visitor estimation uses a daily rotating, site-specific pseudonymous identifier.

Make a website-specific assessment

Other scripts, embeds, forms and business purposes affect the full picture. Describe the tools you use in your own privacy information and seek legal advice when needed. This guide is not a legal opinion.

Sources