PLAYER RESOURCES
Coin Pusher: Monster Siege — Privacy notice
Developer: Vic Yang, Hebei, China. The published document will describe the actual release before the game becomes publicly available.
What this means for players
The free, no-ad and no-purchase statements for B20 do not apply to this game. Data handling, service providers, advertising, purchases, eligibility and any account or deletion features must be confirmed for its release. No claim that this game collects no data is made here.
Current development data practices
On your device
Progress, currencies, inventory, unlocks, settings, a local save identifier and device-model information are stored locally. Optional sharing choices are saved on the device. The current project does not use B20’s online account, leaderboard or cloud-save system. Device backup behavior depends on your operating system and settings.
Optional analytics and crash diagnostics
Google Analytics for Firebase and Firebase Crashlytics have separate choices, both off by default. The current interface lets you change them in Settings → Data sharing. Closing the first-run choice without opting in records a refusal. Turning off a choice stops new optional reporting; it does not delete reports already uploaded.
If enabled, reporting can include app and device information, app-instance or installation identifiers, usage events, player level, numerical gameplay outcomes and crash/error diagnostics. The custom gameplay schema uses predefined events and numerical parameters; it does not send free text, full saves, purchase receipts or the local save ID as analytics parameters. Clearing the custom user ID does not remove identifiers managed by Firebase itself.
When both options are on, gameplay event breadcrumbs can accompany crash diagnostics. Native crash-report changes may require restarting the app, and locally queued reports may be sent if reporting is later enabled. Developer-side controls still require verification against the final installed build.
Rewarded advertising and your choices
The current Android build integrates Google AdMob (Google Mobile Ads SDK) and Google’s User Messaging Platform (UMP). You may choose to watch a rewarded ad for an in-game benefit. When UMP permits ad requests, the game may preload an ad before you press the watch button; choosing not to watch does not mean no ad request has occurred. Test advertisements also use Google’s advertising services.
For ad delivery, measurement, diagnostics and fraud prevention, Google’s advertising services may process your IP address and approximate location inferred from it, app and device information, ad interactions such as views and taps, diagnostic information, and device or app identifiers such as an app set ID. The current Android build removes the advertising-ID and Android ad-services permissions; this does not prevent all identifier or connection-data processing. The game does not request precise device location for advertising.
Where applicable, Google UMP presents an advertising privacy message with consent and privacy options. The game requests ads only when UMP reports that requests are allowed. Where UMP requires it, Settings → Ad privacy lets you revisit those choices. Declining personalized advertising does not necessarily stop all advertising or the processing needed for permitted ads. These advertising choices are separate from the optional Firebase analytics and crash-report switches in Data sharing; turning those switches off does not disable AdMob.
Google processes advertising data under its applicable policies and may process it outside your country. Retention depends on the data and purpose; we do not promise a fixed deletion period for Google-held advertising records. You can contact us about advertising data requests, and use Google’s privacy controls for records Google manages. We cannot locate or erase every Google-held record using your local game save.
How Google uses information from apps and sites · Google privacy controls
Store purchases
Purchasing is integrated through Unity IAP and Google Play on Android. The store handles your payment account and payment details; the game processes product IDs, purchase receipts, transaction identifiers and purchase state to validate purchases, deliver items and prevent duplicate delivery. We do not receive your full payment card details. Store availability and test purchases depend on the store account and release configuration.
Retention and requests
Local data remains until cleared, overwritten or removed, subject to device backups. The Analytics property’s actual retention settings have not yet been verified and must be recorded before release; B20’s retention settings do not apply to this game. Firebase documents a 90-day retention period for Crashlytics traces and associated identifiers before removal begins. Store records follow applicable provider and legal requirements.
Email the developer to request review or removal of information already sent. There is no authenticated game account to delete in the current implementation. A device or app-instance identifier may be needed to locate diagnostic or analytics records; uninstalling alone does not remove those records. Do not send passwords or verification codes.
Firebase privacy and retention information · Google privacy policy · Unity game-player privacy policy
Already used a test build?
You can contact the developer now about a test build, a privacy question or removal of data. Include the game name and version if known. Do not send passwords, tokens or verification codes.
Contact the developer