Privacy

Roadster City Drive uses Google sign-in to identify your account and check access. The access service receives your Google account identifier, email address and name. Your Google sign-in credential is sent to the access service for verification, not to multiplayer peers.

We store account-linked trial start and expiry information, purchase and refund records, relevant checkout and payment identifiers, and access status. These records support access checks, purchase restoration, refund handling and prevention of repeated trials. Stripe processes payments; the game does not receive your payment-card number.

Your browser stores preferences, progress, device-local personal records, cached account and access information and, when applicable, a pending purchase-claim identifier. Clearing browser storage can remove local progress and records. Local records are not verified public rankings.

Optional multiplayer shares your chosen display name and game state, including movement and flight, with participants. PeerJS provides signaling and connection services; network connection information is used to connect participants. Admission uses short-lived opaque tickets and an in-memory proof key. Peers do not receive your Google credential or Google account identifier. Sharing a run or room link happens only when you use the sharing or copy controls.

Cloudflare hosts the website and access service. We use Cloudflare Web Analytics to measure page views, visits, referring sites and page performance. The analytics beacon does not use cookies or browser storage. Its current implementation removes query strings and fragments from page and referrer URLs before sending those fields. We do not send account identifiers, email addresses, purchase identifiers or custom gameplay events to Web Analytics. Analytics totals include our own testing and do not establish unique players or completed purchases. Google supplies sign-in and fonts, and unpkg supplies the PeerJS library. Map searches and network map loading may contact OpenStreetMap Nominatim and Overpass providers, including overpass-api.de and Overpass private.coffee. These providers receive the requests and connection information needed to deliver their services. Their handling of data is also governed by their own policies.

The current software has no scheduled deletion of durable trial, purchase or refund records. Webhook duplicate-event receipts expire after approximately 400 days. Browser-local data remains until cleared or removed by the browser. These are software behaviors, not a promise that all copies or provider records are erased on a fixed schedule. There is no automatic or self-service account-deletion feature.

For privacy questions, access requests or deletion requests, contact [email protected]. Requests are reviewed manually. We may need to verify account ownership before making changes. We review the affected records and any applicable retention requirements before deciding what can be removed or minimized; submitting a request does not automatically delete records. Review must account for purchase restoration, consumed trials and refunded purchases. Support messages contain the information you choose to send. Please do not send passwords, sign-in credentials or payment-card details.