Privacy notice

Depending on enabled services, the platform may process a normalized email address and plan preference supplied with a founding-access request, account identifiers and a primary email address from Clerk, subscription and customer identifiers from Stripe, an account-linked history of observed subscription status and plan changes, and structured cancellation feedback and system reasons. Free-text cancellation comments remain in Stripe and are not copied into the application database. The platform may also process analysis usage, saved races, private race research notes, immutable pre-race research receipts and optional receipt rationales, tracked-runner and tracked-connection identifiers and alert preferences, Signal Scout and daily-briefing preferences, in-app notifications, opted-in email-delivery records and immutable delivery payloads used for retry safety, webhook endpoint URLs and derived delivery records, API-key metadata, security events, and consented affiliate-click records. Webhook signing secrets are deterministically derived from a server secret and endpoint identity rather than stored per customer.

Billing details, passwords, private account attributes, private race research notes and receipts, runner and connection trackers, and affiliate behaviour are not included in race-analysis prompts. Payment-card data is handled by Stripe and is not stored in the application database.

Data is used to record requested founding access and plan demand, contact people who explicitly requested launch information, authenticate users, enforce entitlements and budgets, deliver requested analyses, protect the platform, maintain audit history, settle predictions, and understand service reliability.

The architecture uses managed providers for identity, transactional email, billing, database hosting, caching, AI routing, analytics, and deployment. Clerk supplies the primary address only when an opted-in alert is delivered; Resend processes that address and message for delivery. Founding-access contacts can be exported only by an explicitly allowlisted operator, and every export is recorded in the security audit history. Each provider processes information according to its own contractual role and privacy terms.

Immutable shared predictions and their settled public record are retained as platform history because they are not linked to a customer account. Founding-access emails, account-linked subscription lifecycle and usage records, saved-race records, tracked runners and connections, alert, webhook and daily-briefing preferences, delivery records, private research notes, and research receipts should be retained only as long as needed for the requested contact, service, compliance, dispute handling, and security. Every founding-access confirmation email includes a private removal link; opening the link changes nothing until its holder explicitly confirms removal. Authenticated customers can download their application data—including observed subscription lifecycle and webhook delivery events—and request account deletion from the dashboard. Deletion requires an ended subscription, removes account-linked product records—including webhook endpoints, deliveries, subscription lifecycle events and receipts—and matching founding-access requests, and anonymizes retained security-audit and affiliate-click history. Stripe and Clerk remain responsible for data in their systems, and legal retention exceptions require separate review. Additional access, correction, objection, and other non-account request procedures must be finalised before broad paid launch.