Cookie Policy

Last updated June 10, 2026

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.

2. What we store, and why

• Essential local storage (widget): authentication and session tokens and lightweight UI state, so you stay signed in and the widget behaves correctly. Strictly necessary for the service to function.
• Website preferences: our marketing site may use essential local storage for basic preferences. It does not run advertising or cross-site tracking cookies.

3. Analytics

Our marketing website uses Google Analytics to understand aggregate, anonymized usage — for example, which pages are visited. Google Analytics sets its own cookies (such as _ga) and acts as a third-party processor; see our Subprocessors page. In the UK and EEA, these analytics cookies are used only with your consent, which you can change or withdraw at any time.

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 support@rebase.dev. See also our Privacy Policy.