Browser storage, without the mystery.

Essential technologies support authentication, security, load balancing, payment and identity-provider handoffs, fraud prevention, requested settings, and your privacy choice. They are not used by HandyConnect for cross-context behavioral advertising. Blocking them in your browser may prevent sign-in, contracts, checkout, verification, or other core functions.

• Supabase authentication cookies: session and refresh information used to keep you signed in and secure requests. Duration follows the active session and Supabase Auth configuration.
• hc_privacy: stores the policy version plus analytics and marketing choices for up to 180 days.
• Interface storage: remembers theme, onboarding, inbox, map, or other requested settings. Some values last for the browser session; others remain until replaced, cleared, or no longer needed.
• Stripe technologies: Stripe may use cookies or device information on hosted Checkout, Connect, and Identity pages for security, fraud prevention, payment, and verification. Stripe controls those technologies under its own notices.

When you enable Analytics, the Platform may use:

• First-party visit and event measurement: an hc_vid pseudonymous visitor cookie lasting up to one year, plus page path, referring origin, browser user agent, and selected event metadata. Sensitive account, dashboard, invite, and admin routes are excluded from this page-view collection.
• Vercel Analytics and Speed Insights: traffic and performance measurement provided by our hosting provider.
• Sentry: if configured, minimized error and performance telemetry. Client collection is consent-gated, default user details are disabled, and request bodies, cookies, and headers are removed from submitted browser errors.

Analytics stays off until selected. Turning it off stops new optional collection and clears supported first-party optional browser data and cookies. Provider-side records already collected follow the retention and deletion processes described in the Privacy Policy.

When you enable Marketing and no recognized opt-out signal applies, Google Analytics or Google Ads and Meta Pixel may load if their production identifiers are configured. They can receive page, device, browser, campaign, click, registration, lead, contact, scheduling, and call-to-action event data and may set or read identifiers such as _ga, _gcl_*, _fbp, or _fbc. Provider durations and uses are controlled in part by their settings and policies.

Campaign parameters and the referring site may also be stored in hc_attributionlocal storage and associated with a signup or job. Marketing is not necessary to use the Platform. Turning it off stops new marketing collection and clears supported Google, Meta, and first-party attribution values that the browser allows us to remove.

Open Privacy Choices to accept, reject, or separately set Analytics and Marketing. Rejecting optional technologies does not affect sign-in, contracts, or payments. You can also clear browser data or block cookies through browser settings, although blocking essential storage can break core features.

When your browser sends Global Privacy Control, Marketing is forced off for that browser, campaign attribution is not used, and supported optional marketing data is cleared. GPC does not disable essential technology or analytics you separately selected. The signal is browser- and device-specific, so enable it everywhere you want it applied.

We do not treat a generic “Do Not Track” header as an analytics choice because browsers have not standardized its meaning. Use Privacy Choices or GPC for the controls described here.