Introduction
Our platform, including offhrs.app and partners.offhrs.app (collectively, the “Site”), uses cookies, device identifiers, local web storage, and server-side pixel tracking (such as the Meta Conversions API) to distinguish you from other users. This allows us to optimize booking workflows, verify active vendor dashboard sessions, and maintain a secure payment lifecycle.
1. Strictly necessary cookies
These tokens are vital to the platform’s core infrastructure. Disabling them will cause authentication timeouts, cart dropouts, and dashboard connection failures.
| Cookie name | Provider | Set on | Why we use it | Duration |
|---|---|---|---|---|
| sb-access-token | Supabase | *.offhrs.app | Stores the JWT used to maintain authenticated vendor and consumer sessions. | Session |
| sb-refresh-token | Supabase | *.offhrs.app | Used to safely reissue short-lived access tokens so you do not have to log in repeatedly. | 1 year |
| __stripe_mid | Stripe | *.offhrs.app | Machine identifier used by Stripe to run background risk analysis and detect card fraud. | 1 year |
| __stripe_sid | Stripe | *.offhrs.app | Session token used by Stripe to preserve payment state across checkout redirects. | 30 minutes |
2. Functionality cookies
These allow our views to remember local layout options and scheduling preferences.
| Cookie name | Provider | Set on | Why we use it | Duration |
|---|---|---|---|---|
| offhrs_tz | offhrs | *.offhrs.app | Stores the local timezone so booking dates render correctly against UTC server records. | 1 year |
| offhrs_theme | offhrs | *.offhrs.app | Caches user theme preferences (light / dark mode). | Persisted |
3. Analytical & performance cookies
These give us visibility into how users traverse the workshop discovery funnel so we can make finding classes in Toronto faster and more intuitive.
| Cookie name | Provider | Set on | Why we use it | Duration |
|---|---|---|---|---|
| _ga | *.offhrs.app | Assigns an anonymous client identifier to group pageviews and active dashboard traffic. | 2 years | |
| _gid | *.offhrs.app | Distinguishes unique users within a 24-hour cycle for reporting analytics. | 24 hours |
4. Targeting & advertising cookies
These variables are connected to our Meta and Google advertising accounts. They track conversion metrics (for example, whether a vendor clicked a Meta Reel ad and completed a trial registration).
| Cookie name | Provider | Set on | Why we use it | Duration |
|---|---|---|---|---|
| _fbp | Meta | offhrs.app | Used by Meta to identify browser traffic and deliver optimized retargeting on Facebook and Instagram. | 3 months |
| _gcl_au | offhrs.app | Collected by Google Ads to measure digital acquisition performance. | 3 months |
5. Disabling and managing cookies
Most modern web browsers accept tracking cookies by default. To revoke consent, alter cookie visibility, or wipe historical tracking, adjust your local device configurations:
- Google Chrome: Settings › Privacy and security › Third-party cookies
- Apple Safari: Settings › Safari › Advanced › Cookies and Website Data
- Mozilla Firefox: Settings › Privacy & Security › Cookies and Site Data
Note on platform interaction: if you configure your browser to drop or block all strictly necessary tracking flags, you will be unable to initialize vendor dashboards on partners.offhrs.app or securely register for workshops on offhrs.app.