Privacy policy
Policy revision: 7 November 2026 · Rush Out 1.0.5 and 1.0.6 for iOS and Android, earlier versions and these pages
Current version: Rush Out 1.0.5 on iOS and Android
Rush Out 1.0.5 is the version currently published on the App Store and on Google Play. In 1.0.5:
- Age: the game does not ask for your age and has no age setting. An age answer saved by an earlier version keeps its protections (see Age and ad settings).
- Ads: Google AdMob is the only mediation platform, with Google’s UMP for privacy choices and ironSource Ads bidding through Google’s adapter. Ads are non-personalized for every player. Apple App Tracking Transparency and the IDFA are not used.
- Privacy choices: the first-launch screen offers “Accept all” and “Reject optional”, and each optional purpose can be changed in Settings → Privacy (see Optional privacy choices).
- Purchases: Apple handles iOS payments and Google Play handles Android payments. Unity IAP’s optional Insights events and the client purchase-count reports are turned off.
Text below marked as earlier, historical or for a named older build does not describe 1.0.5. Items under Prepared server updates are not presented as active in 1.0.5.
Rush Out 1.0.6: advertising changes
This section applies to Rush Out 1.0.6 on iOS and Android once that version is published and installed. Until then, the 1.0.5 text on this page applies. Everything else on this page that describes 1.0.5 also applies to 1.0.6.
- Ads: Unity LevelPlay runs a single auction for each ad opportunity. Google AdMob, Unity Ads, ironSource Ads and Yandex Ads can bid in it. Google AdMob is also used directly when the auction returns no ad. Google’s UMP provides privacy choices and starts before LevelPlay. How often ads appear does not change.
- Signals: Before LevelPlay starts, the game requests non-personalized ads by sending every ad network a no-personalized-advertising consent value and a US “do not sell or share” signal, and limits Google ad content to the G rating. For devices with an earlier under-18 age declaration it also sends child-directed signals to LevelPlay, Google, Unity Ads and Yandex, and a device-identifier opt-out signal. The game does not pass a player ID to LevelPlay. These are configuration settings, not a claim that the services process no data.
- Tracking: Rush Out does not request Apple App Tracking Transparency (ATT) authorization, so on iOS the IDFA is not made available to the game or its ad SDKs. The Yandex Mobile Ads SDK includes AppMetrica components. Their iOS privacy file lists a tracking function, which according to Yandex’s documentation operates only when the IDFA is available.
- Data: When ads are allowed, Unity (LevelPlay, Unity Ads and ironSource Ads), Google and Yandex may process device and app information (such as device model, operating system, language, app version and, on Android, the advertising ID or app-set ID permitted by Android), IP address and IP-derived general location, ad requests, views, clicks and other ad interactions, and crash, performance and diagnostic data, for ad delivery, frequency capping, measurement, fraud prevention and service operation. AppMetrica components may also process technical device information and in-app purchase events for analytics. These providers may process data in other countries, including outside your own.
See Yandex’s privacy policy, the Yandex Ads disclosures for iOS and Android, and AppMetrica’s disclosures for iOS and Android. The Google and Unity links are listed under Advertising and consent.
Optional privacy choices in 1.0.5
This screen is part of the published 1.0.5 client on iOS and Android; earlier installed versions do not include it. The first-launch screen states plainly which data is required for the game to work: account and saves, purchases, security, diagnostics and the data needed to show non-personalized ads. It then offers two actions: “Accept all” and “Reject optional”. The optional purposes are gameplay analytics, promotional notifications and purchase-history-based recommendations. If you reject them, the game and ads continue normally and those purposes stay off. There is no in-game switch for advertising, because ads are non-personalized for everyone. You can change each optional purpose later in Settings → Privacy. Gameplay analytics and purchase-history recommendations stay off until a compatible server acknowledges your current choice; until then the choice is kept on the device. Reminders handled on the device follow your saved choice directly. The game does not ask for your age; devices with an earlier under-18 age declaration keep every optional purpose off (see Age and ad settings).
Refusing or withdrawing stops new optional collection and clears the local analytics queue. Offline withdrawal takes effect on the device immediately; server changes wait for connectivity. A notification already handed to a provider cannot be recalled. Native SDK background traffic after withdrawal has not yet been verified by packet capture.
Personalized offers use a separate permission to check whether purchase history exists and mark an available existing booster pack as recommended. This is a simple rule, not a measured likelihood of buying. Refusal leaves the general catalogue and prices unchanged and the recommendation code does not read purchase history. No new price, discount or automatic purchase is created.
The optional Unity IAP purchase/session Insights emitters and the separate client purchase-count reporting queue are disabled in 1.0.5. Purchase delivery, receipts, refunds, ownership checks, account security and progress saving remain necessary operations. Store-provided aggregate downloads and revenue reports remain available independently; client platform counts are not store download totals. Earlier versions and data already processed by providers retain the historical behavior described below.
Server-side handling in 1.0.5
The items below run on our Netcup-hosted service. The game keeps working if that service cannot be reached.
- Server handling of privacy choices: with a compatible server, a received withdrawal deletes that installation’s raw analytics events, removes the push token and cancels pending promotional sends. Raw gameplay events are retained for up to 30 days by the server cleanup job; consent revisions and operational records have separate retention.
- Apple purchase account link: the 1.0.5 iOS client can ask our Netcup-hosted service for an account token before an Apple purchase, then send the signed purchase record so the purchase is tied to your game account. If the token cannot be obtained, for example because the service is unavailable, the purchase continues and is delivered locally on the device.
Who to contact
For questions about Rush Out or requests concerning your information, contact the game’s developer, MehmetVI, at support.rushout@gmail.com.
If you email us, we use your email address, message and any diagnostics you choose to include to respond, investigate the issue or handle your privacy request. We keep this correspondence only as needed for those purposes and applicable legal obligations.
For support and testing follow-up, we also keep a private contact index on the operator’s computer and a private Netcup-hosted server. It contains the sender address and name supplied in the message header, message/thread identifiers, dates and source references. The index contains no message bodies, does not infer a player ID and is not a marketing mailing list. The game does not ask for an email address for this index or obtain one from Apple or Game Center. It does not read your device address book. Deleting an index entry removes its active copies after synchronization; a hashed address is retained to prevent old imports from recreating it. This does not delete the original support mailbox message or existing backups. Support correspondence and index deletion can be requested through the address above.
Game progress and settings
On iOS, the game stores progress, coins, owned vehicle appearances, boosters, settings and pending purchase identifiers locally on your device. It also keeps local competitive records and profile information needed for its Game Center features. These records let the game resume, preserve purchases and avoid granting a purchase twice. Device backups may contain local app data depending on your Apple settings.
A limited recent-event list is held in memory for game diagnostics. The current implementation does not send that event list to a separate analytics service operated by the developer.
Game Center
If you choose to sign in to Game Center, Apple processes your Game Center account information. Rush Out can use the identity and display name returned by Apple for your optional Game Center profile. Switch City keeps campaign progress and daily results on your device. In versions with online career and league services enabled, guest and linked players are registered automatically after choosing or accepting a game name when the service is reachable. Eligible puzzle actions and verified results are then processed by our online services, as described below; there is no separate league opt-in step. You can manage Game Center through your device’s settings. See Apple’s privacy information.
Online presence and support gifts
While the game is in the foreground and online, supported versions periodically send the service player ID, client version and gift acknowledgment to the configured service, normally about once a minute. We store the latest contact time with the player record and use it to show recent activity in a private operator panel and reliably deliver support gifts. Gift sequence, cumulative amounts and acknowledgment records prevent duplicate delivery. This continues during gameplay, subject to connection and account checks; it is separate from the automatic career/league registration described below. A recent heartbeat indicates recent contact, not proof that a person is still playing. Older clients and migration snapshots may not provide current presence information.
Player profile, public ID and chosen name
In versions with player identity and presence synchronization enabled, the game can automatically create or retrieve a stable guest or linked player ID while it is open and online, even if you do not open the profile. Unity Authentication verifies the service account. Depending on the version and migration stage, identity and game records are processed by Unity Cloud Code and Cloud Save or our private servers hosted by Netcup. A guest uses a separate anonymous service account; a linked player uses the authenticated account. “Anonymous” means that you do not need to provide a real name or email for that guest account; the service still keeps an account identifier and its public-ID binding. Identity lookup by itself does not upload puzzle actions. Separately, automatic career/league synchronization can send your chosen or generated name, avatar, eligible gameplay actions and results, and existing career-star progress where migration applies. Your guest ID may not be recoverable after reinstalling the app. The public ID is a label you may copy and share, not a password.
Chosen guest and linked game names are saved locally. When automatic career/league synchronization connects, we also store the chosen name, a normalized name reservation, change count, revision and pending/completed change-operation records on the service to enforce unique names and settle any in-game coin charge once. Guest and linked names and league statistics may be visible to other participants. You do not need to use your real name. Changing a name does not remove earlier operation records needed to recover an interrupted change or prevent duplicate charges.
You can request deletion of a guest cloud identity from Profile → Guest account, or manage a linked account through its league/account controls. Guest deletion removes that guest cloud account and public-ID binding after completion is verified; local campaign progress and a separate linked account are preserved. A request can remain pending during processing. The app keeps a private receipt to check deletion status; its server-side verification record is valid for 30 days. Account data otherwise remains until deletion is completed. These controls do not delete records independently controlled by Apple, Google or Unity’s separate advertising or purchasing services. You can also contact support for an access, correction or deletion request.
Purchases
On iOS, Apple processes in-app payments. The game receives product and transaction identifiers and signed purchase records to deliver purchased items, restore eligible purchases and avoid granting the same purchase twice. The developer does not receive your payment card details.
Rush Out uses Unity In-App Purchasing. 1.0.5 turns off this SDK’s optional purchase and session Insights events; the rest of this paragraph describes earlier versions. In addition to handling purchases, this SDK sends purchase activity to Unity for purchase analytics and service operation. This can include product and transaction identifiers, prices and quantities, signed purchase records, platform identifiers such as IDFV on Apple devices and installation/session identifiers on Android, and technical information such as device model, operating system, language, locale and installation time. These SDK events are separate from the game’s local recent-event list. See Unity’s player privacy policy and Unity IAP privacy overview. Apple and Unity may retain purchase-related records after you remove the game.
Special vehicle purchase verification
Versions with special vehicle synchronization send Apple-signed purchase or revocation records to our Netcup-hosted service using the authenticated game account. The service stores a transaction-derived hash, account owner, product identifier, purchase time and revocation status to verify vehicle ownership and prevent duplicate or conflicting claims. It does not store the raw signed record in this entitlement table. This account-linked ownership record is separate from developer purchase counts.
A protected local queue keeps pending signed records and their native account binding until delivery. Unlike the separate purchase-count queue, this queue has no 14-day expiry. From the AdMob-only 1.0.3 build 90 candidate onward, including 1.0.5, verified completion of account deletion removes pending records bound to that account from the local queue and memory. If local cleanup fails, the deletion recovery marker is retained so cleanup can be retried. Other accounts’ records and records not yet bound to an account are not assigned to the deleted account. Subsequent verified purchase callbacks for that deleted native account do not recreate its cloud-delivery copy; local StoreKit restoration and verified revocation still apply. Server ownership records are removed with the deleted wallet. This does not erase Apple’s purchase history or remove local purchase rights merely because a cloud account was deleted. Earlier builds, including build 89, do not include this local-queue cleanup improvement.
Developer purchase counts — earlier versions
1.0.5 does not send these client reports. In earlier versions with purchase reporting enabled, the app sends Apple-signed transaction data to our private Netcup-hosted service for signature and product verification. A small protected queue on your device retries pending reports while the app runs; queued reports expire after 14 days when the queue is checked, and the queue is excluded from device backups. The request uses the game service account for access control, but the stored observation has no player/account field. We retain a transaction-derived hash, product identifier, purchase time, app identifier and Production/Sandbox environment under a 90-day window from purchase, with daily cleanup. The signed payload, original transaction ID and payment card details are not stored in this observation table. Daily product counts are retained without transaction or player identifiers after the detailed record expires. These records support purchase reporting and duplicate counting prevention; they do not assign purchases to players, grant items, provide prices or revenue, or establish complete purchase/refund history. Hashed transaction records are not described as anonymous. Other StoreKit and Unity purchase processing described above remains separate.
Android identity, purchases and league
On Android, Google Play Games and Unity Authentication identify an online account. We process the service player identifier, Play Games identifier and display name. Campaign puzzles remain playable offline; supported online versions automatically register the career/league profile after name setup when a connection is available. Android purchases and spending purchased balances require an authenticated online account; game-earned coins and boosters remain local.
Google Play handles Android payments. Our Unity Cloud Code and Cloud Save services validate product identifiers, purchase tokens, purchase state and an account-linked hash with Google, then store purchased balances and transaction records. Device transaction identifiers and pending-operation records help recover interrupted purchases and spending without granting or charging the same in-game balance twice. Refunds adjust purchased balances. We do not receive payment card details. A pending transaction may temporarily require reconnecting to the same account before gameplay can continue safely.
Automatic career/league synchronization also sends eligible puzzle actions and verified results to the configured Unity or Netcup-hosted services. Display names, cups and verified statistics are visible to other league participants; purchase tokens and authentication credentials are not public. Google and Unity also process service and purchase information under their own policies. Unity describes Android IAP collection in its Google Play data safety disclosure; this includes identifiers, purchase history and technical diagnostics, and may include transient approximate location and email processing depending on the purchase flow. The game does not request access to your contacts, messages or precise location.
You can request Android online-account deletion through the game’s account controls or our support page. Deletion removes the online account, purchased Coin and booster balances, league records and developer-controlled transaction records after pending operations are resolved and removal is verified. Purchased balances are not transferred to a new account. Locally earned campaign progress and resources are preserved. A private deletion-status receipt remains valid for 30 days. Deletion does not delete your Google account or purchase records independently retained by Google or Unity; see Google’s privacy policy.
Advertising and consent
Advertising depends on the build you use. The current published version, 1.0.5 on iOS and Android, uses Google AdMob as the only ad mediation platform, with Google’s User Messaging Platform (UMP) for privacy choices. Within AdMob mediation, ironSource Ads (ironSource Mobile, a Unity company) is added through Google’s official ironSource adapter and competes for each ad opportunity by bidding alongside Google’s own demand. The Unity LevelPlay mediation plugin and the Unity Ads SDK are not included. The earlier AdMob-only 1.0.3 build 90/91 candidates (14 October 2026) did not include ironSource; earlier LevelPlay builds, including 1.0.2 build 77 and the 1.0.3 build 89 candidate, use the historical flow described below. A version number alone does not identify the advertising configuration. Earlier ad-free builds keep advertising disabled. Unity In-App Purchasing and Unity account services are separate from advertising.
Advertising-enabled builds offer optional rewarded videos and infrequent interstitials at eligible transitions after winning a level. Interstitials do not appear during active play or in the first ten campaign levels. A permanent Remove Ads purchase disables interstitials; rewarded videos remain optional. There are no banner or app-open ads. A video reward depends on the advertising service’s completion confirmation, not accepting a privacy choice or tapping an advertiser link.
The game does not ask for your age and the in-game privacy choices do not turn ads on or off. The only consent gate is UMP: ads start after launch unless UMP reports that ads may not be requested. In regions where the law requires it, such as the EU, UK and some US states, Google’s own consent message is shown separately from the game’s privacy screen. Ads are non-personalized for every player, and Google ad requests are limited to the G content rating. Ads may load before you press a video button. Where required, Settings provides advertising privacy options; opening these options clears loaded ads before later requests. Declining does not block campaign play; ads may be limited or unavailable.
Rush Out does not request Apple App Tracking Transparency (ATT) authorization, so on iOS the advertising identifier (IDFA) is not made available to the game or its ad SDKs. Before the ad SDK starts, the game sets Google’s publisher privacy personalization to Disabled (non-personalized ads), disables Google’s publisher first-party ID and limits ad content to the G rating on both iOS and Android. ironSource Ads receives no personalized-advertising consent and a US “do not sell or share” signal for every player; for devices with an earlier under-18 age declaration it also receives child-directed and device-identifier opt-out signals. These are advertising configuration restrictions, not a claim that the services process no data.
When ads are allowed, Google and ironSource may process device and app information (such as device model, operating system, language, app version and, on Android, the advertising ID or app-set ID permitted by Android), IP address and IP-derived general location, ad requests, views, clicks and other ad interactions, and crash, performance and diagnostic data, for ad delivery, frequency capping, measurement, fraud prevention and service operation. Rush Out does not add your public player ID, league name, email or purchase records as advertising-targeting parameters. SDK data processing is separate from those game-supplied parameters. Using test ads or restricted advertising does not mean that no data is processed.
Historical LevelPlay builds: UMP supplies privacy choices, and on iOS Apple’s ATT choice is a separate gate. These builds initialize LevelPlay only when UMP permits requests and ATT authorization is granted; denied or restricted authorization leaves those ads unavailable while campaign play remains available. They can serve ironSource Ads and Unity Ads. The game does not pass a player ID to LevelPlay initialization and sends restrictive regional-consent and do-not-sell/share signals. Those advertising SDKs may process identifiers, advertising and usage information, diagnostics and purchase-related information for applicable features. Updating does not delete data already processed by providers used in older builds.
See Google’s iOS data disclosure, Android data disclosure and privacy policy. For ironSource Ads, see Unity’s privacy policy (ironSource is part of Unity), Unity’s game player and app user privacy policy and the ironSource Ads data disclosure. For older LevelPlay builds, see also LevelPlay’s disclosure and Unity Ads’ disclosure. Providers apply their own retention and privacy controls. Deleting a Rush Out account does not automatically delete advertising records independently controlled by Google or Unity; contact us if you need help directing a request.
This website
These pages are part of daviestudio.com, a static website without advertising, accounts, forms or cookies. The server keeps short-lived technical request logs, and the site can count page views anonymously unless you decline in its notice; details are in the site privacy notice. The site runs on our own Netcup-hosted server. The earlier address mehmetvi.github.io now only forwards visitors here; GitHub Pages may record request information for that forwarding, as described in GitHub’s privacy statement.
Storage, deletion and your choices
During migration, developer-controlled identity, league and game records may be copied from Unity to private Netcup-hosted storage. A captured copy is a snapshot, not evidence of current activity or every authentication account. Active account records and presence remain until verified account deletion. Deletion can span both production and testing environments; a pending request is not a completion claim. After erasure, limited hashed anti-recreation markers and ownerless player-ID reservations may remain so old requests cannot recreate the deleted account or reuse its identity. These markers are not described as anonymous. Encrypted operational backups rotate on a 14-day schedule; restoring a backup requires preserving current deletion markers. Support correspondence and transaction-count records have the separate handling described above.
Local game data generally remains until it is removed from the device or the game replaces it. Deleting the app does not necessarily delete backups, Apple purchase or Game Center records, or information already processed by Google or Unity. Those providers apply their own retention policies and offer their own account and privacy controls.
You can contact the developer about access, correction or deletion requests, including requests concerning Unity IAP data processed on the developer’s behalf. Include only the details needed to explain your request; do not send passwords or payment card information. Requests concerning data a provider controls independently may need to be handled directly by that provider. Depending on where you live, additional privacy rights may apply.
Children and international processing
If you are a parent or guardian with a concern about a child’s information, please contact us. Rush Out is not directed to children under 13, and its store audience is 13 and older. The game does not ask for an age; if an earlier version recorded an under-18 age on a device, ads on that device receive protected treatment (see Age and ad settings). Apple, Google, Unity (including ironSource), Yandex (from 1.0.6), Netcup and GitHub (for the forwarding address) may process information in countries other than where you live, under the terms and safeguards described in their own privacy policies.
Age and ad settings
Starting with 1.0.5, the game no longer asks for an age group, and there is no age setting. Every player receives non-personalized ads, without a child label, subject to UMP; Google ad requests are limited to the G content rating.
Earlier versions, including 1.0.4, asked for an age group and stored the answer only on the device; it was not sent to the developer’s server. That stored answer is still read:
- Earlier declaration of under 13, 13–15 or 16–17: ads continue with protected treatment. They are non-personalized, Google ad requests are limited to the G content rating, and Google receives the under-age-of-consent (child) treatment signal. ironSource receives child-directed, device-identifier opt-out, no-personalization and do-not-sell signals. Analytics, promotional notifications and purchase-history recommendations stay off and cannot be turned on.
- Earlier “18 or older”, “Prefer not to say” or no stored answer: general treatment. Each optional purpose follows your own choice.
Google and ironSource may still process the data described above for permitted ad delivery. These controls apply to advertising services; online account and gameplay processing is described in the sections above.
Changes
This policy may change as the game or its services change. The revision date above identifies this policy text. Material changes will be reflected on this page and, where appropriate, in the game.
Online career and league
In versions with online career and league services enabled, choosing or accepting a game name starts automatic registration for both guest and linked players when the service is reachable. The game retries unavailable connections; no separate “join league” confirmation is required. Eligible gameplay is then synchronized for career standings and applicable seasonal results. Pending withdrawal/deletion requests and completed deletion controls stop this automatic flow for the affected account. Unity Authentication also supports the separate profile-ID features described above. Depending on the deployed version, Unity Cloud Code, Cloud Save and Leaderboards or our Netcup-hosted game services process the service player identifier, Game Center display name, puzzle actions, and verified results, ranks, seasonal rewards and cup records. Unity Authentication remains the authentication provider. Your display name, cups and verified puzzle statistics are visible to other participants. Signatures and access tokens are not shown in public profiles. You can play campaign puzzles offline; this does not itself delete an existing online account or previously synchronized records. League account, profile, result, seasonal reward and cup records persist on the service until a deletion request is handled; leaving the app or deleting it does not itself delete those records. In your league profile → League Account, you can request withdrawal or account deletion and check Request Status. Withdrawal stops new uploads and hides your in-app profile; private statistics and reward records remain, and removal from the provider leaderboard may still be pending. Withdrawal is not account deletion. Account deletion is processed automatically on the server and can take several hours, including retries when services are unavailable. An accepted request remains pending until completion is verified; acceptance alone is not confirmation of deletion. The app can check a private deletion-status receipt after the original cloud sign-in has been removed. A hashed receipt is retained for status verification with a 30-day validity period. Local campaign progress, purchases and already earned rewards are preserved. Deleting the league account does not delete your Apple account or independently retained Apple or Unity purchase records. For help, contact support.rushout@gmail.com.