Privacy Policy
TRGT keeps the data model lean: account continuity, prediction state, badge progress, and the live race surfaces needed to run the experience without loading the product with irrelevant tracking.
What TRGT Stores
TRGT stores the minimum account, sign-in, badge, and prediction data needed to let you enter the product, lock race picks, track points, and keep your season history consistent.
What TRGT Uses
Session, standings, and circuit surfaces are powered by external motorsport data feeds together with local fallback snapshots. Those feeds are used to keep race information timely and visible throughout the product.
Your Control
If you stop using TRGT, the retained data is limited to the profile and prediction history needed for account continuity and rankings. The product UI is not built around ad-tech or noisy tracking layers.
Authentication
When you sign in, TRGT uses the authentication details needed to identify your account and connect predictions, badges, and profile state to the right user.
Operational Logging
Basic platform logs may exist for uptime, debugging, or API reliability, especially when upstream race feeds fail and the app needs to recover into cached or local snapshot mode.
Minimal by design
The product is built to store what it needs to operate the race experience and little else: identity, predictions, scoring state, and the data required to keep your season history coherent.
Race intelligence, standings, predictions, badges
Live feeds may degrade to cache or local snapshots when upstream services fail
Fan product, not an official Formula 1 property