Last updated: September 8, 2026
This policy explains how Orbit uses cookies, browser local storage, and similar technologies on orbitanalytics.app, and how the Orbit analytics script behaves when a customer installs it on another website. It should be read with our Privacy Policy.
Cookies are small text files that a website stores in a browser. Local storage is a separate browser feature that can retain information on a device. Although local storage is not technically a cookie, laws governing access to or storage of information on a device may apply to both, so this policy covers both technologies.
The standard Orbit analytics script does not write cookies or persistent identifiers to a visitor's browser. It can read an umami.disabled local storage flag if the visitor or website owner has placed one there to opt that browser out of tracking. The script sends analytics events to Orbit without setting an analytics cookie.
On our servers, an IP address and user-agent string are processed transiently to derive a salted, rotating pseudonymous identifier. Raw IP addresses are not stored in the analytics database, and the rotation period may vary with service configuration. This processing is described in more detail in our Privacy Policy.
Cookie-free does not by itself mean that every use of analytics is exempt from notice or consent requirements. Each customer decides why and how it uses Orbit and is responsible for assessing the rules that apply to its website, jurisdiction, and configuration. This is particularly important for optional session replay, heatmaps, and custom events, which may collect more detailed interaction data even though they do not rely on analytics cookies.
The public marketing pages do not use advertising cookies or cross-site advertising trackers. The dashboard uses browser local storage that is necessary to provide requested account features and to remember settings, including:
umami.auth, which keeps an account holder signed in by storing an authentication token until the user signs out, clears browser storage, or the token otherwise expires or is invalidated; andThese values are not used for advertising. Preference values generally remain until they are changed or browser storage is cleared. The authentication token is read by the dashboard and sent to Orbit when needed to authenticate account requests.
If you choose Google sign-in or open Polar's checkout or customer portal, you leave or interact with services operated by those providers. Google and Polar may use cookies or similar technologies on the pages and domains they control under their own policies. We do not use those services to place third-party advertising cookies on the Orbit dashboard.
You can remove Orbit dashboard data by signing out and clearing local storage for orbitanalytics.app in your browser settings. Clearing it will sign you out and reset saved preferences. Blocking necessary storage may prevent the dashboard from working correctly.
For tracking on a customer's website, use the privacy controls offered by that website or contact its owner. If browser Do Not Track support has been enabled by the website owner, the script will honour the browser signal. A website owner can also explain whether it uses optional replay, heatmap, or event features and the legal basis it relies on.
We may update this policy when our technology, providers, or legal obligations change. We will post the revised version here with a new effective date and provide additional notice when appropriate.
Email: hello@orbitanalytics.app
Postal address: Via Vignola 3, 20136 Milan, Italy