Data Policy
What MetriXs collects about your website visitors, and how it stays anonymous.
Why this is a separate page
When you place the MetriXs script on your website, MetriXs processes data about your visitors on your behalf. Under the GDPR, you remain the data controller for that visitor data and MetriXs acts as your data processor. This page documents exactly what that processing involves, so you, and your auditors, can verify the claims.
For the data MetriXs collects from you as a customer (your account, billing, and support communication), see our Privacy Policy.
What we collect
MetriXs measures only the essentials needed for aggregate analytics. Nothing is collected that can identify an individual:
Page URL
Hostname and path. Query parameters discarded except utm_* (saved to dedicated columns).
Referrer
Where the visitor came from. Cleaned to a bare hostname; self-referrals ignored.
Browser & OS
Parsed from the User-Agent. The full User-Agent string is never stored.
Country & city
Derived from IP via a local MaxMind database. The raw IP is never stored.
Visitor identifier
A pseudonymous daily hash (see below). Not a persistent identifier.
Engagement
Scroll depth and time on page. Aggregate metrics only, no profiling.
What we do NOT collect
How we count visitors without cookies
To show useful metrics like unique visitors and sessions, MetriXs needs a way to recognise a returning visitor within a short window, without placing anything on their device. It does this with a daily-salted hash:
Visitor request
(IP + UA in memory)
Daily hash
(salt rotates 24h)
Aggregate only
(IP & UA discarded)
The properties that make this safe:
- The salt rotates every 24 hours. The previous day’s salt is kept briefly (a ~49-hour TTL) for cross-midnight session continuity, then expires. A visitor returning tomorrow receives a different identifier, so the same person cannot be tracked across days.
- The raw inputs are never stored. The IP address and User-Agent are used in memory to compute the hash and then discarded. The hash cannot be reversed to recover the original IP.
- Data is isolated to a single day, a single website, and a single device. There is no way to know whether the same person visits from multiple devices or visits another website.
- The identifier is 16 bytes (32 hex characters) and is never used as a persistent or cross-site identifier.
The result is that MetriXs can report accurate daily unique-visitor and session counts while remaining unable to identify or track individual people, which is the whole point.
No consent banner required
No cookie banner needed
Because MetriXs places no cookies or trackers on the visitor’s device and stores no personal data, the consent requirements of the ePrivacy Directive (Article 5(3)) are not triggered. You can run MetriXs without a cookie consent banner.
Bot and abuse filtering
Bots, scrapers, and floods
Incoming events are filtered for known bots and abuse patterns. Rate limiting caps flood traffic. For logging, only a truncated IP is ever written to a log line, the full IP is never persisted to disk.
Data retention
Visitor analytics data is retained according to your plan and automatically deleted when it falls outside the retention window:
Free
1 month retention
Basic & Team
12 months retention
Pro
24 months retention
A daily automated job purges data past each team’s retention window, including for cancelled subscriptions, so data is never retained longer than promised. When you delete your account, all of your analytics data is permanently deleted without undue delay.
Data residency
EU-only, no US providers in the path
All visitor analytics data is processed and stored on infrastructure hosted by Hetzner Online in Germany. Visitor data never leaves the European Union. No content delivery network or US provider sits in the path of visitor traffic.
Your visitors’ rights
Because MetriXs does not store personal data about your visitors, the standard data subject rights (access, correction, deletion, portability) do not apply to visitor analytics, there is no personal data to access or delete. Should a visitor nonetheless contact you with a request, you can forward it to privacy@metrixs.eu.
Last updated: July 2026