Cookie Controls

Cookie Policy

This Cookie Policy explains every major category of browser storage Arbitrer uses, why it exists, how consent works, and how you can change preferences.

What are cookies and browser storage?

Cookies are small text files stored on your device by a website. They help keep you logged in, remember choices, secure sessions, and understand how the service performs.

Arbitrer may also use localStorage and sessionStorage. These browser storage mechanisms can remember settings or session state but are not automatically sent to our servers with every request like traditional cookies.

1. Scope of this policy

This policy applies to Arbitrer websites, app routes, dashboards, subdomains, franchise or partner pages, support flows, checkout flows, and any web-based product experience that links to this policy.

For broader information about personal data, rights, retention, and service providers, read the Privacy Policy.

2. Cookie and storage inventory

The names below describe the current and expected storage patterns used by Arbitrer. Exact names may vary by provider, environment, or deployment.

Name or pattern	Category	Storage	Provider	Purpose	Duration
arbitrer_cookie_consent	Necessary	Cookie or localStorage	Arbitrer	Stores consent choices, banner version, and timestamp.	Up to 180 days
arbitrer_session / auth token patterns	Necessary	Cookie or localStorage	Arbitrer / auth provider	Keeps authenticated users signed in and secures dashboard access.	Session to 30 days
route_recovery / lazy_reload flags	Necessary	sessionStorage	Arbitrer	Prevents route recovery loops after chunk load failures.	Session
dashboard_preferences	Preferences	localStorage	Arbitrer	Stores UI state such as dismissed panels, dashboard choices, and local preferences.	Until cleared
referral_code / utm_*	Analytics	sessionStorage or localStorage	Arbitrer	Attributes signup source, campaign, partner, or franchise relationship.	Session to 90 days
Vercel Analytics identifiers	Analytics	Cookie or script event	Vercel	Measures page views and aggregate product performance.	Provider controlled
Vercel Speed Insights identifiers	Analytics	Script event	Vercel	Measures web vitals and performance issues.	Provider controlled
ph_* PostHog identifiers	Analytics	Cookie or localStorage	PostHog (EU region)	Records session replays of page content and on-screen activity, plus which pages are visited, so Arbitrer can see how the product is used and diagnose issues. Passwords and access tokens are never recorded.	Provider controlled
support or monitoring identifiers	Necessary / Analytics	Cookie or localStorage	Arbitrer or support provider	Helps diagnose errors, abuse, incidents, and support tickets.	Provider controlled
future marketing pixels	Marketing	Cookie or script event	Advertising provider	Only used if Arbitrer activates advertising and obtains required consent.	Provider controlled

3. Cookie categories explained

Strictly necessary

These are required for authentication, security, consent records, routing, fraud prevention, and core platform operation. You cannot opt out of necessary cookies through the Arbitrer preference panel because the service would not work without them.

Preferences

Preference storage remembers interface choices such as dismissed notices, language, local dashboard state, and similar convenience settings.

Analytics

Analytics storage helps Arbitrer understand page views, feature usage, conversion paths, performance, and reliability. Where required, analytics is blocked until you consent.

Marketing

Marketing cookies track advertising performance or targeted campaigns. Arbitrer does not need marketing cookies for core operation, and they should only be activated after renewed consent where required.

5. Third-party cookies and scripts

Some providers may set their own cookies or run scripts when enabled. This can include analytics, performance monitoring, support tools, payment tools, anti-abuse systems, or embedded content. Those providers process data under their own policies.

Where practical, Arbitrer configures third-party tools to limit unnecessary data collection, use aggregate reporting, and avoid optional tracking before consent.

6. Managing cookies in your browser

Blocking necessary cookies may prevent login, dashboard access, checkout, security checks, or preference storage from working correctly.

Chrome: Settings > Privacy and security > Third-party cookies or Site settings.
Firefox: Settings > Privacy & Security > Cookies and Site Data.
Safari: Settings or Preferences > Privacy > Manage Website Data.
Edge: Settings > Cookies and site permissions > Manage and delete cookies.
Brave and Opera: use the browser privacy, shield, or site settings controls.

7. Consent logs and accountability

Where required, Arbitrer may keep consent logs that record the timestamp, choice categories, policy or banner version, and technical data needed to prove compliance. Consent logs are used for compliance and not for advertising.

8. Changes to this Cookie Policy

We may update this policy when providers, cookies, storage items, consent tools, or laws change. Material changes may reset the banner or ask users to confirm preferences again.