Cookie Policy

1. On websites that use Datasense

Each site picks one of two scripts in its settings. The cookieless script (/js/script.js, the default) doesn't set or read cookies and doesn't store identifiers in local storage. It only uses:

• Session storage: a random id for the current browser tab, so pageviews in one visit are grouped together. It is deleted when the tab closes and is never shared across sites.
• Local storage key datasense_ignore: only present if someone sets it to exclude their own browser from a site's stats. The script reads it and sends nothing.

Unique visitors are counted with a daily-rotating hash instead of a cookie. See the Privacy Policy for how it works.

The cookie script (/js/script.cookies.js) recognizes returning visitors across days. It stores, on the website's own domain:

• datasense_vid (first-party cookie, 400 days, renewed on each visit): A random id that recognizes a returning visitor, shared across the site's subdomains.
• datasense_sid (first-party cookie, 30 minutes, renewed with activity): Groups one visit's pageviews into a session, across tabs.
• datasense_vid (local storage, until cleared, or the site switches back to the cookieless script): A backup of the visitor id, used if the cookie is deleted.

These are the website's first-party cookies: they're never sent to Datasense as cookies or shared across websites, and nothing is stored for visitors who opt out or, where the site respects it, send Do Not Track. If a site switches back to the cookieless script, it deletes them on the next visit.

Consent is the website owner's responsibility. In the EU, EEA, UK and other places with similar rules, the cookie script usually needs the visitor's consent first, through the site's own cookie banner. Datasense doesn't show banners. With either script, website owners should check what their local law requires and mention Datasense in their own privacy policy. If you're a visitor, the site's owner can tell you which script it uses.

2. On usedatasense.com

• Marketing pages: no cookies. We measure them with Datasense itself, which is cookieless.
• Dashboard: strictly necessary cookies set when you sign in, holding your session and protecting the sign-in flow against forgery. They expire when your session ends or after a period of inactivity, and the dashboard can't work without them, so they don't need consent.
• Preferences: your light or dark theme choice may be saved in your browser's local storage.

3. Third parties

When you go to checkout or the billing portal you are on Dodo Payments' pages, and “Continue with Google” takes you to Google. Those pages may set their own cookies under their own policies. We don't use advertising or social media cookies.

4. Managing cookies

You can delete or block cookies in your browser settings. Blocking them on usedatasense.com will sign you out of the dashboard but won't affect the marketing pages.