How your data is handled.

When you sign in, from Patreon: the account ID Patreon uses for you, your email address, and your Patreon display name. That's the entire request. No pledge history, payment details, card, or address. We never see your Patreon password, and we don't keep Patreon's access token once sign-in is done.

When you sign in, from Discord: your Discord account ID, verified email address and display name. We request only Discord's basic identity and email permissions. If you connect both sign-in methods, we retain the second provider's account ID to recognize it; your original GhostGauge account, races and devices stay together. We do not keep Discord's access token once sign-in is done.

When you race: a finished race uploads its recording — the raw telemetry stream the game produced — along with the times, lap and sector splits, the car, the track, the date and the app version. The recording is what lets us re-run the race and check the times independently. While the app runs it also reports each car's total distance driven — free roam included. That total is what your career distance is made of.

The recording describes the car, not you: speed, position on the map, throttle, brake, steering, suspension, tyres. Forza's telemetry carries no player name — there is no field in it for one.

What you choose to add: your Race Driver name, the age bracket you declare at sign-in (recorded once, never overwritten), any screenshots you send to the gallery, and anything you write on the feedback form.

Browser dashboards: when you choose Connect in browser, your game sends telemetry to our Hostinger VPS. We keep a separate recording and history for your account, your assigned connection port, and your home network's public IPv4 address to restrict incoming telemetry. Your finished races use the same account upload and publication rules as the apps. Stop connection ends recording; reconnecting keeps your saved races.

Automatically: necessary cookies, listed below. On the feedback form and the track-submission form, we store a scrambled form of your IP address to stop one person flooding them — and, on the feedback form, your browser's user-agent string. Those forms do not keep the address itself. Browser telemetry pairing keeps the public IPv4 address as described above.

Public when a race is published: its track, car, class, times, lap count, date and any flags. Confirmed races are published by default. Your driver profile is public too — Race Driver name, licence number and year, record times, approved gallery shots, and crowns, titles and career totals drawn from every confirmed race, published or not.

Your email address is never public. It appears on no page, in no board, in no profile, in no API response anyone else can call.

Your provider display name is never public either. No other driver can see it — it appears on your own account page, labelled private, and is available to the site administrator for account moderation. Boards and profiles show the Race Driver name you chose for yourself and nothing else.

Publish all is the default for every user. It applies to confirmed races already in your history and future completed races. Validation, Race Driver name and online-start requirements still apply. Races you or an administrator explicitly unpublished stay unpublished. You can unpublish individual races in My Races.

The following companies handle sign-in or hosting:

• Patreon — handles sign-in if you choose that method. We send them nothing you have not already given them.
• Discord — handles sign-in if you choose that method. We do not request your servers, messages or contacts.
• Hostinger — hosts this site and serves it through their network.

No analytics. No tracking pixels. No advertising. No profiling.

These cookies support sign-in and your private dashboard:

• gg_session — keeps you signed in. 30 days.
• gg_oauth_state — a single-use security check during sign-in, burned the moment it's used. ten minutes.
• gg_oauth_flow — remembers whether you are signing in or connecting another provider; removed after the callback. Ten minutes.
• gg_age_attest — carries the age you declared through the sign-in round trip, then is burned. ten minutes.
• __Host-ggweb — opens only your browser dashboard on the telemetry server. Up to eight hours; website sign-out or device revocation invalidates access.

These authentication cookies are Secure, HttpOnly and SameSite=Lax, and none is readable by scripts on the page.

There is no cookie banner because there is nothing to consent to.

While your account is open: we keep it until you delete it. Nothing is removed on a timer, and we do not thin your history out behind your back. A race’s recording is kept for as long as the race itself, so a result can be re-checked later as the checks improve.

When you delete your account: it disappears from GhostGauge immediately. Your races leave every leaderboard and your profile stops existing. Your Race Driver name is released straight away for someone else to claim.

Your races and their recordings go with it, and so do your screenshots. We keep no copy, so there is nothing to ask us for later and nothing for anyone to recover. If you sent in a custom track's share code, the code stays in the queue with your details taken off it.

The browser telemetry server checks account deletion and removes its recording copy and saved pairing address within five minutes while the services are available. If a service is unavailable, access is refused and cleanup retries when it returns. A port reservation is retained so an old game configuration can never send to a different account.

Deleting is the one thing on this site you cannot undo. Export first — it carries everything except the recordings themselves, which are named and fingerprinted in it but too large to hand back.

We don't have a password of yours to lose — sign-in goes through Patreon or Discord and no GhostGauge password exists. Session tokens are stored only as hashes, so the database doesn't hold anything that could be used to sign in as you. Race recordings live outside the public web directory and are never served directly. Sign-in, dashboard viewing and account uploads use HTTPS. The game's Data Out uses unencrypted UDP; source filtering does not make those game packets cryptographically authenticated. The browser recording service holds a revocable device credential, protected by server file permissions, to upload your finished races.

No system is perfectly secure, and one person running a small service is not going to pretend otherwise. If something goes wrong that affects your data, we'll tell you.

You must be at least 13 to hold an account. We don't knowingly collect anything from anyone younger; if we learn an account belongs to someone under 13, we close it and delete the data.

If you're between 13 and 17, everything on this page applies to you the same way — and two things are worth knowing specifically. We never sell your information and we run no advertising, profiling or tracking of any kind, for anyone, at any age. Confirmed races are published by default for every account: you can unpublish individual races in My Races, your screenshots wait for approval before anyone sees them, and the only name shown anywhere is the racing name you picked.

Supporting on Patreon is different — that's 18 and over, or younger with a parent or guardian's permission.

Parents: if your child holds an account and you want it removed, write to us and we'll delete it immediately.

If you live in California: we don't sell or share your personal information, and we never have. We don't allow third parties to collect personal information about you across other sites through this service. Your browser may send a "Do Not Track" signal; there's no agreed standard for honouring one, so we don't respond to it — but since we run no tracking or advertising of any kind, there's nothing for it to switch off.

Whatever state you're in, you can export your data and delete your account yourself, from your account page, without asking us.

When this policy changes in a way that matters, the date at the top changes with it and the change is noted on the site. Questions go to the feedback page, or to connect@GhostGauge.pro.