1. The Short Version

We don't use cookies for tracking or advertising. We use browser localStorage to remember your preferences and keep you logged in. That's it.

No cookie banner needed because there are no cookies to consent to. We believe in being straightforward: if you use ROLLIN, the only data stored in your browser exists to make your experience better. Nothing is sold. Nothing is shared with advertisers. Nothing follows you around the internet.

2. What Are Cookies vs. Local Storage

Cookies are small files that get sent to a server with every single request your browser makes. This is how many websites track you across the internet — a cookie placed by one site can be read by another, building a profile of your browsing habits.

localStorage is different. It stays entirely on your device. It is never automatically sent to any server. No one can read it except the website that created it. It's simply a way for a website to remember things locally — like your preferences — without phoning home.

ROLLIN primarily uses localStorage. The only cookie involved is a secure authentication token set by our login provider, and it exists solely to keep you logged in.

3. What We Store (and Why)

Here is a complete list of everything ROLLIN stores in your browser:

Storage Item Type Purpose Duration
sb-*-auth-token Supabase Cookie Authentication session Until logout
theme-preference localStorage Dark/light mode choice Persistent
rollin-region localStorage Last selected region Persistent
rollin-filters localStorage Your accessibility filter selections Persistent
rollin-updates-dismissed localStorage Which update notices you've dismissed Persistent
rollin-analytics-session localStorage Anonymous session ID for privacy-first analytics Session
Service Worker Cache Cache API Offline access to map tiles, CSS, JS, images Until SW update

That's it. No hidden entries. No surprise trackers.

4. What We Do NOT Store

We want to be crystal clear about what you will never find in your browser from ROLLIN:

5. Third-Party Services

We use a small number of third-party services to run ROLLIN. In the interest of transparency, here is what they may store:

Supabase (Authentication)

Supabase handles user login and sets a secure, httpOnly cookie to maintain your authentication session. This cookie is used exclusively for keeping you logged in and is not used for tracking.

Stripe (Payment Processing)

If you purchase an API subscription, Stripe may set cookies during the checkout flow to process your payment securely. These cookies are limited to the payment process and are governed by Stripe's Privacy Policy.

Leaflet / OpenStreetMap (Map Tiles)

Our interactive map uses Leaflet with OpenStreetMap tiles. The tile servers may set cookies for caching purposes. These are functional cookies required to display the map and are governed by OpenStreetMap's Privacy Policy.

6. Service Worker and Offline Storage

ROLLIN is a Progressive Web App (PWA). This means it can work offline or in low-connectivity situations, which is especially important for users who need accessibility information on the go.

Our service worker caches static assets — CSS, JavaScript, images, fonts — and map data so the app loads quickly and works even without an internet connection. All of this data stays entirely on your device.

You can clear this cached data at any time by:

7. How to Clear Storage

If you want to clear everything ROLLIN has stored in your browser, here's how to do it in each major browser. Note that clearing this data will log you out and reset your preferences.

Google Chrome

Safari

Firefox

8. Contact

Questions about our storage practices? We're happy to explain anything in more detail.

Email us at hello@joinrollin.com