SUNFLOWER / MISTBOUND

Privacy policy

Effective and last updated: November 19, 2026

Local saves, optional gameplay analytics and crash reports, and your choices. Here is how we handle information.

The current version, at a glance

No account required · Local saves · Optional Android and iOS analytics and crash reports off by default · Google AdMob ads

01Scope

This policy is provided by sunflower and applies to the current version of Mistbound: Dungeon Escape and this official game website. The game is built for Android and iOS. This policy explains how game data, website access information, and messages you send to us are handled.

02Local game saves and optional usage data

The game does not require an account. Your current run, unlocked characters, records, gold, cosmetics, tasks, language and sound preferences, and local reward-entry counters are stored on your device to restore progress and remember preferences. We do not provide cloud save synchronization or receive copies of your complete game saves.

Separately, if you enable optional analytics in the Android or iOS game, selected gameplay events and a randomly generated player identifier are sent to Google Firebase Analytics as described in section 03. This identifier is pseudonymous: it links activity in the same local game installation without requiring your name or an account. The game does not request your name, precise location, contacts, or photos. Advertising and analytics services process the technical information described below.

03Advertising, analytics, and purchases

Google AdMob advertising. The game displays advertising provided by Google AdMob. To request, deliver, cap, and measure ads, and to prevent invalid traffic, the AdMob SDK may collect and share with Google your advertising identifier or other advertising-related device signals, IP address, device and app information such as device model, operating-system version and language, approximate location derived from your IP address, and ad interactions such as impressions and clicks. Google processes this information under its own policies.

Where required by applicable law, including in the European Economic Area, the United Kingdom and Switzerland, we request consent through Google's consent form before the relevant advertising processing. When available, you can reopen that form through Settings → Privacy → Manage ad privacy options. You can also manage advertising identifiers and personalization in your device settings. Advertising choices and optional gameplay analytics are separate.

Optional Firebase Analytics on Android and iOS. Gameplay analytics is off by default. It starts only after you enable “Share gameplay usage data” in Settings → Privacy and save the setting. We use Google Firebase Analytics (Google Analytics) to understand game usage, progression, the in-game economy and advertising interactions, and to improve the game. The browser version currently does not send gameplay events to Firebase Analytics.

When enabled, events may include game launches, starting or resuming a run, floor entry and outcomes, run results, character and difficulty choices, blessings and keepsakes, shop activity, in-game gold earned or spent, and ad entry, loading, playback and reward results. These events include a randomly generated player ID, session and event IDs, event times, app version, language and relevant gameplay parameters. The player ID normally persists within the same local data space; clearing that data generates a new ID. It is not a login account or a hardware identifier.

The Analytics SDK also processes automatically collected app, device and interaction information, such as app-instance identifiers, device model, operating-system version, app version, language, first-open and session events, and engagement information. Google may process IP addresses in providing the service, including deriving approximate location; we do not request precise device location for analytics. We can view analytics reports and events in the Firebase/Google Analytics console. Google processes service data under its own terms and privacy policies.

For this Firebase Analytics integration, advertising-ID collection is disabled and consent for advertising storage, advertising user data and ad personalization is set to denied. These Analytics settings do not disable AdMob's separate advertising processing. You can turn gameplay analytics off at any time and save the setting; this stops further collection and clears pending game-event uploads, as explained in section 06.

Optional Firebase Crashlytics on Android and iOS. Crash and error reporting is off by default and separate from gameplay analytics. You can enable “Share crash and error reports” in Settings → Privacy and save the setting. When enabled, Firebase Crashlytics sends Android and iOS crash reports and unhandled JavaScript errors to Google to help us diagnose faults and improve stability. These JavaScript reports are nonfatal diagnostics and do not necessarily mean the app closed. Completed reports are submitted on subsequent game starts while reporting remains enabled; delivery is not immediate or guaranteed.

Reports may include exception types and messages, call stacks and code locations, report and installation/session identifiers generated by the SDK, crash times, app and operating-system versions, device model and technical state such as available memory and storage. JavaScript reports may also include game version, language, selected character, difficulty and current floor. We do not deliberately attach complete saves, contacts or photos to these reports, and we filter common email addresses, URL query strings and credential patterns from JavaScript diagnostic text. Error messages can still contain dynamic information. If you also enable gameplay analytics, Analytics events may be included as breadcrumbs to help explain activity before a crash. The browser version currently does not send Crashlytics reports.

You can turn crash and error reporting off and save the setting at any time. This disables automatic report upload and requests deletion of unsent reports; it does not delete reports already received by Google. With automatic upload off, the SDK may still generate diagnostic files locally. The game requests deletion of unsent reports when reporting is disabled and before a new opt-in, so previous opt-out reports are not deliberately submitted as a backlog. The game does not set your gameplay player ID as a Crashlytics user ID.

Purchases and future changes. The cosmetic shop and in-game rewards use gold and items earned in the game; there is no real-money payment integration. We will update this policy when additional services change how information is processed, and provide notice and consent choices where required.

How Google uses information from sites or apps that use our services ↗

Firebase privacy and security information ↗

04Official website and hosting

This website is hosted using Google Firebase Hosting. When you visit, the hosting provider processes technical information needed to deliver and protect the website, such as your IP address, browser or device information, request time, and requested resources. We have not added visitor analytics, advertising trackers, marketing cookies, or game-account registration to this website. Google handles hosting data under its own privacy policy.

Google Privacy Policy ↗

05When you contact us

If you email sunflower, we receive your email address, message, and any attachments or other information you choose to provide. We use this information to respond, provide support, and handle privacy requests. We do not use it for marketing or sell your personal information. Please do not send passwords, payment credentials, or unnecessary sensitive information. Email providers process messages under their own policies.

06Retention and deletion

Local game data remains on your device until overwritten or cleared. You can clear it through your device's app-storage settings, or clear site storage for the browser version. This removes local progress and unlocks. Uninstalling normally removes local data, but operating-system backups may retain or restore copies depending on your device and backup settings. We do not receive copies of your complete local saves.

When optional Android and iOS analytics is enabled, game events may be queued locally before being handed to the Firebase SDK. The game's pending queue holds at most 300 events for up to seven days; the SDK manages its own subsequent upload queue. Turning off “Share gameplay usage data” and saving stops further collection, clears the game's pending queue, and requests a reset of local Firebase Analytics data. It does not delete information already transmitted to Google or automatically erase existing reports.

Crashlytics reports are generally retained by Google for 90 days, subject to its current service policies. Disabling reporting or clearing local app data does not erase previously uploaded crash reports. Contact us below about access or deletion requests. Uploaded analytics information is retained according to the Google Analytics property's retention settings and Google's service policies. Aggregated reports may be retained separately from individual event and user data. To ask about access or deletion, contact us using the address below; we will assess requests under applicable law and the identifiers and tools available to us. Clearing local data alone does not delete previously uploaded information.

Support emails are retained to handle your request, necessary follow-up and applicable legal obligations; you may request deletion using the address below. Hosting and advertising providers manage retention of the technical information they process under their policies.

07Your choices and rights

You can enable or disable optional Android and iOS gameplay analytics through Settings → Privacy → Share gameplay usage data, then save the setting. Optional crash reporting has its own “Share crash and error reports” switch in the same screen. Both choices are off by default, and declining either does not prevent gameplay. Advertising consent can be managed separately through Manage ad privacy options when available, and through your device's advertising settings.

You can manage local storage and operating-system backups, choose not to send personal information by email, and request access to, correction of, or deletion of information we process about you. Depending on local law, you may also have rights to withdraw consent, object to or restrict processing, data portability, and to complain to a data-protection authority. Contact us below to exercise these rights. We may need information to verify your request and identify the relevant records; do not send passwords or unnecessary sensitive information. We cannot access or recover game records stored only on your device.

08Children’s privacy

The game does not require an account. Optional gameplay analytics is off by default, and we do not knowingly use it to collect children's personal information without any consent required by applicable law. Google AdMob advertising is subject to Google's policies and applicable consent requirements. If you are a parent or guardian and believe your child has provided personal information through the game or by email, please contact us so we can review the circumstances and take appropriate action. We will apply protections required by applicable law.

09Security and service providers

We take reasonable steps to protect information we process, but no transmission or storage method is completely secure. Relevant information is shared as needed with hosting, email, advertising and, when enabled, analytics and crash-diagnostics providers, or where required by law or to protect lawful rights. Google, including Google AdMob and Firebase/Google Analytics and Firebase Crashlytics, may process information outside your region under its policies and applicable law.

10Policy updates

We may update this policy when game features or data practices change. The latest version will appear on this page with an updated date. We will provide notice of material changes as required.

11Contact us

Developer: sunflower
Game: Mistbound: Dungeon Escape
Email: zdq18992199@gmail.com

For privacy questions or requests about your information, please email the address above.