Data collected

snorklee collects the minimum needed to produce useful statistics. The goal is to measure a site, not identify a person.

#Sent by the browser

The tracker may send: site identifier, page path, referrer hostname, scroll depth, duration, event type, event name, limited properties and outbound hostname.

UTM / campaign parameters (utm_source, utm_medium, utm_campaign, etc.) are not collected: they are stripped on receipt and never stored.

It does not send form field contents.

#Used server-side

The server may use IP, User-Agent and HTTP language transiently to geolocate, detect browser/device, limit abuse, link a visit for a short time and verify AI bot identity (the IP is checked against the ranges published by the bot's vendor). Raw IP and raw User-Agent are not stored in analytics events.

#Stored in statistics

Events store data such as timestamp, page path, referrer/outbound hostnames, source, country and region (deduced from IP, never the city), browser family, OS, device, language, event type, duration, scroll, bounce and cleaned properties.

Bot hits additionally carry the bot family, its observed purpose, its user-agent token and the identity verdict. These are not visitor data: a bot is not a person.

#Never send

Never put emails, phone numbers, names, addresses, customer numbers, CRM identifiers, advertising click IDs, IBANs, card numbers, health data or secrets in events, properties or URLs.