1. Data processed by the game
The game processes a Firebase account identifier when you sign in, an optional email address and public display name supplied by your authentication provider, game progress, inventory, preferences, achievements and technical save metadata. Guest play stores progress locally on the device.
2. Purposes
These data are used to authenticate accounts, synchronize and restore cloud saves, prevent conflicting devices from silently overwriting progress, provide account deletion and recovery tools, operate purchases, diagnose technical problems and maintain the game.
3. Authentication and cloud storage
Authentication is provided through Google Firebase Authentication. Depending on the option you select, Google, Facebook or email credentials may be used by the authentication provider. The game does not receive your provider password. Cloud saves are stored in Google Cloud Firestore and are restricted to the authenticated account identifier.
4. Payments
Web payments are processed by Xsolla. Payment-card details are entered on Xsolla's checkout and are not stored by the game. The game receives transaction identifiers, product identifiers, payment state and signed notifications needed to grant or revoke purchased content. Android purchases may be processed by Google Play when that version is offered publicly.
5. Advertising and consent
The game may offer optional rewarded advertising. A rewarded advertisement is initiated by the player in exchange for a clearly described game benefit; declining or closing it does not block normal play. Google advertising services may process device, consent and advertising information according to the choices available in the consent message. Users in the EEA, United Kingdom and Switzerland are shown a Google-certified consent mechanism where required.
6. Analytics and diagnostics
Cloudflare Web Analytics may collect privacy-oriented aggregate information about visits and performance. The support diagnostic can include the game build, language, installation type, viewport, network state, account UID, save version, maximum zone and recent client errors. It is displayed to the player before being included in an email so additional context can be added.
7. Local storage and offline play
Local storage, IndexedDB, caches and a service worker are used for preferences, local progress, downloaded assets, update state and offline operation. Removing site data from the browser can delete an unlinked guest save. A connected account provides cloud recovery but does not replace the need to choose carefully when a genuine save conflict is shown.
8. Retention
Cloud save data are retained while the account exists and may include a limited save history for restoration. Purchase records may be retained as required for accounting, fraud prevention, refunds and legal obligations. Local data remain until the player, browser or operating system removes them.
9. Sharing and processors
Data are not sold by the game developer. They are shared only as necessary with service providers operating authentication, cloud storage, hosting, analytics, advertising, payments and player support, or when disclosure is legally required.
10. Account deletion and player rights
The in-game privacy panel contains a permanent account-deletion action. This removes the Firebase account and associated cloud save records after recent authentication is confirmed. You may request access, correction or deletion assistance through Support. Applicable privacy law may provide additional rights concerning processing, objection or restriction.
11. Children
The game is not directed to children below the minimum digital-consent age applicable in their country. A parent or guardian should supervise access where required. Purchases require the authorization of the account holder and the relevant payment platform.
12. Security
Firebase Security Rules restrict cloud-save access to the authenticated account. Firebase App Check, signed payment webhooks and server-side purchase validation are used to reduce unauthorized access. No online system can guarantee absolute security, so suspected account or payment issues should be reported promptly.
13. Contact and policy changes
Questions can be sent to [email protected]. This policy may be updated when services or legal requirements change. The current version and update date will remain available on this page.