Privacy model
Supersaas Analytics counts Visitors without cookies and without remembering anyone from one day to the next. This page explains how, so you can describe it accurately in your own privacy policy.
Nothing is stored in the browser
The snippet sets no cookies and uses no localStorage, sessionStorage or IndexedDB. It reads nothing from the
browser that could fingerprint it, such as the screen size, fonts or canvas. Each hit carries only what the
Installation page lists.
A Visitor id that lasts one day
On our side, each hit is assigned a Visitor id:
visitor id = SHA-256(daily salt + Site id + IP address + User-Agent)
- The daily salt is a random value created each UTC day. It is deleted once the day is over, and never leaves our servers. Without it, nobody, us included, can recompute yesterday's ids from an IP address and User-Agent.
- The Site id makes the same person a different Visitor on each Site, so Sites cannot be linked.
- The IP address and User-Agent are used only to compute the hash. Neither is stored.
So the same person is one Visitor for one day on one Site, and a new Visitor the next day. The cost is that
"returning visitors" across days cannot be counted, and a Visitor's journey covers one day only, unless your Site
links days with identify().
What is stored
For each Visit, we store the pages viewed with their titles and times, the referrer's domain and campaign parameters, the Events and Outbound links, and:
- location: country, region and city, looked up from the IP address when the hit arrives, plus approximate coordinates for the Live globe. The IP address itself is dropped.
- device: browser, operating system and device type, parsed from the User-Agent. The User-Agent itself is dropped.
Paths are stored without their query string or #hash, apart from the five utm_ parameters, because those can hold
emails, tokens and other personal data.
No consent banner
The snippet stores nothing on the visitor's device, so the ePrivacy rule on cookies and similar technologies, which is
what consent banners ask about, does not come into play. The data we keep cannot single out a person across days. We
believe this lets most websites use Supersaas Analytics without a consent banner, but your own lawyer has the final word
for your website, especially if you use identify().
Where the data lives
Supersaas Analytics runs on Cloudflare, with the data in Cloudflare D1. We are the processor of your Sites' analytics data and you are its controller; see our Privacy Policy. Raw rows are kept for 3 years, so every report, Filter and Funnel works over that span without sampling. Deleting a Site deletes its data.
With a Self-hosted License, everything runs on your own Cloudflare account, and no data reaches us.