Last updated: 12 November 2026
1. Scope and controller
This policy explains how data is processed in the Warvolve game and on warvolve.games. The game publisher and the controller for the processing described below is Samsufi sp. z o.o., address: ul. Jagiellońska 4A, 19-120 Knyszyn, Poland, entered in the Polish National Court Register (KRS) under number 0000901262, EU VAT: PL5423435334.
For privacy, GDPR and data deletion requests, contact [email protected]. For technical support, contact [email protected]. We do not run a telephone helpline; email is our contact channel. You do not need to install the game or create an account to contact us. The company has not appointed a data protection officer (DPO).
This policy covers the game on Android (package name pl.samsufi.warvolve, distributed through Google Play), the game on iPhone (bundle ID pl.samsufi.warvolve, distributed through the App Store) and the website. The game is not yet available in the stores; this policy describes the version that will be published. Where a provision applies to only one platform, it says so.
We do not operate our own server containing player profiles. This does not mean that no data leaves your device when you use the game: Google provides crash reporting, game statistics (only with your consent), Google Play Games and store services, Apple provides the App Store, Game Center and iCloud for the iOS version, and Cloudflare delivers the website.
2. Key information
- Warvolve is a single-player strategy game against computer-controlled opponents. It has no multiplayer mode, chat, Warvolve accounts, messages between players or user-generated content.
- The game has no ads and no in-app purchases. It contains no advertising SDK and does not collect the advertising ID (on Android the AD_ID permission is removed; on iOS neither the IDFA nor the IDFV is collected, so the game shows no tracking prompt).
- Progress, settings and records are stored on your device. Campaign, skirmishes, Endless Siege, challenges and saving work without an internet connection.
- Firebase Crashlytics sends technical crash reports so that we can fix bugs (section 5).
- Google Analytics for Firebase and Firebase Performance Monitoring are off until you agree in the game's “Game statistics” window. You can change your choice at any time in Settings › Game statistics (section 6).
- On Android, the game can use Google Play Games (sign-in, leaderboards, achievements and cloud saves, section 7). On iOS, it uses Game Center and an iCloud save on your own account (section 8).
- The game does not ask for your name or email address and does not use contacts, the camera, microphone, photos or location.
- The website has no cookies of its own, no analytics and no trackers, and loads nothing from other servers (section 12).
3. Data, purposes and legal bases
In the table, “contract” means GDPR Article 6(1)(b), “consent” means Article 6(1)(a), “legal obligation” means Article 6(1)(c), and “legitimate interest” means Article 6(1)(f).
| Data | Purpose | Legal basis | Where it goes |
|---|---|---|---|
| Profile, progress, settings, records and battle history stored on the device | Providing the game | Contract | Stays on the device (and in your own system backup, section 11) |
| Crash reports with technical data and a random Firebase installation ID | Finding and fixing errors | Legitimate interest in a working, secure game | Firebase Crashlytics (Google, our processor) |
| Game statistics events, device and app data, approximate country, random app-instance ID | Balancing stages and improving the start of the game | Consent | Google Analytics for Firebase (Google, our processor) |
| Performance measurements (start-up time, frame smoothness, network timings) | Keeping the game smooth on different devices | Consent | Firebase Performance Monitoring (Google, our processor) |
| Play Games profile, scores, achievements and cloud save (Android) | Leaderboards, achievements and cloud saves you use | Contract | Google Play Games (Google) |
| Game Center scores and achievements, iCloud save (iOS) | Leaderboards, achievements and restoring progress | Contract | Apple, on your Apple Account |
| Emails you send us and their contents | Answering questions, complaints and GDPR requests | Contract, legal obligation, legitimate interest | Our mailbox (section 14) |
| IP address and request data of website visits | Delivering and protecting the website | Legitimate interest | Cloudflare (section 12) |
4. Data stored on your device
The game stores the following in its private app storage:
- your in-game commander nickname;
- campaign stages, stars, medals, research, missions, achievements and local leaderboard records;
- battle history and saved replays;
- statistics (such as battles, wins, defeated units and play time);
- settings (such as language, graphics quality, sound, vibration, accessibility options, reminders and reminder hour) and your choice in the “Game statistics” window;
- a temporary save of an interrupted battle so you can resume it;
- up to 10 local crash and error reports and up to 3 reports of the app being ended by the system;
- a local playtest log (days and sessions played, time to finish the tutorial and to the first win, loss streaks, surrenders, visited screens and performance of recent sessions).
Local problem reports contain the game version, device model, operating system version, the current screen, the last 30 technical events and the call stack; on Android 11 and later also the system's reason for the previous exit of the app. They do not include your nickname, player IDs, exception messages or profile data. They never leave the device automatically. After a crash the game asks once whether you want to share the report, and Settings › About › Report a problem does the same: both only open the system share sheet, and you decide whether to send it and to whom.
Tester report and feedback (test builds only). The tester report (Settings › About) works the same way: it opens the share sheet with technical information and settings, including whether a screen reader is on, and is never sent automatically. Test builds also have a “Leave feedback” button that saves notes and an error log only on the device; they leave it only when you share the file yourself. In the version published in the stores, the feedback feature is turned off.
5. Crash reports (Firebase Crashlytics)
When the game crashes or catches an error while drawing a frame, it sends a report to Firebase Crashlytics, a service of Google LLC. The report contains the technical details of the error (error type, stack trace and time, without exception messages), the device model, operating system and game version, free memory and storage, a random installation identifier created by Firebase, and the game's state at the time: the open screen, mode, stage, era and graphics quality level. Crashlytics also records app starts to measure the share of crash-free sessions.
The report contains no nickname, email address, Play Games or Game Center account, advertising ID or location, and we do not add any. We use crash reports only to find and fix bugs, based on our legitimate interest in a working and secure game, so they work without separate consent. You may object to this processing (section 17). Crash reports are kept for 90 days.
6. Game statistics and performance (only with your consent)
Statistics are off until you agree. After the tutorial the game shows its own “Game statistics” window once, with two equal buttons: “I agree” and “No, thanks” (Back means no). Before you agree, the game records no statistics at all and nothing is queued; after you agree, it collects them only from that moment. You can change your choice at any time in Settings › Game statistics. The decision is stored only on the device, outside the profile, backups and cloud saves. The game works the same without consent.
Google Analytics for Firebase (Google LLC). With your consent, the game records events from a closed list: first launch, early milestones (such as the first win, the first research or 10 minutes of battles), battle start and end (mode, stage, era, difficulty, result, duration, surrender), Staff Orders results, the Endless Siege wave reached, the Daily Challenge result, research purchases, opening a mode screen and tutorial steps when you replay the tutorial. The events contain no nickname, account, text typed by the player or identifiers other than Firebase's own. Google Analytics also records basic usage events (such as sessions and app updates), the device model, operating system and game version, a country or region derived from the IP address (Google does not store the IP address itself) and a random app-instance identifier. Google consent mode is set so that ad storage, ad user data and ad personalisation are always denied. We do not use these statistics for advertising, do not build profiles of individual players and do not sell them. Event-level data is deleted after 2 months; aggregated reports that identify no one may be kept longer.
Firebase Performance Monitoring (Google LLC), under the same consent: the time from launch to the menu, app start and screen rendering times measured by the SDK, the timing of the game's network requests (address without parameters, response code, size and time) and, for each battle, its duration, number of frames, slow and frozen frames, average frames per second, mode, starting era, graphics quality and frame limit. The SDK adds the device model, operating system and game version, CPU and memory use, carrier and network type, language, a random Firebase installation identifier and the country derived from the IP address. The measurements contain no nickname, account or game content. Withdrawing consent turns them off together with the statistics. Google keeps IP-associated events for 30 days and installation-associated data for 60 days.
Debug test builds never send statistics or performance measurements. Firebase is active only in builds configured by us.
7. Google Play Games (Android)
The game integrates Google Play Games Services. Play Games is not needed to play. When it is configured and your Google account allows it, Google may sign you in to your Play Games profile automatically when the game starts; the game also checks sign-in when it returns to the foreground. In Settings › Play Games you can retry sign-in or request synchronisation. After sign-in, the following may be transferred to Google automatically, without a separate confirmation each time:
- scores for five leaderboards: Endless Siege, Daily Challenge, campaign stars, Skirmish and Staff Orders. Google's leaderboards may show your Play Games profile name and score to others according to your profile visibility settings; your in-game nickname is not used as the public name;
- unlocked achievements;
- a cloud save of the game profile (nickname, local scores with their names and dates, progress, medals, research, missions, achievements, statistics and settings), so that progress returns on another device signed in to the same account. If saves conflict, the game keeps the profile with more progress.
Sign-in uses your Play Games player ID and profile name. The game does not ask for your Google password, email address or phone number. Google processes Play Games data under its own policies and may collect its own diagnostic data. You manage Play Games accounts and automatic sign-in in your Google Play or device settings. Play Games data collection, Google Privacy Policy.
8. Apple services on iOS
- Game Center: when you are signed in to Game Center, the game sends leaderboard scores and unlocked achievements to Apple. Game Center leaderboards are visible to other players under your Game Center name, according to your Game Center privacy settings. The publisher does not receive your Apple Account data.
- iCloud save: when you are signed in to iCloud, the game keeps a copy of your game profile (progress, settings and nickname) in the iCloud key-value store on your own iCloud account, so that progress returns after reinstalling and is shared by your devices. The publisher has no access to this copy.
- Share sheet: “Report a problem”, the tester report and profile export open the iOS share sheet or the Files app; nothing is sent unless you choose a recipient.
- iOS backup: the device backup may include the game profile, battle history and replays. It does not include the statistics choice, the reminders answer, the playtest log, local crash reports or the feedback log, which are excluded from backup.
Game Center & Privacy, Apple Privacy Policy.
9. Ratings and updates
After certain campaign wins the game may ask the store to show its standard rating prompt (Google Play In-App Review on Android, Apple's rating prompt on iOS). The store decides whether and how often to show it, and any rating goes directly to Google or Apple.
On Android, when the game was installed from Google Play, Google Play In-App Updates may offer a new version in the main menu. On iOS, at most once an hour when the game becomes active, it asks Apple's public App Store lookup service which version is available in your country; the request contains no player data. If a newer version exists, the menu shows a button that opens the App Store.
10. Daily Challenge reminders
The game can remind you about the Daily Challenge once a day, after your first win and only while reminders are on. The game does not ask for notification permission at launch: after a later win it shows its own question first, and the system prompt appears only if you choose “Yes”. Reminders are scheduled locally on the device (Android AlarmManager, iOS UNUserNotificationCenter). No data is sent to a server for them and the game uses no push notifications. You can turn reminders off in the game's settings or in the system notification settings.
11. Android permissions and backups
| Permission | Purpose |
|---|---|
| INTERNET | Play Games, crash reports, consented statistics and store features; the game itself works offline |
| POST_NOTIFICATIONS | Local Daily Challenge reminders, only with your permission (Android 13 and later) |
| RECEIVE_BOOT_COMPLETED | Rescheduling local reminders after the device restarts |
| VIBRATE | Haptic feedback, which can be turned off in settings |
If Android backup is on, it may include the profile (with your nickname, progress and settings) and the battle history. The interrupted-battle save, replays, local reports, the playtest log and the feedback log are excluded. Android backup is separate from the Play Games cloud save; the publisher has no access to your system backups.
12. The warvolve.games website
Hosting and security. The website is static, without accounts, forms, advertising or analytics. Cloudflare Pages delivers it and protects it against abuse. Cloudflare receives IP addresses and request data needed to transmit content and protect its services and keeps its logs according to its own policy. We do not have access to raw IP logs. The site itself sets no cookies; Cloudflare's security features may set strictly necessary security cookies (such as __cf_bm) only when bot protection requires it.
No statistics, no external requests. We do not use website analytics or tracking. Fonts and images are served from warvolve.games itself; the site does not connect to font services, social networks or other third parties.
The browser demo runs entirely in your browser. It sends nothing anywhere and stores nothing.
Remembering your language. Only when you explicitly choose a language from the menu does the site save a wv-lang entry in your browser's localStorage. It contains the language code and an expiry date, expires automatically 6 months after it is saved and is never sent to us. Storage strictly necessary to provide a feature you have explicitly requested does not require consent (Article 399 of Poland's Electronic Communications Law and Article 5(3) of the ePrivacy Directive). You can remove the entry by clearing this site's data in your browser.
13. Age of players
The game does not ask for your age and does not verify it. The game's age rating is assigned through the stores' IARC questionnaire and is shown on its Google Play and App Store pages. The game is not enrolled in Google Play's Families programme.
In Poland, a person under 16 cannot give consent covered by GDPR Article 8 alone; other EU countries set this age between 13 and 16. If you are below the age applicable to you, do not agree to game statistics without permission from a parent or guardian. You can play the game in full without that consent. If you believe that a child's data has been processed improperly, contact [email protected].
14. Recipients and transfers outside the EEA
Google: for Firebase Crashlytics, Google Analytics for Firebase and Firebase Performance Monitoring, Google acts as our processor under the Firebase data processing terms; we do not enable data sharing with other Google products for advertising. Google is separately responsible for Google Play, Play Games and Google accounts. Firebase privacy and security.
Apple: for the iOS version, Apple separately processes Apple Account and App Store data and is separately responsible for Game Center and iCloud.
Cloudflare: it acts as our processor for data processed on our instructions and may act as a separate controller for its own network data. Cloudflare Privacy Policy.
Email: messages sent to [email protected] and [email protected] are routed through Cloudflare Email Routing to a Gmail mailbox provided by Google, both acting as our processors.
Google, Apple and Cloudflare may process data in the United States and other countries outside the EEA. Google and Cloudflare rely on the EU–US Data Privacy Framework for transfers covered by their certification and on European Commission standard contractual clauses where required; Apple describes standard contractual clauses for EEA data. To ask about safeguards and how to obtain a copy, contact [email protected].
15. Retention
- Local data stays on the device until you reset progress, clear the game's data or uninstall it.
- Crash reports: 90 days. Game statistics: event-level data for 2 months. Performance measurements: 30 to 60 days. They are then deleted automatically.
- Emails to [email protected] and [email protected], including attachments: 2 years after the case is closed. A minimal register of how GDPR requests were handled (date, scope, outcome): 3 years after the case is closed.
- Data held by Google, Apple and Cloudflare under their own control is kept according to their policies and your account settings.
16. How to delete data
- Data on the device: “Reset progress” in the game's settings clears progress and records but keeps your nickname. To remove everything, clear the game's data in the system settings or uninstall the game. A system backup may still contain the profile until it is replaced.
- Play Games (Android): open your Play Games profile and delete the data for this game, or delete the whole profile. First uninstall the game or clear its data on every device signed in to Play Games, otherwise a device may upload its progress again. Google Help.
- iCloud and Game Center (iOS): “Reset progress” replaces the iCloud copy with a profile without progress (the nickname stays). To remove the copy completely, delete the game from your devices and then remove its data in Settings › [your name] › iCloud › Manage Storage. Game Center data is managed with Apple's tools or the Apple privacy portal.
- Crash reports, statistics and performance data: they are linked only to random installation identifiers, not to your name. You can ask for access or deletion at [email protected]; tell us roughly when you played and your device model so that we can try to find the installation. If we cannot identify it, GDPR Article 11 applies. Withdrawing consent in Settings › Game statistics stops future collection.
- Data under our control: email [email protected]. You do not need to install the game or have an account.
17. Your rights
To the extent and under the conditions provided by the GDPR, you may access your data and obtain a copy, correct it, request deletion or restriction of processing, obtain data in a portable format, object to processing based on legitimate interest (including crash reports), and withdraw consent at any time in Settings › Game statistics without affecting earlier lawful processing. You may complain to the President of the Personal Data Protection Office (UODO) in Warsaw, Poland, or to the authority in the country where you live or work. UODO.
Send requests to [email protected]. We respond without undue delay, normally within one month. Warvolve does not make decisions about you based solely on automated processing.
18. Changes to this policy
If data, services or the law change, we will update this policy and its date. We will communicate a material change in a way appropriate to its scope before it affects your data. Updating this document never replaces fresh consent where consent is required. Questions: [email protected].