Cookies & storage
Effective date: 22 September 2026
The website and native app use limited device storage for sign-in, preferences, and optional usage statistics.
1. Website storage
- Clerk authentication storage: cookies or browser storage managed by Clerk keep account sign-in and security working. Names and lifetimes are controlled by Clerk rather than set in Runsembly code.
- runsembly-privacy-v1: local storage containing the consent version, optional-statistics choice, save time, and configured analytics scope. It expires in Runsembly after 180 days.
- runsembly:discover-filters: session storage for race search and filter choices. It lasts for the browser-tab session.
- runsembly-account-deletion-started: a one-time session value used to confirm deletion has started after sign-out, then removed.
- sidebar_state: a seven-day cookie used by the shared sidebar component to remember whether a sidebar is open.
- GAESA: a cookie observed on published Runsembly responses from Google’s serving infrastructure. Replit documents that it routes requests to the correct published instance; it is not created or controlled by Runsembly and is not used for Runsembly account data. The observed response lifetime was about 30 days.
2. Native app storage
- Clerk token cache: sign-in tokens are stored in Expo SecureStore using Clerk-provided key names. Runsembly does not configure a separate token lifetime.
- runsembly-privacy-v1: the optional-statistics choice is stored in Expo SecureStore and is valid for up to 180 days.
Native choices are separate from website choices and from choices made on another device.
3. Optional Plausible statistics
Plausible statistics are disabled in this version’s configuration, so this Runsembly integration sends no analytics requests.
When enabled and allowed, approved public page views may be counted. Race-page URLs are reduced to a generic race-detail path, and query parameters are excluded. The website may also send these custom events: “Sign up started,” “Registration submitted,” “Plan created,” “Plan joined,” and “Share clicked.” Registration, plan, and share events have only one custom property: race, containing the public event key and edition. “Sign up started” has no custom properties. Events do not contain user IDs, names, email addresses, plan titles, or free text. Private page paths are not sent. Requests still include the normal network and device information received by a web service, but use no Runsembly analytics cookie or persistent analytics identifier.
Events are sent only after the relevant click or successful action. On the website, DNT or GPC keeps optional statistics off. If a preference cannot be read or saved, or consent has expired, statistics remain off.
Published pages also include Replit’s hosting-layer request for its default published-app traffic metrics. Replit describes those metrics as IP-based and separate from Runsembly’s Plausible integration; the Runsembly preference does not control them.
4. Change or withdraw your choice
Rejecting optional statistics does not disable authentication or essential product features. Your choice can be changed at any time and applies only to this browser or app installation.
5. Other provider requests
Authentication, hosting, Google Maps and Places, directions links, Replit’s published-app traffic metrics, and push notifications can make provider requests for their product purpose. The Plausible preference does not control those requests. See the Privacy Policy for provider and data-use information.