Privacy policy

Who operates Race Engineer

Race Engineer is operated by Jasper Ruan. This policy covers the Race Engineer desktop application, RaceEngineer.app, and the cloud services that connect them.

Information we collect

Account information

When you sign in with Google or Discord, our authentication provider, Supabase, receives an account identifier and the basic profile information your provider makes available, such as your email address, display name, and profile image. Race Engineer requests only the OpenID, email, and profile permissions needed to authenticate you and show your account.

Lap and driving data

If you connect the desktop application to your account, it uploads clean-lap records from Le Mans Ultimate. A record can include:

• lap and sector times, date and time, track, car, class, and session type;
• fuel or virtual energy, tyre compound and wear, and laps since the pit stop;
• track wetness, rain, temperature, and grip; and
• traction-control, ABS, brake-bias, and driver-aid event counts.

Device and local data

The cloud service stores a random device identifier, device label, sync status, and a hash of the device token. The raw device token is returned once and is not stored by the server. On your PC, Race Engineer keeps its configuration, encrypted cloud credential, account display hint, and local lap-history files. These local files remain on the PC unless you remove them.

The website stores your Supabase sign-in session in browser storage. If you untick “Keep me signed in,” it uses tab-scoped session storage instead. Race Engineer does not use advertising cookies.

Desktop product analytics

Product analytics are enabled by default in the desktop application and are sent to Mixpanel under a random per-install identifier, not your OAuth email or display name. Events can include app version, session and track context, car class and setup, driving-aid events, engineer messages, missing app assets, and use of selected launcher controls. This helps diagnose reliability problems and improve the race engineer.

How we use information

• to authenticate you and keep your account secure;
• to sync and display your lap history across your devices;
• to operate, troubleshoot, secure, and improve Race Engineer; and
• to respond to support, privacy, and deletion requests.

We do not sell your information, use it for targeted advertising, or share your lap history with other Race Engineer users.

Google account data

Google account information is used only to sign you in, identify your Race Engineer account, and display basic account details. Race Engineer does not request access to Gmail, Drive, Contacts, Calendar, or other Google product data.

Race Engineer's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Service providers

We use service providers only where needed to run Race Engineer:

• Supabase for authentication, database storage, and cloud functions;
• Cloudflare for website hosting and delivery;
• Google or Discord when you choose that provider to sign in;
• Mixpanel for desktop product analytics; and
• GitHub for software distribution and update checks.

These providers may process technical request data, such as IP addresses and user-agent information, under their own privacy terms.

Storage, security, and retention

Cloud data is protected in transit and by account-based access controls. Database row-level security restricts each signed-in user to their own lap records. Device tokens are stored as hashes on the server, and the desktop credential is protected with Windows data encryption.

Account, device, and lap records are retained while your cloud account is active. Removal records are retained to stop deleted laps from being re-uploaded by another connected PC. Product analytics are retained only as reasonably needed for product improvement and service operation.

No online service can guarantee absolute security, but we limit the data collected and use safeguards appropriate to the service.

Your choices and deletion

• You can sign out of the website without signing out your other devices.
• You can remove individual laps from the desktop launcher's Lap Log.
• You can stop cloud uploads by disconnecting the account in the desktop launcher.
• You can turn off desktop analytics by setting "analytics_enabled": false in %APPDATA%\LMU Race Engineer\config.json and restarting the app.

To request deletion of your cloud account and associated live cloud data, email jasperruannz@gmail.com from the address connected to your account. Account deletion removes the account, cloud laps, removal records, and connected-device records from live systems. Copies may remain in provider backups until the provider's normal backup-retention period expires. Account deletion does not remove the local configuration or lap-history files stored on your PC.

Changes to this policy

We may update this policy when Race Engineer's features or service providers change. The latest version and its update date will remain available on this page.

Contact

For privacy questions or account-deletion help, email jasperruannz@gmail.com.