Summary
Uplitycs does not set HTTP cookies for analytics. The public tracker uses first-party browser storage on the site where the script runs. The signed-in dashboard uses one session cookie so your sign-in works.
This notice sits with the Privacy Policy.
On sites that install the script
The tracking script may write:
- localStorage key
upl_vid— an anonymous visitor id (random UUID). It stays until the visitor or the site clears storage. It is sent with events so hourly unique counts work. - sessionStorage key
upl_sid— an anonymous session id for the current browser tab session.
These are not HTTP cookies. They are first-party storage on the customer’s site. We do not set a third-party cookie and we do not use a fingerprinting database.
If you operate a site with the script, you are responsible for telling your visitors about this storage and for any consent your local law requires.
On uplytics.space
Strictly necessary — session. When you sign in, we set one first-party cookie named upl_session so the dashboard knows it is you. It is not used for advertising.
Our own marketing site. In production the marketing site may load the Uplitycs tracker for the public demo property, using the same localStorage / sessionStorage keys described above — not an advertising cookie.
How to control storage
- Clear site data in the browser to remove
upl_vid/upl_sid. - Sign out of the dashboard to end the session; you can also clear cookies for Uplitycs.
- Most browsers can block or delete site storage per origin.
Blocking the session cookie will prevent sign-in. Blocking the tracker storage will reduce unique-visitor accuracy on sites that use the script; pageviews can still be counted.
Contact
Privacy questions: privacy@uplytics.space.