1. The widget uses no cookies
The widget does not use cookies or account tokens. It keeps a short, scrubbed record of recent activity and correlation identifiers in session storage, so a report keeps its recent context across navigation. When packets are on for a website (the default), it also keeps scrubbed details of recent visits in IndexedDB for up to 24 hours, within 5 MiB. Replays stay in memory only. The demo on our website is illustrative and does not send reports.
2. What we store, and why
- Dashboard: your sign-in token in local storage, plus small preferences and unsent drafts in local and session storage. If you arrived from a link on our website, the page and campaign it names, until you create a workspace (at most 30 days).
- Widget: bounded session context and, when packets are on, recent visit details, without background uploads or product analytics events.
- Marketing website: your consent choice in a cookie and local storage (
rebase_cookie_consent, kept for 12 months), optional analytics identifiers when you consent, and, for the visit only, the first page you opened, the site that linked to it and any campaign tags in that link (rb_first_touch, session storage). That last one holds no identifier and sends nothing by itself: it is added to the links into the dashboard, so a new workspace records which page and campaign brought it. Rejecting optional cookies clears it and turns it off.
3. Analytics
With your consent, our marketing website uses Google Analytics — which sets its own cookies (such as _ga) and acts as a third-party processor, see our Subprocessors page. It doesn’t load without your consent, wherever you are — not just in the UK and EEA — and you can change or withdraw your choice at any time via “Cookie settings” in the footer.
4. No advertising or cross-site tracking
We do not use cookies for advertising, ad targeting, or selling data, and we do not embed third-party advertising trackers.
5. Managing storage
You can clear cookies and local storage at any time through your browser settings. Clearing the dashboard’s storage signs you out; clearing a website’s storage removes what the widget saved there.
6. Changes & contact
If our use of cookies or local storage changes, we’ll update this page. Questions? Email support@rebase.dev. See also our Privacy Policy.