Leaderboard participation
New online official-track finishes join anonymously by default. Turn this off before starting. Old records and custom tracks do not enter the board; local saves and optional sync continue as usual.
A separate essential guest cookie keeps your anonymous leaderboard identity, independent of analytics. Email is never public.
Guests can join anonymously without registering. After signing in, results move to your account only when you choose to link this browser’s guest results. Duplicate results on a track become one best. Previously hidden guest results stay hidden until you separately choose to publish them.
Turning off hides existing results and revokes share links. Turning on restores unwithdrawn results, but old share links stay revoked.
Account leaderboard settings can permanently withdraw existing results. Their public pages and links become unavailable, while local records and your future participation choice remain. Also turn participation off if you do not want the next lap submitted.
Revoking the link cannot recall downloaded or forwarded images.
Leaderboard participation →Game data on your device
Language, sound, car colors, tracks and driving progress are stored in your browser. No account is needed to drive. Clearing browser data deletes local content; you can choose to download a backup.
Account and optional cloud sync
Email verification gives access to your account. Your email is not used as your public comment nickname. Signing in to comment does not enable sync. You choose whether to upload progress, car colors and custom tracks; device sound, language and control settings are not uploaded.
Comments and moderation
Nicknames and public comments are visible to visitors. Comments are reviewed before publication, using a configured model and human review where applicable. The model receives only nicknames, comments and related discussion, not emails, IP addresses, tickets or personal driving history.
Support tickets
Only a verified account with the matching email and the support team can view a ticket. We keep the email, content, timestamps, limited device language and browser information, and necessary context such as region and IP address to handle the issue. IP addresses are cleared after 30 days; location may be inaccurate or unknown. Attachments are not currently accepted.
Sign-in verification and third-party services
Image codes and Cloudflare Turnstile help reduce abuse. Sessions use necessary secure cookies. Sending codes or explicitly emailing a reply requires an email service; model moderation uses the service configured in the backend. We do not publish secret keys or verification codes on pages.
Visitor statistics
To improve the experience across regions, languages and browsers, we count successfully served public-page requests. We record request times, connection IP, approximate country and region supplied by Cloudflare, browser language and limited browser headers (user agent, language preferences, browser brands, platform and mobile hints). If Cloudflare provides JA3 or JA4 connection fingerprints, we also retain these optional signals; they do not identify a person. Administrators can view this information.
After optional analytics is accepted, we set a random first-party browser ID for up to 90 days to count public page views, actual driving starts and valid completed laps. Independent browsers are not unique people. When signed in, a separately keyed active-account ID is counted server-side without storing email; browser and account counts are never combined into one people count. Rejecting or withdrawing removes the optional ID and stops site events and Google Analytics. Global Privacy Control or Do Not Track is treated as necessary-only.
Raw IPs, limited browser headers and connection fingerprints are retained for up to 30 days, then hidden from details and cleared. Pseudonymous visitor IDs, coarse location and daily statistics are retained for up to 90 UTC calendar days. The ID can still link requests from the same network and browser during this period; it is not unrelatable anonymous data. Location and bot signals may be missing or inaccurate; a request not verified as a bot is not necessarily human.
To understand traffic sources, we also record the referring domain and source category, and use the user agent and available Cloudflare signals to identify likely automation. These details are retained for up to 90 UTC calendar days. We save only the referring domain and a recognized campaign source category, not referral paths, search terms or full query strings. Sources can be hidden or spoofed; a missing referrer does not necessarily mean a direct visit, and unidentified automation is not proof of a human visitor.
Administrators alone may use a configured password to sign in again within 24 hours of successful admin email verification. A necessary secure cookie binds this permission to the browser, with checks against the connection IP and an actual Cloudflare JA4 connection fingerprint. JA3 changes do not affect permission; missing JA4 falls back to an email code. The server retains only keyed comparison values and verification times for up to 24 hours; short-lived security verification grants last up to five minutes. Password sign-in does not extend this permission. Players continue to use email codes only.
We also use Plausible, hosted at stats.aceailabs.com, to measure page visits, sources, device types and approximate regions to improve the site. Plausible runs separately from the optional Google Analytics described above; declining optional analytics does not disable Plausible.
Advertising and cookies
The homepage, game pages and some guide and reference pages may display advertising provided by Google AdSense. When ads are served, Google and its advertising partners may use cookies, web beacons, IP addresses and other identifiers to collect or receive information about pages visited, devices, browsers and approximate location. They use this information to deliver and measure ads, prevent fraud and, with applicable consent, personalize advertising.
You can manage or delete cookies in your browser and manage personalized advertising preferences in Google’s ad settings. Browser settings may affect features such as sign-in and saving; ad preferences do not turn off all ads. The analytics settings in this site’s footer control optional Google Analytics and this site’s browser statistics, not consent to personalized advertising.
How Google uses data from partner sites · Manage Google ad preferences
With optional analytics enabled, the game reports the screen size and pixel density ranges, input type, automatic resolution level and whether driving was smooth. We use keyed codes for the browser and network to limit repeat votes. Reports expire after seven days and help choose the starting resolution for similar devices.
Deletion and contact
You can delete your own comments and clear local and cloud game data separately. For account or ticket data requests, use the contact page. Deleting cloud data does not automatically delete local copies.