Come on! Racing (home-screen name: Rush)
Last updated: October 22, 2026
This Privacy Policy explains how Come on! Racing ("we," "us," or "this App") collects, uses, and protects your information when you use our Android application. On the device home screen, the App may appear as Rush.
Summary: This App is a local, offline-capable arcade racing game. Game progress stays on your device. We do not require registration, do not show in-app ads, and do not ask for location. We use Firebase Analytics and Firebase Crashlytics to understand usage and improve stability.
Come on! Racing is primarily a local arcade racing game. Core gameplay, garage progress, settings, and records are processed on your device. It does not require you to register or sign in, and it does not upload your game save to our servers for an account system. Specifically:
If you use the system "Share" feature to share a race result, or open the system Play Store page to rate the App, the data flow is governed by the system and the destination app's policies. This App accesses such features only to the extent needed to perform the action you chose.
[Important] About location: This App does not request location permission and does not use GPS, approximate location, or background location for gameplay.
This App does not integrate advertising SDKs for showing ads in the game (such as AdMob banners or rewarded video), and we do not use the Advertising ID to show personalized ads in the App. We do not operate a user-account backend or cloud service for storing users' personal account data. This App uses the following third-party services, which may collect certain information:
We use Firebase Analytics to understand how users use this App and to improve the experience. Firebase Analytics may collect:
Important: Firebase Analytics is designed primarily for product and aggregated analysis. For more information, see Google's documentation: https://firebase.google.com/support/privacy
We use Firebase Crashlytics to automatically detect and report app crashes and errors so we can fix issues and improve stability. Crashlytics may collect:
Important: Crashlytics is used primarily for technical diagnosis and app improvement; Crashlytics does not collect your full local save file, garage inventory, or personal notes as content. For more information, see Google's documentation: https://firebase.google.com/support/privacy
The Firebase-related data above is processed under Google's privacy policy. For more information, see: https://policies.google.com/privacy
General note: Data collected through Firebase is used primarily for analytics and app improvement. Google processes such data in accordance with its privacy policy. We do not upload your full local save, garage details, or settings file through Firebase.
Important: We do not provide a user account system, and we do not operate our own servers for storing users' personal data. Data processed by Firebase is subject to Google's data retention and security practices; retention periods follow Google's rules.
No weather, maps, social login, or cloud catalog: This App does not contact weather providers, map providers, or social networks for gameplay. Online network access is used for Firebase Analytics / Crashlytics and for system actions you start (such as opening the Play Store rating page or using Share).
To provide the corresponding features, this App declares or may use the following permissions (subject to your device system and the final merged application manifest):
| Permission | Purpose |
|---|---|
android.permission.INTERNET |
Used for Firebase Analytics / Crashlytics network transmission, and for system actions that require a network connection when you choose them (for example, opening the Play Store). Not used to provide an account, cloud backup of your garage, or an in-app advertising network. |
android.permission.ACCESS_NETWORK_STATE |
Merged via libraries such as Google Play services / Firebase. Used to check network connectivity before SDK operations and to avoid unnecessary failed requests. |
android.permission.VIBRATE |
Used for optional haptic / vibration feedback during races (for example, collisions and coin pickups) when vibration is enabled in settings. |
android.permission.WAKE_LOCK |
Merged via Google / Firebase libraries. Used by system components as needed for short background work windows related to those libraries. This App does not use wake locks for continuous tracking. |
com.google.android.gms.permission.AD_IDand related AdServices attribution / ad-id permissions (merged via Google libraries) |
Present because Firebase / Google Play services libraries may access the Advertising ID for analytics measurement. This App does not show personalized ads and does not use an in-app ad network. You may limit ad tracking in system settings where the OS provides that control. |
[Sensitive-access note]: This App does not declare location, microphone, camera, contacts, SMS, phone, or storage-access permissions for gameplay. Racing and progress saving work with on-device storage only.
Advertising ID: Although AD_ID-related permissions may appear in the merged package because of Firebase / Google libraries, we do not use them to display ads inside Come on! Racing.
Note: This App requests only the permissions needed for its features or brought in by its libraries. You may manage some related controls in system settings; changes may affect analytics measurement or vibration feedback.
This App provides endless-road and timed-sprint racing, car garage upgrades, parts (including a wing), items, daily missions, achievements, check-in rewards, a local weekly cup, and local ghost cars based on your previous runs. These features use data already stored on your device.
This App does not provide cloud sync, online multiplayer, leaderboards with other players' accounts, or personalized advertising recommendations. The App uses Firebase Analytics and Crashlytics as described in Section 1.2.
We use related information only for the following purposes:
We do not sell, trade, rent, or share personal information for advertising purposes. Technical data may be transmitted to Google Firebase solely for analytics and crash reporting as described in this Policy. Data processing or disclosure may occur only in the following circumstances:
We take the security of your information seriously. Data related to this App's core racing and management features is processed primarily on your device. When Firebase Analytics / Crashlytics transmissions occur, network transmission typically uses secure protocols such as HTTPS/TLS. We will not sell your data or use it in ways inconsistent with this Policy. We do not operate a user-account backend or cloud service for storing your garage or race records.
Please note: if Android Auto Backup is enabled on your device, some app data may be included in device backups according to system rules. That visibility results from your device / account backup settings, not from upload by us to a separate game-account service.
This App is not directed to children under the age of 13, and we do not knowingly collect personal information from children under 13. If you believe there is a related issue, please contact us.
We may update this Privacy Policy from time to time. The updated version will be posted on this page (or the same in-app / store link), and the "Last updated" date will be revised. For material changes, we will provide notice in an appropriate manner as required by applicable law. We encourage you to review this Policy periodically.
To the extent permitted by applicable law, you may have the right to know about, access, correct, delete, or restrict processing of information related to you. Because this App is primarily local, you can usually manage local data through in-app features such as resetting all data in Settings, or by clearing app storage / uninstalling the app in system settings. You may uninstall this App at any time to stop using it; after uninstall, data in the app's private directory is deleted according to system rules, but device backups may retain copies until expired or deleted by you or the backup provider.
Because we do not store your garage or race records on our servers as a cloud account, there is no server-side request for access, correction, or deletion of that local content from "our cloud." For information processed by Google Firebase, please see Google's privacy policy.
If you have any questions, comments, or suggestions about this Privacy Policy or our data practices, please contact us at:
Email: doesantalya@outlook.com