RaceHQ legal
Cookie Policy
RaceHQ uses cookies and browser storage to keep accounts signed in, remember settings, run RaceHQ+ billing, protect the site, and improve the product.
Last updated: 17 July 2026What Cookies Mean Here
Cookies are small bits of information saved by your browser. Browser storage is similar and can include local storage or session storage. RaceHQ uses both where needed for normal app behaviour.
Some cookies are essential. Without them, logins, subscriptions, organiser tools, watchlists, and protected RaceHQ+ features may not work properly.
Essential Cookies And Storage
- Data collected
- Login session, account authentication state, security checks, and basic site preferences.
- Why it is used
- Needed so you can sign in, stay signed in, use protected pages, and keep the site secure.
- Examples
- Supabase auth/session storage, security cookies, browser local storage used by the app.
Preference Storage
- Data collected
- Theme choice, interface preferences, recently used settings, and small browser-only settings.
- Why it is used
- Used so RaceHQ remembers things like dark/light mode and other display choices.
- Examples
- Theme storage and UI preference values saved in your browser.
Payment And Subscription Cookies
- Data collected
- Checkout session information, billing portal state, fraud-prevention signals, and payment status handled by Stripe.
- Why it is used
- Needed for RaceHQ+ checkout, subscription management, free trials, invoices, fraud prevention, and payment security.
- Examples
- Stripe checkout and billing portal cookies or local storage.
Performance And Product Analytics
- Data collected
- Pages visited, feature usage, approximate device/browser details, errors, and basic performance information.
- Why it is used
- Used to understand what works, fix bugs, improve loading, and decide what RaceHQ should build next.
- Examples
- Vercel analytics, future privacy-friendly analytics, and error/performance logs if enabled.
Embedded Or Third-Party Content
- Data collected
- Information set by third-party tools if RaceHQ embeds maps, videos, payment pages, timing widgets, or official event services.
- Why it is used
- Used only when those features are loaded or connected to an event page.
- Examples
- Timing provider widgets, official event embeds, map tools, or media embeds.
Your Choices
You can usually block or delete cookies in your browser settings. If you block essential cookies or storage, RaceHQ may not be able to sign you in, remember your theme, manage RaceHQ+, or show protected features.
If RaceHQ later adds optional analytics or marketing tools that need consent controls, the site should show a clear cookie choice before using those optional tools.