v1.4.0Triage that admits when there's nothing to find

Cookie Policy

Last updated

This policy explains how Rebase uses cookies and similar browser storage. Our approach is deliberately minimal.

1. The widget is cookieless

The Rebase widget and API do not use cookies. Authentication is handled with short-lived tokens kept in your browser’s local storage on the device you sign in from — not cookies — and the API is stateless. This means embedding the widget does not add tracking cookies to your site. The interactive demo on our demo page loads the real widget, which behaves the same way.

2. What we store, and why

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 — and our own first-party analytics, which sends anonymous usage events (page views, clicks on key actions) to our API so we hold our own copy of how the site is used. Neither loads 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 widget’s storage will sign you out and reset widget UI state.

6. Changes & contact

If our use of cookies or local storage changes, we’ll update this page. Questions? Email [email protected]. See also our Privacy Policy.