Sync service · privacy

What the sync service knows about you.

This page covers the hosted sync service at sync.gt7-datalogger.com. The datalogger itself runs on your own machine and sends nothing anywhere until you paste a connection string into it and switch a data type on. There are no ads, no analytics and no trackers, and nothing here is sold or handed to anyone to market to you.

Last updated 15 October 2026.

Who runs it

One person, as a hobby.

Hi, I’m JB (github.com/jbhoorasingh). I built the sync service and I run it on my own, so wherever this page says “the administrator”, that’s me — there is nobody else with access. It’s free to use: I pay for the hosting myself, with help from donations. It isn’t affiliated with Polyphony Digital or Sony.

If you’re using a copy of the service that somebody else hosts, that one is theirs to look after. This page only covers the one I run, and can’t speak for what happens to your data on anyone else’s.

Signing in

There are no passwords here. You sign in through one of three providers, the service asks each for the least it offers, and it keeps four things: the provider’s permanent id for your account, a login, a display name, and the address of your avatar image.

Provider	Permission asked for	What is kept as your login
GitHub	`read:user` — your public profile	your GitHub username
Discord	`identify` — your username and avatar; not your email, servers or messages	your Discord username
Google	`openid email profile` — your name, picture and email address	your email address, and only if Google says it is verified

Your login is never public. It is shown to you, under Profile → Account, and to the administrator. A Google account has no username, which is the only reason its email address is kept at all; GitHub and Discord are never asked for one. No email is ever sent to you.

Your display name can be public — see below — and you can change it in your profile at any time.

The access token a provider issues is used once, to ask who you are, and then thrown away. It is not stored, no refresh token is requested, and the service cannot act on your GitHub, Discord or Google account.

In your browser

Two cookies, both for signing in.

gt7sync_session keeps you signed in, for up to 30 days. The server stores only a hash of what it contains. Signing out deletes it.
gt7sync_oauth lasts ten minutes and exists only while you are being sent to a provider and back, so that a sign-in started in your browser cannot be finished in somebody else’s.

Neither can be read by scripts, and neither is used to follow you anywhere. The portal also remembers whether you prefer km/h or mph, in your browser’s local storage; that never leaves your device.

When you sign in, the session records your browser’s user-agent string and a keyed hash of your IP address — not the address itself, and not something that can be turned back into it without the server’s secret. No screen shows either, to you or to the administrator, and both are deleted with the session.

The pages load their typeface from Google Fonts, so Google receives your IP address when the font is fetched, as it would from any site that uses it.

What your logger sends

Three kinds of data, each off until you switch it on.

Track surveys

The borders and walls your logger measured as you drove a circuit. These are a contribution to a shared map: they are reviewed, merged with other people’s, and published in the public track-data repository under CC0.

A survey carries no name and no account. It does carry the random id of the installation that recorded it, and that id appears in the published file. Which account an installation belongs to is known only to the service and is never published.

Each circuit’s page lists the surveys that built it and when they were merged. You are listed there as “a contributor”, with the dates and no name, unless you turn track credit on in your profile — then your display name is printed beside your surveys. It is off until you turn it on, and turning it off takes the name down again. With it on, somebody who compares those dates with the published files could work out which installation id is yours.

Surveys are kept indefinitely, and stay if you delete your account — other people’s surveys have been merged against them.

Sessions

Your laps: times, sectors, the car, the telemetry behind the racing line — position, speed, throttle, brake, gear and the rest — and what your logger worked out about each lap: fuel, tyre temperatures, the lockups and wheelspin it detected.

Private to you unless you share it. Shared by link, a session can be opened by anyone who has the link — with your display name, the car, and every lap — and is listed nowhere; making it private again ends every link to it. A public session is also listed to anyone with your display name, car and best lap, and its laps can be compared against.

A session is deleted after 90 days, or by you, one at a time, whenever you like; one that still holds your best lap on that circuit and car is kept for as long as it does. The recording of a lap that is not its session’s best is removed after 30 days and its times stay. A shared or public session, or one you mark Keep all laps, keeps every recording.

Live

Your car’s position, speed, gear and lap, a few times a second, while you drive.

Private unless you make your stream public. While it is public, anyone — signed in or not — can watch it, and sees your display name, the track and the car.

Frames are relayed, not stored: a viewer who joins gets the last 30 seconds from memory. Recording is switched off on this service.

The connection string you paste into the logger contains a token. The service stores only a hash of it, along with the label you gave it and when it was last used. You can revoke a token at any time, which stops that logger uploading.

Behind the scenes

Logs, and a record of changes.

Request logs record the method, path, status and duration of a request, its query string with anything secret removed, and — when you are signed in or a token is used — the internal id of the account or token. Every request that changes something, is refused or fails is logged; of the ordinary reads that succeed, about one in ten is. They do not record your IP address or your browser. They are deleted after 14 days. Cloudflare, which hosts the service, keeps its own short-lived copy of the same lines, for every request.

The audit trail records changes: an account being created, a display name changed, a token issued or revoked, a session deleted, a setting altered. It exists so that the administrator’s own actions can be checked, and it is not deleted on a schedule. An entry can include the display name and login an account had at the time, and those entries remain after the account is deleted.

Who can see what

You, the administrator, and what you chose to publish.

Anyone can see the published track map; your display name beside a session or live stream you made public; a session you shared by link, if they have the link; your display name beside the surveys you contributed if you turned track credit on; and that stream or session’s track, car and times.
The administrator can see every account’s display name, login and avatar address, its installations, its uploads, its sessions including private ones, and its live stream, and can disable an account, reject an upload or end a stream. The administrator cannot see your tokens, and cannot share your sessions or make your stream public on your behalf.
The merge job — the automated process that turns surveys into the public map — can read uploaded surveys and the internal account id behind each installation, so that one person cannot count as several. It never sees a name or a login.

Other companies involved

A host, three sign-in providers, and a public repository.

Cloudflare hosts everything — the code, the database and the stored files — and so handles every request, including your IP address. Data is held on Cloudflare’s network, which may be outside your country.
GitHub, Discord or Google, whichever you sign in with, learns that you signed in to this service. The service sends them nothing else about you.
GitHub hosts the public track-data repository that accepted surveys are published to.
Google Fonts serves the typeface.

If the service fails badly it can post an alert to the administrator’s private chat. An alert names the fault and the circuit; it contains no account id, name or login.

Donations go through GitHub Sponsors and never touch this service, which learns nothing about who gave.

Leaving

Deleting your account, and what that does.

Profile → Account → Delete account. It takes effect at once and cannot be undone.

You are signed out everywhere and every token is revoked.
Your login and avatar address are erased, your display name becomes “deleted account”, and track credit is switched off, so your surveys are listed without a name.
Your live stream is closed, and any recordings of it are deleted.
Your sessions are made private immediately and deleted, laps and all, within a day.

What stays: the track surveys you contributed; an empty account record and the provider’s id for you, with nothing personal attached, so the same sign-in cannot be used to slip back in as a new contributor; the link between your installations and that record, for the same reason; revoked token records, without the tokens; and audit entries, as described above. Request logs expire after their 14 days.

Without deleting your account you can delete any session, revoke any token, and make a stream or session private again. There is not yet a way to remove a single survey, forget an installation, or unlink one sign-in provider while keeping another — ask, using the contact below.

Asking

A copy, a correction, a deletion, a question.

Wherever you live, you can ask what is held about you, ask for a copy, ask for something to be corrected or deleted, or object to how it is used. Your lap times can already be exported from the Sessions page.

To ask, open an issue at github.com/jbhoorasingh/gt7-datalogger/issues. Issues are public, so say only that you have a privacy request and how to reach you; do not post personal details there.

The service is not meant for children. You must be at least 13, or older if the provider you sign in with or the law where you live requires it.

If this page changes, the date at the top changes with it. A change to what is public about you, or to what is kept, will not be applied to data you have already uploaded without saying so here first.