TRACE sends a small amount of anonymous usage data by default, and lets you optionally submit lap times to a public leaderboard — with an optional free account if you want your name on it. Here's exactly what each of those is, and how to control them — plus what this website itself collects, which is a separate thing.
Each time you launch Live Dashboard, Lap Analyst, or Race Analyst, TRACE sends one small anonymous record. This is on by default — you can turn it off any time in Settings → Share anonymous usage data.
| Field | What it is |
|---|---|
| event | Which action happened — e.g. "app launch" |
| tool | Which tool was opened — dashboard, lap analyst, or race analyst |
| version | Your installed TRACE version, e.g. 0.3.3 |
| os | Windows, macOS, or Linux |
| timestamp | When the launch happened |
That's the whole record. Five fields, nothing else. It's used only to see which tools actually get used and whether people are on a current version — nothing more.
This section is about the TRACE desktop app. This website is separate and is covered further down under This Website.
Data submitted to any opt-in feature — like the leaderboard below — is separate, always explicit (a button you click), and disclosed in full right here.
Submitting a lap to the leaderboard is never automatic — it only happens when you press "Submit to Leaderboard" in Lap Analyst. Here's exactly what's sent for each submission:
| Field | What it is |
|---|---|
| car_name | The car you were driving |
| track_name | The track you were on |
| lap_time_ms | Your lap time |
| psn_name | The name you typed into the submit dialog — self-reported, not read from your PlayStation account |
| samples | A compact per-sample trace of the lap — track position, speed, throttle, brake, steering, and gear only. No GPS coordinates, no other telemetry channels |
The leaderboard itself is public — any lap you submit, along with the PSN name you typed in, is visible to anyone using TRACE via the Top-10 panel and can be downloaded as a ghost lap. Don't submit under a name you don't want publicly associated with that lap time.
Every submission passes through server-side anti-cheat before it can appear: a lap that's physically impossible for that track's length is rejected outright, and a lap that beats the current record by more than 20% is held in a private review queue instead of publishing immediately. Both checks run in the database itself, not in the app.
If GT7 reports a car ID that isn't in the local database yet, or you type a track name that isn't in the picker, that name/ID is also submitted automatically to a shared community inbox — this one isn't a button you press, but it only ever sends the car ID or track name itself, nothing else about your session.
The first time you open TRACE, it offers a free account so a leaderboard submission ties to something real instead of a self-typed name anyone could fake. Creating one is entirely optional — skip it and everything except submitting a lap still works exactly the same: viewing the leaderboard, downloading ghost laps, and the consensus line all stay fully available.
| Field | What it is |
|---|---|
| display_name | Whatever name you type when creating the account. Note this is stored separately from the psn_name above — the name shown on a leaderboard row is the one you type in the submit dialog each time, not this one |
| account ID | An anonymous identifier created via Supabase's anonymous sign-in — no email, no password, ever |
That's it — a display name and an anonymous ID, nothing else. No email address is asked for or stored, no password exists to leak, and nothing ties the account to your PlayStation identity, your real name, or anything else about you. It exists purely so a leaderboard row belongs to a real (if anonymous) account rather than any name a submission form happens to have typed into it.
Skipped it and changed your mind? Sign up any time from the tool menu — nothing is lost, and there's no penalty for waiting.
Everything above is about the TRACE desktop app. This site — gt7trace.netlify.app — does two things of its own, and they run whether or not you ever download TRACE.
| What | What it does |
|---|---|
| Google Analytics | Loaded on every page of this site (measurement ID G-1DRKJH6JTG). Google records the usual web-analytics signals — pages visited, referrer, approximate location, device and browser, and a cookie-based visitor ID. Unlike the in-app ping, this is Google's product and runs under Google's privacy policy; your IP address reaches Google as part of any web request. |
| Download counter | Clicking a download button on the Setup page sends one record to the same Supabase project used by the app, containing a single field: which platform you clicked (windows, linux, macos, or source). Nothing else — no identifier, no session, no page history. It's fire-and-forget and never delays or blocks the download. |
Neither of these touches the app. The TRACE desktop app never loads this website, never loads Google Analytics, and never reports anything about your browsing. Blocking analytics in your browser — or just not visiting this site — has no effect on how TRACE works.
To opt out of the Google Analytics side, any standard content blocker or Google's own opt-out browser add-on will do it. The download counter has no personal data to opt out of, but a content blocker will stop it too.
The app analytics, leaderboard, account and download-counter data are all stored in a Supabase project controlled by the TRACE developer. None of it is sold, and none of it is shared with third parties. (Google Analytics is the exception to "no third parties" and is called out separately above — that data lives with Google, not with us.) Usage analytics exists purely to answer questions like "is anyone actually using Race Analyst" and "did people update to the latest version." Leaderboard and account data exists to run the leaderboard, ghost-lap download, and consensus racing-line features — none of it is used to track anyone individually beyond the display name shown on a public leaderboard row.
Questions about this page or a data request: reach out via GitHub Issues.