Privacy Policy
Summary
Dualbound has no account and no sign-in, and never asks for your name, email address or contacts. Your game progress is saved only on your phone. The game uses services run by Google to measure how it is played (Google Analytics for Firebase), report crashes (Firebase Crashlytics), adjust game settings remotely (Firebase Remote Config), show ads (Google AdMob) and sell optional ad-free passes (Google Play Billing). Each is described below. The game requests the Internet permission on Android for these services.
What the game stores on your device
To remember your progress, the game saves small files inside its own app storage on your phone:
- your stage progress, records and the stars you have earned
- daily missions, the weekly challenge, achievements, titles and the bricks and gimmicks you have met
- your gear, tickets and the characters, backgrounds and skins you have unlocked or chosen
- a duel in progress, so you can continue it after closing the game
- your settings (sound, music, vibration, language, speed, effects), whether you have seen the tutorial, and how many games you have played
- the status of a pass you bought, so the game knows when ads are turned off
These files never leave your phone. We cannot see them and cannot restore them. Uninstalling the game or clearing its storage deletes them.
Usage statistics (Google Analytics for Firebase)
The game sends these events to Google Analytics for Firebase:
- when the game is ready, and when a duel starts, is paused, is left, or ends: the mode (against the CPU or two players), the stage, how many seconds it took, both scores, whether you won or quit, and whether it was a continued duel
- ad placements: when an ad would show, is held back (and the rule that held it), or a reward ad is offered or completed
- for each ad shown: the ad’s estimated value and currency, and which ad network and ad unit provided it
- pass activity: opening the pass page, buying a pass (which plan), and using a free action that the pass gives you
- whether you currently hold a pass, and which difficulty target the game is using for you
- once, after you install the game from Google Play: where the install came from (the Play Install Referrer) — the source, medium and campaign named in the store link and whether it followed a Google Ads click. We use this only to measure which store links bring installs
- information the Firebase SDK collects on its own: when sessions start and how long the app is open, the app version, device model and operating system, and an approximate location (country or region) that Google works out from the connection
To count devices, the Firebase SDK creates a random app-instance ID for each installation. Firebase is set up not to collect the Android advertising ID for us (the ad service below uses it). We use these statistics only to improve the game and to balance its difficulty and ad frequency. We do not sell them.
Crash reports (Firebase Crashlytics)
If the game crashes, Firebase Crashlytics sends a crash report: where in the game’s code the crash happened, the app version, device model and operating system version, and a random installation ID that groups reports from the same installation. Reports contain no name, contacts or game progress. We use them only to fix bugs.
Remote settings (Firebase Remote Config)
The game downloads a few settings from Firebase Remote Config, such as how many duels pass before the first ad, the spacing between ads, and difficulty targets. These settings may differ between groups of players so that we can compare them. To fetch them, the SDK uses a random Firebase installation ID.
Ads (Google AdMob)
The game shows a full-screen ad at the end of some stages and offers optional reward ads (for example, to continue after a loss, to double the stars from a stage, or to roll gear once more). The ads come from Google AdMob. There are no banner ads. AdMob is set up only when the game is about to show its first ad, not when you open the game.
- When it is set up, users in the European Economic Area, the United Kingdom and Switzerland are asked for their choices about ads and data through a consent form from Google (User Messaging Platform). You can play either way. To change your choices at any time, open Settings in the game and tap Privacy choices; this row appears whenever the consent form applies to you, and your saved progress is kept.
- To show and measure ads and to prevent fraud, the Google Mobile Ads SDK collects the IP address (which may be used to estimate the general location of the device), your interactions with the app and its ads, diagnostic information about the app and the SDK, and device identifiers such as the Android advertising ID and app set ID. Google describes this in its data disclosure for the SDK and in How Google uses information from sites or apps that use its services.
- You can reset or delete your advertising ID in your Android settings.
Passes (Google Play Billing)
You can buy a prepaid pass for 1 week, 3 months or 1 year. A pass removes ads and does not renew automatically. Payment is handled entirely by Google Play: we never see your card or payment details. The game receives from Google Play only which pass you bought and whether it is active, and keeps that on your phone.
Who receives data
The only third party that receives data from the game is Google, through the services above. Google processes it under the Firebase privacy and security terms and the Google Privacy Policy. We do not sell data, and we do not run our own server for game data.
What the game does not do
- No account, no sign-in, no chat and no online play with strangers. Two-player mode is on one phone.
- No precise location, contacts, photos, camera or microphone are accessed.
- The advertising ID is used only by the ad service described above.
Children
The game is not directed at children. It does not ask anyone, including children, for a name, contact details or other personal information.
Changes
If a future version starts collecting or sharing other data, this page will be updated before that version is released, and the effective date above will change.