Data policy
How data flows through our system, what we collect, and why you can trust it.
Our tracking script
The Datrika snippet you add to your site sends one small request per event - typically a page view, plus any custom events you choose to track. It doesn't set cookies, and it doesn't write anything to localStorage or sessionStorage. Nothing of ours is left behind on the visitor's device.
It does have to read a few things from the browser, or it would have nothing to measure. It reads four, and coarsens every one of them straight away:
| What the script reads | What we keep from it |
|---|---|
| Browser window dimensions | A bucket only, such as Full HD or HD. The exact numbers are never stored. |
| Browser language | The first part of the code only - cs-CZ becomes cs. It tells us nothing about your specific settings. |
| Page address | The address without link parameters. The exception is five utm_ tags, which we turn into a traffic source. |
| Where the visitor came from | The referrer, meaning the address of the previous page. From it we work out whether it was a search engine, a link, or a social network. |
None of this feeds the visitor hash - that is computed from the truncated IP address, the user agent, and your site ID alone, as described below. The request carries no cookie identifier, no advertising ID, and no cross-site tracking pixel.
Why Datrika doesn't require visitor consent is covered on our GDPR page.
Security and protection
Instead of a cookie, every visitor gets a pseudonymous identifier computed on our servers the moment a request comes in:
| Input | What happens to it |
|---|---|
| IP address | Truncated to its network before hashing - we drop the last octet of an IPv4 address and the second half of an IPv6 one. The full address is used only to look up the visitor's country and city, then discarded, never written to disk. |
| User agent | Used once as hash input, then discarded - never stored separately. |
| Daily salt | A random 16 bytes used as the hash key. Rotates every 24 hours and is never stored alongside the data, so the same visitor can’t be linked across different days. |
| Resulting hash | The only thing we keep - a pseudonymous ID scoped to your site, with no way back to an IP or a person. |
The formula is HMAC-SHA256(Daily salt, Truncated IP + User agent + Site ID) - a keyed one-way hash, computed fresh for every request. We keep its first 64 bits. On top of that:
- All traffic to our collector and dashboard is encrypted in transit over TLS/HTTPS.
- All analytics data is hosted exclusively on servers in Frankfurt, Germany - never outside the EU.
- Only Datrika's operator has access to production databases.
What we collect
Beyond the pseudonymous hash, here's everything we record for each visit:
| Category | Examples |
|---|---|
| Technical | Browser and version, operating system, device type, screen resolution bucket, two-letter browser language code |
| Location | Country, region, and city - as reference IDs, not coordinates |
| Traffic source | Referrer, and UTM tags (source, medium, campaign, content, term) |
| Behavior | Page visited, visit duration, number of page views, whether it was a bounce |
| Custom events | Any events and metadata you choose to send from your own site |
We never collect names, email addresses, or any other directly identifying field as part of standard analytics - the one exception is custom events, where the content is entirely up to you (see our GDPR page for what not to send through them).
Storage and retention
Analytics data is stored for 5 years, the same for every plan, and deleted automatically once that window passes.
What differs by plan is how much of that history you can see. On the Free plan, the dashboard and API only show the last 6 months - older data isn't deleted, it's just hidden until you upgrade. Upgrade at any point and the rest of your history - still within the 5-year window - becomes visible immediately, since it was never actually removed.
Deleting a site or your account is immediate and permanent: the corresponding analytics data is erased right away, with no waiting period and no way to recover it afterwards.
Subprocessors
We keep the list of companies that touch any Datrika data short and deliberate:
| Subprocessor | Role | Location |
|---|---|---|
| Hetzner Online GmbH | Hosts our infrastructure and all analytics data | EU (Germany) |
| MaxMind Inc. | Local GeoIP lookup - the database is downloaded and used on our own servers, visitor data never leaves our infrastructure | Database downloaded from the US; no visitor data sent |
| Resend | Transactional email for account holders (e.g. login codes) - not visitor data | US, covered by Standard Contractual Clauses and EU-US Data Privacy Framework |
| Stripe | Billing for account holders - not visitor data | EU contracting entity; processing may also occur in the US, covered by Standard Contractual Clauses and the Data Privacy Framework |
Only Hetzner and MaxMind ever come into contact with your visitors' analytics data, and both stay inside the EU. Resend and Stripe only handle your own account and billing details. This same list is part of our Data Processing Agreement.
Why you can trust us
- We don't use cookies, and we don't track visitors across sites.
- IP addresses are never stored - not even briefly in logs kept around.
- The daily-rotating salt means visitors can't be linked across days, even by us.
- Your analytics data is yours - we don't sell it, share it, or use it for advertising.
- Everything stays in the EU, hosted on servers we control.
For the legal detail behind all of this, see our GDPR page.