Privacy and data use.

We currently collect account and profile data, authentication session data, profile preferences, and basic operational logs needed to keep the service available and secure.

We do not currently run advertising trackers or sell personal information. If non-essential analytics or marketing technologies are added later, this notice and the cookie experience should be updated before launch.

Account data: email address, authentication provider, account identifier, and Supabase session cookies used to keep you signed in.

Profile data: username, favorite constructor, favorite driver, avatar preference, onboarding state, and the related timestamps and cooldown fields used to manage profile changes.

Picks data: entertainment-only race picks, timestamps, point totals, and leaderboard display names when you choose to submit Picks while signed in.

Operational data: limited server logs, rate-limit identifiers derived from hashed client/network information, and request metadata used to secure the API and diagnose failures.

To authenticate accounts, persist your profile settings, and render your personalized profile experience.

To save entertainment-only Picks, calculate points, and show race or season leaderboard positions.

To secure the app, rate-limit sensitive routes, investigate failures, and prevent abuse of account flows.

To deliver the core race analytics product surfaces and the profile preferences you choose inside the app.

Where privacy law requires a legal basis, the current launch baseline relies primarily on contract or pre-contract necessity for account features, legitimate interests for service security and abuse prevention, and consent if non-essential tracking is introduced later.

Privacy obligations vary by jurisdiction. This policy should be reviewed when the product adds paid features, prizes, advertising, analytics tracking, or broader international distribution.

The app currently relies on strictly necessary authentication/session cookies provided through Supabase to support sign-in and account persistence, plus a first-party preference cookie that stores your cookie banner choice.

We do not currently deploy advertising cookies or non-essential analytics cookies in the product experience. See the Cookie Notice for more detail.

Supabase is used for authentication, account storage, and profile persistence.

Vercel or equivalent hosting infrastructure may process requests, logs, and deployment telemetry needed to run the app.

Google sign-in may be available if enabled in Supabase Authentication providers.

Profile data is retained while your account remains active, unless deletion is requested or the data is removed manually.

Operational logs should be retained only for a limited period needed for security and reliability review.

Auth/session retention is also subject to Supabase platform configuration and provider behavior.

You can access and correct your profile information directly in the account area.

You can export your current account/profile data from the account page.

Account deletion and broader privacy requests are currently handled manually. Contact f1.insightx@gmail.com for deletion, access, or correction requests that you cannot complete in-product.

If you receive a rights request through email today, fulfillment still depends on manual review and operator action. Automated deletion workflows are not yet implemented.

If you access the service from outside the country where its infrastructure operates, your data may be processed in other jurisdictions, including the United States.

The product is not designed for children under 13 and should not be positioned or marketed as a child-directed service.