Indea Games (“we”, “us”, “our”) is an independent mobile game studio. This privacy policy covers the mobile game ShiftRush: 2048 Racer (package name com.indeagames.shiftrush) on Android and iOS. It explains what data is processed when you play, why, and the choices you have. It applies only to this app — our other games have their own policies at indeagames.com/privacy.
ShiftRush: 2048 Racer does not require a game account and does not ask for your name, email address or contact details. Your progress and settings are stored on your device. The third-party services built into the game do, however, collect some technical data from your device — such as your advertising ID, IP address and approximate location when advertising is enabled, purchase and device information to complete purchases, and, only if you turn on Analytics in Settings, gameplay events and crash reports tied to a random installation identifier. Some of that data counts as personal data under laws such as the GDPR, and the rest of this policy explains how it is handled.
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.
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. Local files are stored in the application's private area; operating-system backup, transfer and security settings may also apply.
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. The file is rotated at its size limit.
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 us for access or deletion of previously received analytics, including your installation identifier if available.
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. These custom managed signals do not capture native crashes or Android ANRs. When you opt in on Android, Google Play Install Referrer may provide campaign, source and 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.
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 and operating-system metadata, app instance or installation identifiers, session activity, crash stacks and diagnostic information. Firebase Crashlytics reports can contain stack traces, exception details and diagnostic logs, and the integration may collect native crash and ANR diagnostics when enabled with your analytics choice. Analytics services may infer coarse geographic information from network data; we do not request precise location permission.
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 the advertising privacy of Yodo1 MAS. You can withdraw gameplay analytics permission in Settings; the game stops further collection and 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 or deletion assistance. Provider retention and our Analytics and BigQuery configuration govern already exported data; the 90-day limit of the optional custom backend does not apply to Firebase or BigQuery data.
In versions with purchases enabled, 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. Catalog-preview versions do not process payments or grant purchases from preview buttons.
In versions with ads enabled, 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. When the advertising service is disabled in a preview version, game code does not initialize Yodo1 ads. On iOS, tracking permission is requested by the enabled advertising provider for cross-app ad personalization and measurement; declining permission does not prevent gameplay.
Local reward and mission reminders are optional. Android notification permission is requested through the operating system when required, only after the game's explanation and your choice, not automatically at launch. 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.
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.
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.
You can delete local data using ShiftRush's storage and data-clear option in Android settings. 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. 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 and consent interfaces and regional protections. 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. 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. The current policy is accessible from Settings > Privacy Policy and the policy URL in the store listing.
ShiftRush: 2048 Racer is free to play. In versions with ads enabled it is funded by ads (including optional rewarded ads), delivered through the Yodo1 MAS mediation platform, and by optional in-app purchases handled by RevenueCat, Google Play and the Apple App Store. To do this, the app includes the third-party SDKs listed below. Each SDK collects the data shown on its card directly from your device, which means that data is shared with the vendor named on the card, and each vendor processes it under its own privacy policy, linked there. The same disclosures are reflected in the app’s Google Play Data Safety section and Apple App Privacy label. Mediation means Yodo1 passes each ad request on to a number of partner ad networks and serves whichever one fills it, so the data on the Yodo1 card is also received by the network that ultimately shows you the ad. Yodo1 maintains the current list of those partners, and each of them processes data under its own privacy policy; the Yodo1 policy linked below is the authoritative starting point for that list.
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Data this SDK may collect:
Ads in ShiftRush: 2048 Racer may be personalized (chosen using your advertising ID and inferred interests) or non-personalized (chosen only from context, such as the game you are playing and your approximate region). Where the law requires it — for example under the GDPR — personalized ads are only shown with your consent, and declining consent means you see non-personalized ads instead; the game itself stays fully playable either way.
Your device’s advertising ID is a resettable identifier that ad networks use for frequency capping, fraud prevention, measurement and personalization (with your consent where the law requires it). You are in control of it:
We use Firebase Analytics and Firebase Crashlytics to understand how the game is played — for example which levels are too hard, where crashes happen, and which features players enjoy. This data is tied to a device or app instance, not to your real-world identity: we see counts and patterns, never your name or contact details, and we use it only to improve the game. Details for each tool are in section 3.
ShiftRush: 2048 Racer requests only the permissions it needs to work:
ShiftRush: 2048 Racer is not directed at children under 13 (or the equivalent minimum age in your country), and we do not knowingly collect personal data from them. If you believe a child has provided us personal information, contact us at indeagamesstudio@gmail.com and we will take steps to delete it.
Depending on where you live, you may have legal rights over your personal data, including the following.
If you are in the EU/EEA or UK (GDPR): you have the right to access, rectify, erase and receive a portable copy of your personal data, to restrict or object to its processing, and to withdraw consent at any time without affecting the lawfulness of prior processing. Our legal bases are your consent (personalized advertising and optional gameplay analytics, where the law requires consent), performance of our contract with you (processing and restoring your in-app purchases), our legitimate interests (non-personalized ads, analytics, crash reporting and fraud prevention) and compliance with legal obligations. You also have the right to lodge a complaint with your local supervisory authority.
If you are a California resident (CCPA/CPRA): you have the right to know what personal information is collected about you, to request its deletion, to correct it, and to opt out of the “sale” or “sharing” of personal information. We do not sell your personal information for money. Showing personalized ads can, however, count as “sharing” (and in some cases a “sale”) as the CPRA defines those terms broadly; you can opt out by limiting ad tracking on your device (see section 4) or by using the vendor opt-out links in section 3. We will never discriminate against you for exercising these rights.
Because most data described in this policy is collected directly by the SDK vendors in section 3, requests about that data are fastest through the vendor’s own privacy page. For anything else — or if you would like our help — email us at indeagamesstudio@gmail.com and we will respond within the time required by law.
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. Data collected by third-party SDKs is retained by those vendors according to their own published retention periods, as described in their privacy policies. The SDK vendors protect data with industry-standard safeguards such as encryption in transit, but no method of transmission or storage is completely secure, and we cannot guarantee absolute security.
The SDK vendors listed in section 3 operate globally, so data they collect may be processed in the United States and other countries outside your own. Where data leaves the EU/EEA or UK, the vendors rely on recognized safeguards such as the EU Standard Contractual Clauses or an adequacy decision (for example the EU–U.S. Data Privacy Framework, where the vendor is certified). Details are in each vendor’s privacy policy.
If we add an SDK, remove one, or change how data is handled, we will update this page and change the effective date at the top; where required, we will also give additional notice. The current version always lives at indeagames.com/privacy/shiftrush.
Questions, concerns, or a privacy request? We are a small team and we actually read our email: indeagamesstudio@gmail.com.