The short version
Rocket Wheels uses Firebase to give your game a player identity, store runs and keep the global leaderboard fair. Your chosen player name, best distance, and the car and colour used for that record are public. Your full run history is not public.
Supported versions can show Google AdMob ads when advertising is enabled. The game does not use Google Analytics for Firebase or Firebase Crashlytics.
Advertising and your choices
Google AdMob may show an ad when you return to the garage after a run, or offer an optional rewarded video to continue after a crash.
Google’s Mobile Ads SDK may collect and share your IP address, device or advertising identifiers, interactions, and diagnostic information for ad delivery, measurement, and fraud prevention. Your IP address may be used to estimate your general location. For a rewarded ad, the game supplies Google with your Firebase player ID and a run verification token so our server can verify the reward.
Where applicable, you can manage ad consent in the consent prompt or under Ad Privacy Choices in the garage settings. See how Google uses information from apps that use its services.
What the game collects
The game does not request your contacts, precise location, photos or microphone.
How Firebase is used
Google Firebase Authentication provides the anonymous player ID. Cloud Firestore stores profiles, run history and leaderboard records. Cloud Functions validates submissions and returns rankings. App Check with Play Integrity supports Android app/device integrity checks where available.
Firebase and its infrastructure process technical data such as IP addresses, SDK/app information, request logs and integrity/attestation material to deliver and secure these services. This technical processing is separate from advertising or gameplay analytics. See Firebase’s privacy information and its Android data disclosures .
Data may be processed on Google infrastructure outside your country. Access to private profiles and histories is restricted to the associated player and authorised service operators. Authenticated server functions validate score changes. No security system can guarantee complete protection.
What other players can see
The leaderboard displays your chosen name, rank, best distance and the car/colour used for that score. Leaderboard records and their identifiers can be read publicly. Choose a nickname and avoid putting personal contact details in it.
Your private profile and individual run history are not part of the public leaderboard. We retain player records to provide history, ranking and abuse prevention until they are deleted or no longer needed. Service providers may separately retain technical logs under their own retention policies.
Delete your account and player data
In the game, open Garage → Settings, choose Delete account & data, then confirm with Delete permanently. This requires an internet connection and cannot be undone.
The server removes your player profile and name, public leaderboard entry, stored run history and Firebase anonymous authentication account. Once the server confirms deletion, the game clears your local best score, queued and active runs, and stored leaderboard identity. Your selected car, paint, audio and tutorial settings stay on this device. Choosing a new player name afterwards creates a new anonymous identity; it does not restore the deleted records.
If deletion cannot be confirmed, score syncing stays paused. Reconnect and choose Continue deletion in Settings to retry, or contact support. The game does not report success until server deletion and local cleanup have been confirmed.
If you cannot use the in-app option, send a data deletion request on our Support page. Include your player name, approximate best score and device details. If available, use Copy player ID for support in Settings and include that ID. We may need additional information to verify the correct profile before acting. You can also contact us for access or correction requests. Never send passwords or sign-in tokens.
Uninstalling or clearing the game removes local data but does not itself delete server records. It can also remove access to your anonymous identity. Contact us before uninstalling when possible; recovery or verification without the original identity may be limited.
Temporary deletion safeguard
A private temporary deletion marker prevents previously issued sign-in tokens or delayed score submissions from recreating your records while deletion is processed. While work is pending, the marker contains your user ID, a pending status and a start time so the server can retry unfinished deletion.
After successful server deletion, the marker contains only a SHA-256 hash of your user ID as its key, a completed status and an expiry time. It no longer contains your raw user ID, player name, scores or run history. This security record is not public or used for gameplay rankings.
The completed marker expires two hours after server deletion finishes and is removed by cleanup scheduled every hour. Pending work is retried by the same cleanup process. A marker can remain longer if deletion or cleanup is delayed or fails. Firebase service logs and backups follow the provider’s separate retention policies; deleting your player records does not immediately remove those copies.
This website and support messages
This website adds no analytics trackers or advertising cookies. Our hosting provider may process connection logs and cookies needed to serve or control access to the site. The download route checks your browser’s device information locally to choose a store; we do not save that check.
The support form prepares an email in your own email app. It does not silently upload a report or automatically send mail. If you send it, we receive your email address and the details you include, and use them to answer the request. Do not send passwords or payment details.
A parent or guardian can contact support about a child’s data. Changes to this policy will appear here with an updated date.
Need a hand?
Contact Rocket Wheels at databyze@gmail.com.