Skip to main content

Consentless Analytics FAQ

Because there is nothing to consent to. Sealmetrics is a cookieless tracking system: no cookies, no fingerprinting, no cross-session tracking, no personal data. We measure isolated hits (page views), not user journeys.

ePrivacy requires consent for storing or reading information on a device. Sealmetrics stores nothing on the device, so the consent requirement does not attach. GDPR obligations for personal data do not attach either, because no personal data is collected.

We follow the measurement guidelines published by the AEPD and CNIL. Note that no supervisory authority certifies or approves analytics tools — our compliance pages are self-assessments against the published criteria, not third-party validations.

Do you track users anonymously?​

No.
We do not track users individually, even anonymously.

Every interaction is treated as a standalone hit.
There is no reconstruction of journeys, no profiling, no identification.

What makes Sealmetrics compliant?​

For each hit, Sealmetrics records:

  • Timestamp
  • URL
  • Referral URL
  • User Agent — the raw string is purged after 1 day; only anonymous device categories persist in aggregates

No IP address
No persistent identifiers
No device fingerprinting

With no personal data collected and nothing written to the visitor's device, there is no consent to obtain under ePrivacy and no personal-data processing under GDPR. See the compliance self-assessments for the framework-by-framework analysis.

Why does consentless analytics require aggregated measurement?​

Because ePrivacy requires consent for any technology that tracks users across sessions.
Sealmetrics avoids this by not linking hits, so no cross-session tracking takes place.