Analytics with no cookie banner. Here is why that works.
Snorklee sets no cookie to count your visitors. So it adds no banner to your site.
No measurement cookie. So nothing to accept.
The banner exists because most tools write something into the visitor’s browser. Snorklee, by contrast, counts server-side.
That holds for Snorklee only. Ads, social pixels, videos, chat, maps or CRM are still yours to assess.
Five things Snorklee never does.
No measurement cookie, no browser storage, no fingerprint, no advertising ID, no tracking from one site to another. Your audience data is neither sold nor shared.
- No audience-measurement cookie. The only cookie set is « snorklee_sid », a session cookie created after you sign in to your dashboard — strictly necessary, therefore exempt from consent under article 5(3) of the ePrivacy directive (2002/58/EC). The tracker itself sets nothing.
- No identifier that follows you over time. To tell two visits apart within a single day, snorklee builds an anonymous marker each day, never stored as-is; the secret code that produces it is renewed monthly and the IP address is never kept. From one day to the next, no link remains.
- No cross-site tracking, no advertising, no campaign parameters. Campaign parameters — the « UTM » tags some people add to their links — are wiped on arrival, never stored. So no campaign information is read from or written to the visitor's device, nor kept: there is nothing to consent to. (This also reinforces the « audience measurement » scope defined by the European data protection authorities.)
- Unique visitors are counted without a list: no identifier kept, no one can be extracted from it. Unique visitors are estimated with a statistical counter (±1-2 % margin) that keeps no visitor list: it holds an overall numeric summary, not individuals. No one can be pulled back out of it.
- We hide very small numbers. As soon as you cross two pieces of information (e.g. country × page) or a filter is on, we hide any combination that would involve too few people — so it can never point to a person. The rule is the same for everyone, including the signed-in site owner: no special access, no view that could let anyone be recognised.
Every technical choice, and what it avoids.
| Technical choice | Privacy effect | Related documentation |
|---|---|---|
| No measurement cookie | No reading from or writing to the terminal for measurement | ePrivacy art. 5(3) (dir. 2002/58/CE) |
| Non-persistent identifier | Non-reversible daily pseudonym, monthly salt, IP never kept | RGPD art. 4(5) |
| No UTM or campaign tracking | Neutralised at ingestion → nothing read from or written to the terminal, nothing to consent to | ePrivacy art. 5(3) (dir. 2002/58/CE) |
| Counting by estimation (HLL) | No visitor list, aggregate non-individualised data | EDPB Guidelines 2/2023 |
| occurrence floor on every crossing | No re-identifiable cell, owner included | RGPD art. 5(1)(c) |
| GPC / DNT signal honoured | A browser that opts out is never measured | RGPD art. 21 · CCPA / GPC |
| US: documented service-provider role | No sale or sharing of data, no advertising identifier | CCPA / CPRA · DPA art. 28 |
One architecture, two legal rationales.
In Europe — designed not to add analytics-cookie consent
In Europe, ePrivacy rules notably govern access to or storage of information on the visitor's device. Snorklee is designed to measure audience without analytics cookies, localStorage, sessionStorage or fingerprinting. In standard configuration, Snorklee therefore does not add a cookie banner to your site. This conclusion does not cover your other tools: advertising, social pixels, embedded content, A/B testing, chat or CRM must be assessed separately.
In the United States — no sale or advertising sharing by Snorklee
US privacy regimes generally rely less on a prior banner than on information, opt-out rights and controls around certain advertising uses. Snorklee processes audience data on behalf of the customer, without sale, without advertising sharing and without advertising identifiers. Whether a “Do Not Sell or Share” link is needed depends on all tools used on the site, not only Snorklee.
And the features that go further?
Three features go beyond plain counting: your own events, your Google and Bing keywords, and the AI bots that read your pages.
None keeps a lasting identifier and very small numbers are hidden. If you send us personal data inside an event, you step outside the recommended scope.
Snorklee technically limits analytics-side collection. The site publisher remains responsible for its other tools, visitor information, legal bases and any cross-referencing it may perform with its own systems, such as CRM, server logs or a customer database.
The documents to have reviewed.
This page explains how it works. These documents help you review scope, retention, processors and visitor wording against your own context.
- The DPA (data processing agreement) — processor status, GDPR art. 28 clauses, CCPA addendum
- The privacy policy — accounts, support, audience and processors
- GDPR & ePrivacy compliance in detail
- Retention periods — raw events, aggregates and recovery
- Visitor rights (CCPA / CPRA)
- The data protection contact — details and customer assistance
- International compliance (US, Canada, Australia)
Count your visitors with no cookie banner.
200,000 pageviews and 10 sites for €8 a month excluding tax. 14 days free, no credit card.