Analytics that respects your visitors
Analyse is cookieless, stores no IP addresses, and collects no personal data unless you ask it to. Your visitors get a fast page, and you get numbers you can trust without a consent banner.
No cookies, no cross-site trackers, nothing stored that needs a consent banner for the analytics itself.
We read the IP once on our server to resolve an approximate city, then drop it. It never lands in your reports.
Your analytics live on our own servers in Germany, not on someone else's ad platform.
You are the data controller, we are your processor, and a signed Data Processing Addendum is included.
Visitors get a random first-party id, not a device fingerprint stitched across the web.
A few kilobytes, loaded without blocking your page, served from your own domain.
What we collect, and what we never do
Every event is anonymous by default. Here is the full list, so there are no surprises for you or your visitors.
- The page URL, path, and referrer
- A random anonymous id and session id, kept in the browser's local storage
- Browser, operating system, device type, and screen size
- UTM campaign parameters when they are present in the link
- Country, region, and approximate city, resolved server-side from the IP
- Any custom events and properties you choose to send
- No cookies, first party or third party
- No IP addresses saved to your reports
- No device or browser fingerprints
- No names, emails, or other personal data unless you explicitly identify a user
- No cross-site or advertising identifiers
- No selling or sharing of any of it, ever
Compliance built into the product
Privacy is not a setting you turn on later. It is how the tracker works out of the box, backed by the paperwork your legal team will ask for.
- You are the data controller and Analyse is your processor under Article 28 of the GDPR
- A Data Processing Addendum is signed and available before you send a single event
- Because analytics is anonymous by default, there is no personal data to sell under the CCPA and nothing to opt out of
- The WordPress plugin honors Do Not Track and Global Privacy Control signals, and the SDK lets you gate tracking on them yourself
- You control retention and can delete a visitor's identified profile at any time
- Standard Contractual Clauses cover the few sub-processors outside the EEA
Our analytics databases are self-hosted on our own infrastructure in Germany. These sub-processors support the service, each under a data processing agreement.
| Hetzner | Hosting and databases | Germany |
|---|---|---|
| Google Cloud | Supporting infrastructure | EU, SCCs |
| Stripe | Billing | EU / US, SCCs |
| Resend | Transactional email | US, SCCs |
No speed nightmares
Heavy analytics tags are why so many sites feel slow. The Analyse tracker is tiny, loads without blocking your page, and makes no third-party requests in the critical path.
Questions buyers ask
Do I need a cookie consent banner?
For the analytics itself, usually not. Analyse sets no cookies and stores no personal data by default, so there is nothing to consent to. Your own obligations still depend on your region and anything else your site does, so check with your counsel.
Do you store visitor IP addresses?
No. We read the IP once on our server to work out an approximate city, then discard it. It is never written to your reports or kept in the event.
How is this different from Google Analytics?
Google Analytics is built to feed an advertising business and ships a heavy tag. Analyse collects anonymous data only, stores it in the EU on our own servers, and never sells or shares it.
Where is my data hosted?
On our own servers in Germany. A short list of sub-processors supports billing and email, each under a data processing agreement, with Standard Contractual Clauses for anything outside the EEA.
Can visitors opt out?
Yes. The WordPress plugin honors Do Not Track and Global Privacy Control and can skip logged-in users. On a custom install you can check those signals before starting the tracker, and reset() clears a device's history on demand.
What counts as personal data here?
Nothing, until you call identify() with a user id and traits of your choosing. That call is opt in and entirely under your control, so you decide what your privacy policy needs to cover.
Analytics you can defend
Give your visitors a private, fast experience and give yourself numbers you can trust. Start free, no cookie banner required.