GDPR and cookieless tracking
Datasense tracks with first-party cookies or with none at all. What each mode stores, how visitors are counted, and what it means for consent.
Each website picks how visitors are recognized in Settings → Tracking. Each mode has its own script, so the tag on your site says what it does.
Cookie mode (default)
Script: /js/script.cookies.js
datasense_vid: a random visitor ID for up to 400 days, on the widest domain the page may set, sowww.,app.and the apex share it. Mirrored to localStorage.datasense_sid: a session ID that slides 30 minutes, shared across tabs.- The most accurate counts: a visitor who comes back next week is still the same visitor.
- In the EU and UK, analytics cookies need consent. List both in your banner as analytics cookies.
Cookieless mode
Script: /js/script.js
- Nothing on the device: no cookies, no localStorage IDs. A per-tab session ID lives in sessionStorage.
- The server derives a visitor ID by hashing a daily-rotating salt with the site ID, IP address and user agent. The IP is never stored.
- A visitor who returns on another day counts as new.
- Usually needs no consent banner. Check with your own adviser.
- Switching back to cookieless deletes the cookies the other script set.
In both modes
- Raw IP addresses are never written to disk. Only country, region and city are kept.
- No fingerprinting and no cross-site tracking.
- Visitors can opt out.
See the privacy policy, cookie policy and DPA.