Skip to content

Cookies

What the Otopair website keeps in your browser, who puts it there and why. No advertising or analytics cookies.

Last updated

The short version

The website stores a few things in your browser: what the sign-in service for shop staff and the map need to run, and a note of how you reached the site, which Otopair receives only if you join the waitlist. Otopair runs no advertising or analytics tools on the site, and nothing it stores is used for cross-context behavioral advertising.

Sign-in

Clerk runs sign-in for the Otopair shop portal, at clerk.otopair.com. Its script loads on every page so the site can tell whether you’re signed in, and it stores these whether or not you have an account:

  • __client. A cookie on clerk.otopair.com that identifies this browser to the sign-in service. Pages can’t read it. Lasts up to 400 days.
  • __client_uat, sometimes twice with a short suffix. A cookie recording whether this browser is signed in. It holds 0 when you aren’t. Lasts up to 400 days.
  • __clerk_environment. A local-storage copy of the sign-in settings, which Clerk falls back on if it can’t reach its service. It expires after a day.
  • __cf_bm and _cfuvid. Cookies Cloudflare sets on clerk.otopair.com to keep bots out. The first lasts 30 minutes; the second ends when you close the browser.

Signing in to the shop portal adds the cookies that keep you signed in: __session, __refresh and clerk_active_context. When a session needs renewing, Clerk may also set cookies beginning __clerk_handshake or __clerk_redirect, which last a few seconds.

Maps

The live map on the home, Coverage, Staten Island and Contact pages comes from Mapbox. Once it loads, Mapbox stores:

  • mapbox.eventData. Three local-storage entries holding an anonymous ID that Mapbox uses to count map loads and monthly visitors, which is how it bills Otopair. The ID is replaced every 24 hours and isn’t linked to an Otopair account.
  • mapbox-tiles. A browser cache of map pieces, so the map draws faster next time.

Otopair has switched off Mapbox’s optional performance reporting. The other map pictures on the site are plain images and store nothing.

Sign-up source

  • otopair_attribution. A session-storage entry noting how you reached the site on this visit: the campaign tags on the link you followed (such as the link in Otopair’s Instagram bio), the first page you opened, and the site that sent you, without its full address. It stays in your browser unless you join the waitlist, when it’s saved with your sign-up so Otopair knows which posts bring people in. It ends when you close the tab.

Services your browser connects to

Like any web request, each of these sees your IP address and browser type.

  • Sign-in. Clerk, on every page.
  • Otopair’s database host. Convex, for the live shop count, the map’s shops and shop photos.
  • Maps. Mapbox, for map pieces and map pictures. Typing in the map’s search box sends what you type to Mapbox to find the place.
  • Oto. Nothing connects until you start a conversation. Then what you type or say goes to ElevenLabs, which runs Oto’s conversations, and if you give Oto a car, its picture loads from the vehicle-data provider. Chatting stores nothing in your browser; the Privacy Policy says how long conversations are kept.
  • Shop application. Typing a street address on the application form sends it to Google for address suggestions.

Your choices

  • Clear or block them. Your browser’s settings can delete or block cookies and site storage. Without Clerk’s cookies, shop sign-in stops working; the rest of the site still works.
  • Global Privacy Control. If your browser sends one, the opt-out form on Your privacy choices records it with your request to stop Otopair licensing your car’s service history.
  • Do Not Track. The website doesn’t respond to Do Not Track signals.

If what the site stores changes, this page will change with it. Questions go to support@otopair.com.