Draft last updated October 7, 2026
1. What Mileage Sync handles
Mileage Sync may process account information such as your email address and username, plus driving statistics including car names, mileage, laps, shifts, fuel use, session information, and app health information needed to operate and improve the service.
2. Local-first records
Detailed race history is designed to remain on your computer unless you choose to synchronize it to a connected service such as Google Sheets or private cloud backup. Signed-in desktop accounts automatically publish community summaries as described below.
3. Community leaderboard
Community period activity is included with every signed-in desktop account. Dated car and track summaries are published automatically under your public username. There is no separate period opt-in or opt-out switch. Lifetime Car Totals remain a separate setting. Your account email is not displayed on the public leaderboard.
Automatic period publishing also publishes observed iRating and Safety Rating start/end values, license class, racing category, net changes, and observation coverage dates and times. Summaries include distance, ending odometer, laps, shifts, sessions, track time, overtakes, braking/coasting coverage and distance, and fuel. Raw Race Log rows, session IDs, notes, email, credentials and local files are excluded. Ratings are simulator observations, not official race results. Older desktop versions must be updated before they can publish automatically.
4. Account and service providers
Supabase supports account identity and session services. The public website and leaderboard use hosting and data services required to deliver those features. If you connect Google Sheets, Google’s own terms and privacy practices also apply to that connection.
5. Diagnostics and beta improvement
If you allow website analytics, Mileage Sync records sanitized routes, active engagement time, scroll milestones, important interactions, coarse device and browser information, campaign attribution, page performance, and sanitized errors. A random identifier counts visitors and sessions; the account ID is associated after sign-in. The hosting edge may add a coarse country or region code for aggregate reporting without giving Mileage Sync your IP address. Passwords, tokens, complete form values, full IP addresses, precise locations, and browser fingerprints are not stored.
6. Your choices
Website analytics does not start until you choose Allow. Choosing Decline, enabling Global Privacy Control, or enabling Do Not Track prevents collection. You can also choose whether to use optional lifetime totals and connected exports and may request access, correction, or deletion of hosted account data. Signed-in users can delete account-linked website analytics directly from the Account page.
7. Security and retention
Website analytics is available only to server-verified administrators and raw records are scheduled for deletion after 730 days. Small geographic cohorts are suppressed. Reasonable safeguards are used, but no system is perfectly secure; retention will be reviewed before general release.
8. Changes and contact
This draft may change frequently during beta. Material changes should be communicated through the website or product. A formal privacy contact method will be added before general release.