RepairFlow

RepairFlow Web Beta

Cookie Notice

Effective date: June 22, 2026

RepairFlow Web currently uses essential session/security storage and a small set of preference storage. We do not currently use advertising, behavioral tracking, or marketing analytics cookies in the web beta.

Essential session cookie

RepairFlow Web creates an HTTP-only session cookie after sign-in. This cookie is used to keep your account signed in, protect authenticated routes, and verify your shop role on the server. It is essential for the service and cannot be disabled without signing out.

  • Name: __session, unless a different Firebase auth cookie name is configured.
  • Purpose: authentication, route protection, and shop role verification.
  • Duration: up to 5 days, or until sign out.
  • Access: HTTP-only, so browser JavaScript cannot read it.

Security tokens

RepairFlow Web may request Firebase App Check or reCAPTCHA Enterprise tokens for selected signup and account-protection requests. These are used to reduce abuse and automated misuse of beta signup flows.

Preference storage

RepairFlow Web stores a few local preferences in your browser:

  • sidebarOpen: remembers whether the dashboard sidebar is expanded or collapsed.
  • repairflow.print.presets.v1: remembers receipt and label print preferences.
  • repairflow:first-run-intake-banner-dismissed:*: remembers that a shop setup banner was dismissed for a shop.

Non-essential cookies

The current web beta does not use advertising cookies, behavioral tracking cookies, session replay, or marketing analytics pixels. If we add non-essential tracking or analytics later, we will add a consent and preferences control before enabling it.

Managing storage

You can clear RepairFlow Web cookies and local storage through your browser settings. Clearing the session cookie signs you out. Clearing preference storage may reset layout, onboarding, or print preferences.