Legal & policies

This page covers cookies, local storage and session storage. They are all ways a website can remember information in your browser, but they behave differently.

Sign-in cookies

If you sign in, an essential, HTTP-only session cookie keeps you signed in and protects access to your account. The built-in session lasts for up to 30 days; names and durations can differ when Supabase authentication is enabled. The cookie uses secure browser settings in production and is not available to page scripts. Signing out removes the active browser cookie.

First-party visit measurement

Public pages create a random visitor identifier in local storage and a random per-tab identifier in session storage. They help us estimate unique and returning visitors and group page views into visits. We send them to our own same-origin analytics endpoint with page, referral, campaign, browser, device and approximate location information. They are not advertising identifiers, but the persistent visitor identifier can distinguish one browser over time. If you disable this measurement below, a local preference remembers that choice so the first-party beacon stays off in that browser.

We also load Vercel Web Analytics and Speed Insights to measure aggregate use and technical performance. These services receive technical request data as our processors. The current site does not load third-party advertising pixels. An interactive course map also requests map styles and tiles from OpenFreeMap or another configured map provider when the map loads.

Runner profile

The free tools save a runner profile in local storage so answers and results carry between calculators and the coaching application. It can contain goals, race results, predicted times, paces, training volume, fuelling choices, workout preferences and an email after you enter one. It stays in that browser until it is cleared. Clearing it does not delete plans or information already saved to our server.

Your controls

You can also block or clear site data in your browser. Blocking essential sign-in cookies will prevent account features from working. Some jurisdictions require prior choice for non-essential browser storage; the production consent approach should be confirmed during legal review before launch in those markets.