Privacy Policy

Track N Race ("Track N Race," "we," "us," or "our") is an open-source, local-first telemetry dashboard and session recording project designed for use with racing simulation software and compatible devices.

This Privacy Policy applies to the following:

Android App

The Track N Race mobile application for Android.

Desktop App

The Track N Race desktop applications for Windows, macOS and Linux, including the Electron, Native and Minimal builds.

Website

The Track N Race website at track-n-race.com.

The Android App and the Desktop App are referred to together as the "Apps." The Apps, together with the Website, are referred to as the "Services."

The Apps are designed to operate without a backend server or cloud-based data processing infrastructure. We do not operate a service that collects telemetry, account information, or other personal information from the Apps. Communications required for their core functionality take place between compatible devices on the user's local network. The limited exceptions, such as optional update checks in the Desktop App, are described in this Policy.

The Website collects a small amount of anonymous usage information, described in Section 6.

By using the Services, you acknowledge the practices described in this Privacy Policy.

The Apps do not operate a backend collection system and do not intentionally collect or transmit users' personal information to the developer.

The Apps may process the following information locally or exchange it with compatible devices on your local network to provide their functionality.

2.1 Racing Telemetry

The Apps receive and process racing simulation telemetry, which may include:

• Vehicle speed, gear, throttle, and brake inputs.
• Tyre temperatures and other vehicle parameters.
• Lap times, session information, and timing data.
• Vehicle position and other simulation-provided information, which can include the in-game names of other participants in a session.

This information is processed to display dashboard instruments, graphs, timing information, and other supported features. Where applicable, telemetry is exchanged between compatible devices on the user's local network.

2.2 Device Identification Information

During device pairing, the Android App may transmit a randomly generated device identifier and the device's model name to the Desktop App over the local network. This allows the Desktop App to identify and display the device for pairing and connection management.

This information is not transmitted to a Track N Race-operated backend or external analytics service.

2.3 Locally Stored Information

Depending on the features you use, the Apps may store information on your device or computer, including:

• Application preferences and configuration.
• Pairing information and reconnection credentials for paired devices.
• Optional telemetry session recordings.
• Files you choose to create, such as spreadsheet exports or screenshots.
• Diagnostic logs and crash dumps (Desktop App, see Section 4.3).
• Other data necessary for the Apps to function.

This information remains under your control, subject to file system permissions, operating system behavior, and any actions you take to export or share it.

The Android App requests permissions necessary to support its features. Permissions may vary by Android version and application release.

3.1 Camera Access

You may revoke camera permission through Android settings. QR-based pairing will not be available while camera access is denied, although other functionality may remain available.

3.2 Network and Wi-Fi Access

The Android App's network functionality depends on the configuration of the user's network and compatible devices.

3.3 Wake Lock

This permission is used to support the Android App's operation and is not used to collect personal information.

4.1 Local Network

The Desktop App listens for racing simulation telemetry over UDP on the configured port (which defaults to 20777 where applicable). When pairing with the Android App is used, the Desktop App advertises itself on the local network through mDNS/DNS-SD and accepts local WebSocket connections from paired devices. This traffic stays on your local network.

4.2 Update Checks

4.3 Diagnostic Logs and Crash Dumps

To help troubleshoot problems, the Desktop App writes diagnostic logs, and the Electron build also records crash dumps, to its application data folder on your computer. Logs may include the application and operating system versions, platform and architecture, system locale, file paths, and the addresses of your computer's network interfaces.

These files are kept on your computer and are not uploaded automatically. Launch diagnostics are replaced each time the Desktop App starts. They reach the developer only if you choose to send them, for example when reporting an issue.

The Apps may offer an optional session recording feature, which is disabled by default where configured as described in the Apps.

When enabled, telemetry data may be saved in .tnrd files. On Android, these are saved in an application-accessible Documents directory or in a location selected by the user through the Android document picker. On desktop, they are saved in a folder you choose in the Desktop App.

Session recordings are stored locally unless you choose to move, export, or share them. The developer does not receive these recordings through a Track N Race-operated server.

You are responsible for managing exported recordings and any copies stored in other locations or shared with other parties.

6.1 Hosting

The Website is hosted on Cloudflare. To deliver and protect the Website, Cloudflare processes the information that every web request carries, such as your IP address, browser user agent, and the page requested. Cloudflare handles this information under its own privacy policy and may make aggregated traffic statistics available to us. We do not use this information to identify individual visitors.

6.2 Download and Event Counts

The Website counts clicks on its download buttons using Cloudflare Workers Analytics Engine, so that we can see which builds and platforms people use. Each count records only:

• What was clicked: the build (Electron, Native or Minimal) or the release page.
• The platform: the operating system of the chosen download.
• The Website page the click came from.
• Your country, as determined by Cloudflare from the request.
• The current Track N Race release version.
• Whether the click looks automated rather than made by a person, as a short label such as “crawler” or “data centre”. It is worked out when the request arrives, from whether Cloudflare recognises it as a known bot, the browser user agent, the network it comes from and whether it came from a click on the Website. Only the label is stored.

No IP address, cookie, browser user agent, or other identifier is stored with these counts, and they cannot be linked to an individual visitor. Cloudflare retains this data for a limited period, currently three months.

6.3 Downloads

Download links on the Website redirect to the corresponding file on GitHub, which serves the download. GitHub handles that request under its own privacy statement.

6.4 Cookies and Third-Party Content

The Website does not set cookies, does not use browser storage to track visitors, and does not include advertising, third-party analytics, or social media trackers. Its fonts, scripts, and images are served from the Website itself, with one exception: if you choose to show the contact email in Section 14, the Website first loads Cloudflare Turnstile from Cloudflare to check that the request comes from a person. Turnstile processes information about your browser and device to make that check, under Cloudflare's privacy policy, and the Website keeps none of it. Cloudflare may set strictly necessary security cookies if it needs to check a request for abuse.

The Website links to external sites, such as GitHub and Discord. Those sites have their own privacy practices, which this Policy does not cover.

The Apps do not intentionally integrate third-party advertising networks, analytics SDKs, behavioral tracking services, or crash-reporting services.

The Services rely on the following third parties in the limited ways described above:

GitHub

Hosts the source code and release downloads, and answers the Desktop App's update checks.

Cloudflare

Hosts the Website, stores its anonymous download and event counts, and runs the Turnstile check before the contact email is shown.

This Privacy Policy does not claim to govern information collected independently by third-party websites, operating systems, network providers, or other services outside our control.

The developer does not sell, rent, or disclose personal information to third parties. The Apps are designed without a backend collection service, and the Website's download and event counts contain no personal information.

Information may be exchanged between your own compatible devices as necessary for the Apps' functionality. You may also choose to export, transfer, or share recordings, diagnostic files, or other locally stored files yourself.

Information that you voluntarily disclose or transfer outside the Apps may become subject to the privacy practices of the recipient or service involved.

The Apps do not maintain a developer-operated server-side repository of users' telemetry, pairing information, or session recordings.

Locally stored information may be deleted or managed as follows:

Pairings

Use the Android App's "Forget Desktop" feature, or remove the paired device in the Desktop App, where available.

Session recordings

Delete .tnrd files through the Apps, a file manager, or the storage location in which they were saved.

Android App settings and local data

Clear the Android App's data through Android settings or uninstall the Android App, subject to Android's storage behavior and any files exported to other locations.

Desktop App settings, logs and local data

Uninstall the Desktop App and delete its application data folder. Launch diagnostics are also replaced automatically each time the Desktop App starts.

Website counts

Download and event counts are anonymous and cannot be linked to you, so they cannot be retrieved or deleted for an individual. Cloudflare deletes them at the end of its retention period.

Uninstalling an App or clearing its data is not guaranteed to delete files that you previously exported or saved outside the App's managed storage.

The Apps may store credentials used to reconnect paired devices.

In the Android App, the reconnection token is encrypted at rest using AES-GCM with a 256-bit key held in the Android Keystore system. The key never leaves the device, so although the Android App's preferences may be included in Android system backups, a backed-up or copied token cannot be decrypted or used on another device.

In the Desktop App, pairing secrets are protected with the operating system's credential storage where available: Windows Data Protection (DPAPI), the macOS Keychain (Electron build, once you opt in), or the Secret Service keyring on Linux. Where no such storage is available, they are kept in the Desktop App's local settings without this additional encryption.

Security depends on the device, operating system version, operating system integrity, and the actual implementation of the Apps. No method of local storage or electronic communication can be guaranteed to be completely secure under all circumstances.

You should keep your devices and operating systems up to date and protect access to them.

Track N Race does not intentionally collect personal information from children.

The Services are not designed to solicit personal information from children. If you believe personal information has been inadvertently disclosed to the developer in connection with the Services, you may contact us using the details in Section 14.

You can exercise control over the information processed by the Services by:

• Revoking Android App permissions through Android settings.
• Turning off update checks in the Desktop App's settings.
• Choosing whether to enable optional session recording.
• Removing paired devices.
• Deleting locally stored recordings, diagnostic files, and application data.
• Choosing whether to export or share locally stored files.
• Downloading releases directly from GitHub instead of through the Website, if you prefer your download not to be counted.

The availability of specific controls may vary by App version, build, and operating system.

This Privacy Policy may be updated to reflect changes to the Services, their functionality, applicable legal requirements, or their data-handling practices.

When changes are made, the revised policy will be published with an updated "Last Updated" date and documented in the project repository where appropriate.

Your continued use of the Services after an updated policy is published constitutes use of the Services subject to the revised policy, to the extent permitted by applicable law.

For questions, concerns, or requests relating to this Privacy Policy, please contact the project maintainer through the following channels: