Last updated and effective: 24 October 2026
ShiftRush: Redline Racer is a mobile game developed by Indeagames. This policy explains how the game uses data, its service providers and your choices. Privacy questions and data requests: indeagamesstudio@gmail.com. Application ID (Android package name and iOS bundle identifier): com.indeagames.shiftrush. Platforms: Android and iOS (iPhone).
Game progress, level stars, coin balance, unlocked vehicle skins, upgrades, best score and distance, daily missions, reward claims, and sound, vibration, notification and language preferences are stored on your device. Purchase transaction identifiers are recorded locally to prevent duplicate delivery. The game does not require a game account. Daily best is the best daily score on your device and is not submitted to a public leaderboard.
Game events and random session identifiers may be kept in a local diagnostic file. Events include level starts, collections, evolutions, distance, store activity and advertising transaction status. Optional gameplay analytics is off by default. When a publisher-configured HTTPS analytics endpoint is available and you enable Analytics in Settings, gameplay events, a random pseudonymous installation identifier, installation date, session identifier, app version and platform are transmitted to that endpoint to measure return play and improve the game. Names, email addresses and precise location are not included in these events. You may switch this off at any time; queued events are then deleted. The custom publisher analytics endpoint is currently unconfigured. This does not disable Firebase Analytics and Crashlytics: those separate services receive permitted data when you opt in, as described below. Contact Indeagames for access or deletion of previously received analytics, including your installation identifier if available. Local files are stored in the application's private area; operating-system backup, transfer and security settings may also apply.
Run checkpoints, your personal ghost replay, mastery progress and cosmetic project progress are also stored locally. Exported backups remain on your device unless you choose to share them through another application; the game has no cloud account or automatic progress upload.
Optional analytics also includes qualified driving days, weekly and friend routes, skill-chain and share-button events, SDK-estimated ad revenue, purchase delivery status, and up to five distinct managed error fingerprints per session. The custom managed-fingerprint event excludes error messages and file paths and may send method names and hashed groups. Firebase Crashlytics reports can separately contain stack traces, exception details and diagnostic logs. These custom managed signals do not capture native crashes or Android ANRs; the separate Firebase Crashlytics integration may collect native crash and ANR diagnostics when enabled with your analytics choice. When you opt in on Android, Google Play Install Referrer may provide campaign/source/creative names; the game does not retain the raw referrer or advertising click identifiers in this feature. A missing source remains unknown.
RevenueCat uses a random installation identifier as its app user identifier when store services are configured. If the publisher enables the currently undeployed financial webhook backend, store-verified purchase notifications may reach that backend independently of optional gameplay analytics to reconcile transactions, gross amounts and refunds. Net payout amounts require settlement records. Campaign costs and first-install attribution supplied by authorized publisher integrations can be joined to consenting gameplay records; the game does not collect an individual player's age.
A result image is generated locally only when you choose Share your run. It can include your score, vehicle, distance, route code, UTC day and app version. The Android share chooser passes this image or a chosen progress backup to the application you select; that application's data policy applies. Local backup import uses the operating system's document picker, reads only your selected JSON file, and asks before replacing progress. A backup is not a verified purchase receipt or a public leaderboard record.
Google Firebase Analytics and Crashlytics are integrated. Optional gameplay analytics and crash-report upload are off by default in the game's settings and native collection configuration. If you enable Analytics in Settings, we send a random installation identifier, app version, game events such as runs, evolutions and missions, and crash diagnostics and game-state context. Firebase can also process device/OS metadata, app instance or installation identifiers, session activity, crash stacks and diagnostic information. Analytics services may infer coarse geographic information from network data; we do not request precise location permission. Stack traces and native diagnostics have a different scope from the game's limited managed-error fingerprints.
Our Firebase configuration disables advertising-ID collection and denies advertising storage, ad user data and ad-personalization consent. These choices do not govern RevenueCat transactions or MAS advertising privacy. You can withdraw gameplay analytics permission in Settings; the game stops further collection/upload through its Firebase integration and resets its Analytics instance data. This is not automatic deletion of already processed provider records. Contact us with your support identifier for access/deletion assistance. Provider retention and the publisher's Analytics/BigQuery configuration govern already exported data; local file rotation and the optional custom backend's 90-day limit do not impose a 90-day limit on Firebase/BigQuery data.
Each SDK below is part of the build. None of them requires a game account.
Purpose: displays products, verifies store purchases, delivers and restores entitlements. Data: a random installation identifier used as the app user identifier, product and transaction identifiers, purchase time and status, store and country, app version. Policy: https://www.revenuecat.com/privacy
Purpose: delivers interstitial and optional rewarded ads, verifies reward completion, measures ads and prevents fraud. Data: device type, operating system, app and SDK versions, IP address and approximate location inferred from it, advertising identifier (on iOS only with your App Tracking Transparency permission), impression and click events, consent choices. Policy: https://policy.yodo1.com/website/en/privacy.html
Purpose: optional gameplay analytics, only after you allow it in Settings. Data: random installation identifier, app version, game events such as runs, merges, shifts and missions, session information. Policy: https://firebase.google.com/support/privacy
Purpose: crash and error diagnostics, collection is off by default and follows your analytics choice. Data: stack traces, device and operating-system metadata, app version, game-state context. Policy: https://firebase.google.com/support/privacy
Purpose: campaign and source names for an install, only if you allow analytics. The raw referrer is not retained. Policy: https://policies.google.com/privacy
Purpose: asks Google Play to show its own rating prompt after a positive moment. The game receives no rating text or account information. Policy: https://policies.google.com/privacy
Purpose: optional local reward and mission reminders scheduled on your device. No data leaves your device through this component.
This version offers in-app purchases. Google Play or Apple App Store/StoreKit and RevenueCat display products, verify payments, deliver entitlements and restore permanent purchases. Information processed may include product and transaction identifiers, purchase time, payment and entitlement status, store and country information, app version, connection information and the application user identifier created by RevenueCat. The game does not request or store your payment-card number or banking password. The store processes payment information under its own rules.
Coin and support packs contain consumable items. Spent coins and supports may not be restored after app data is deleted. Permanent entitlements such as ad removal and the skin pack can be restored using the same store account. Without an in-game account, switching devices may not automatically transfer all local progress.
This version contains ads. Yodo1 MAS and its advertising providers may deliver ads, verify rewarded-ad completion, measure advertising and prevent fraud. These services may process device type, operating system, app and SDK versions, IP address, approximate location inferred from IP, advertising identifiers, impression and click events, and consent preferences. The game does not request precise-location access.
Where applicable, advertising privacy choices and necessary consent are collected through the provider's privacy interface. Consent and operating-system restrictions affect personalized ads. You can use your device's advertising privacy settings to delete or restrict advertising identifiers. The ad-removal product removes interstitial ads; optional rewarded ads remain available only when you choose them. You can decline rewarded-ad offers. On iOS, the App Tracking Transparency prompt asks whether the advertising provider may use your device's advertising identifier to personalize ads and measure ad performance across apps and websites. If you decline, ads may still be shown but are not personalized with that identifier, and gameplay is not affected.
Local reward and mission reminders are optional. Android notification permission is requested through the operating system when required. Disabling reminders in Settings cancels future scheduled reminders; you can also disable notifications in system settings. Notifications are scheduled on your device and do not require an email address or remote notification account. Internet access is used for purchases, ads and store services. Game features do not request camera, microphone, contacts, SMS or precise-location access.
When you email us, we use your email address, message and any screenshots, device information or transaction identifiers you choose to share to handle your request. Do not send card details, passwords or unnecessary personal documents. Support correspondence should be accessed only by people who need it to resolve the request.
Data is used to preserve game progress, apply preferences, provide purchased products, give support, keep the service secure and meet applicable legal obligations. Depending on applicable law, processing relies on performance of the service or purchase contract, legal obligations, legitimate interests in security and support, or your consent where required. Withdrawing consent does not affect processing that was lawful before withdrawal.
When the relevant features are enabled, information may be transmitted to Google Play, Apple App Store, Google Firebase, RevenueCat, Yodo1 MAS and participating advertising providers for their functions. Support messages are processed through email services. Information may also be disclosed where necessary to respond to lawful requests or protect security and legal rights. Indeagames does not sell personal information for data trading. Advertising providers' processing and activities that may legally constitute sale or sharing are subject to their own policies and regional privacy controls.
Providers may process data outside your country. International transfers are subject to provider agreements, safeguards and applicable law. See:
Google / Firebase: https://policies.google.com/privacy Firebase: https://firebase.google.com/support/privacy Apple: https://www.apple.com/legal/privacy/ RevenueCat: https://www.revenuecat.com/privacy Yodo1: https://policy.yodo1.com/website/en/privacy.html
Local progress and transaction records remain until you clear app data or uninstall; operating-system backups and store records may remain separately. The local diagnostic file is rotated at its size limit, replacing the older rotated file. Support correspondence is retained to resolve the issue and necessary follow-up; information no longer needed is deleted or anonymized. Providers retain their transaction records under their own rules; some payment and legal records must be retained for mandatory periods.
You can delete local data using ShiftRush's storage/data-clear option in your device's app settings (Android) or by deleting the app (iOS). This may delete your progress and unspent local coins and supports. For deletion requests or help with provider records, contact indeagamesstudio@gmail.com and, where possible, include the app name and relevant transaction identifier. Reasonable, proportionate identity verification may be necessary. A deletion request is not a refund or cancellation; refunds are handled under store rules.
The publisher’s optional custom telemetry backend is not currently deployed or connected. If it is deployed, hosted gameplay events are automatically deleted after 90 days, with hourly maintenance when that service runs. Pending upload events expire after seven days. Publisher-side deletion removes gameplay and acquisition links and unlinks the installation from financial records; necessary financial transaction records remain subject to legal obligations and provider rules.
Depending on your region's law, you may have rights to access, correct or delete data, restrict or object to processing, data portability, or limit sharing for advertising. Use the email above to make a request. Requests are assessed under applicable deadlines and exceptions. Rights under Turkey's KVKK and the right to contact its competent authority, and rights to complain to the relevant data-protection authority elsewhere, remain available.
ShiftRush is intended for audiences aged 13 and above and is not marketed as an educational or preschool game. A target-age declaration is not proof of an individual user’s age. Advertising providers may use age/consent interfaces and regional protections. On iOS, tracking permission is requested by the enabled advertising provider for cross-app ad personalization/measurement; declining permission does not prevent gameplay. Notification permission is requested only after the game’s explanation and your choice, not automatically at launch.
The game does not collect age, name or contact information through its own account system. Applicable age and consent rules and platform restrictions govern advertising and store transactions involving children. Contact indeagamesstudio@gmail.com if you believe a child's personal information was processed improperly. Parents can use device purchase and advertising privacy controls. Age ratings and target-audience information appear in the store listing.
Measures include private app storage, providers using HTTPS, access restrictions and verified store transactions. No system provides absolute security. This policy is updated when significant data practices change; in-app notice or renewed consent is provided where required. The current policy is accessible from Settings > Privacy Policy and the policy URL in the store listing.
Data controller / developer: Indeagames Contact: indeagamesstudio@gmail.com