Version 2.2 · effective from 4 September 2026
The short version, with nothing hidden: to let you play, we need your email, a password and your location. Location is the core of the game — without it there would be no territory to conquer. We delete the detailed location history after 24 hours; what stays long term is a daily total of the metres you walked and an anonymous record of which coarse part of the map somebody moved through.
We do not sell your data and we do not hand it to anyone for advertising. There is no ad package and no advertising identifier anywhere in the app. You can delete your account and its data at any time — straight from the game in Settings, or through the form on the website.
Below you will find the full breakdown: for every purpose, the specific data, the legal basis and how long we keep it.
The controller of your personal data is the operator of the game Kokume:
For any question about personal data, write to info@kokume.eu — it is also the contact point for exercising your rights. We have not appointed a data protection officer, because the law does not require us to; your requests are handled at the address above.
This table is the heart of the whole document. For every purpose it names the specific data, the legal basis under the GDPR and how long we keep the data.
| Purpose | Data | Legal basis | Retention period |
|---|---|---|---|
| Game account and sign-in | Email, encrypted password, account status, time of registration and of the last sign-in, whether you registered on the website or in the game | Performance of a contract (Art. 6(1)(b) GDPR) | For as long as the account exists |
| Verifying the minimum age at registration | The date of birth entered in the registration form | Compliance with a legal obligation and performance of a contract — the game is offered from the age of 16 | Not stored; evaluated when the form is submitted and then discarded |
| Location-based game mechanics | GPS coordinates, accuracy of the fix, speed of movement; with each record the IP address and an identifier of the app | Performance of a contract | 24 hours from the record |
| Location with the screen off (optional) | The same as for the game mechanics, only recorded while the game is in the background or your screen is off | Consent (Art. 6(1)(a) GDPR) — switched on in the game Settings and withdrawable there at any time; off by default | 24 hours from the record |
| Daily movement summary (walking streak) | Date and the number of metres walked that day | Performance of a contract | For as long as the account exists |
| Game progress | Hero name, faction, buildings, units, items, resources, conquered territory, battle results, score | Performance of a contract | For as long as the account exists |
| Sign-in with a Google account (only if you choose it) | The Google account identifier and the email address Google passes to us | Performance of a contract | Until the link is removed or the account is deleted |
| Sign-in tokens and two-factor authentication | IP address, identifier of the device and browser, token validity | Performance of a contract | Until the token expires |
| Protection against creating multiple accounts | IP address, identifier of the device and browser, device fingerprint (operating system type, language, game installation identifier), version of the terms you accepted | Legitimate interest (Art. 6(1)(f) GDPR) — keeping the game fair | For as long as the account exists |
| An overview of where players come from | Country code derived from the IP address used at registration (only the country code is stored, not a location) | Legitimate interest — knowing which countries the game is played in, and offering and translating it accordingly | For as long as the account exists |
| Plausibility check of reported location | A record of the rejected location and the type of discrepancy | Legitimate interest — keeping the game fair | For as long as the account exists |
| Game and operational logs | Actions taken in the game, resource changes, the time and technical context of the action | Legitimate interest — tracing bugs, disputes and abuse | 90 days |
| Push notifications | Device token or push service address, encryption keys, device identifier, your notification settings | Consent (Art. 6(1)(a) GDPR) | Until consent is withdrawn or the account is deleted |
| Measuring how the game is used (our own telemetry) | Game session identifier, event name, platform, game and system version, device language, session length, application error messages | Consent (Art. 6(1)(a) GDPR) — nothing is collected unless you switch it on | 30 days |
| Faction chat | The text of the message, its author and the time it was sent | Performance of a contract | For as long as the account exists; after the account is deleted the message stays without any link to its author |
| Reporting a player and content moderation | Who reported whom, the reason and description; a record of any measure imposed | Legitimate interest and compliance with a legal obligation under the Digital Services Act | For as long as the account exists |
| Account emails (address verification, warning about an upcoming deletion, password reset) | Email address | Performance of a contract | For as long as the account exists |
| Protecting the registration form and the account deletion form against bots | The reCAPTCHA assessment, IP address and in-browser behaviour when the form is submitted | Legitimate interest — protection against automated abuse | The assessment happens when the form is submitted; we do not store the result |
| Server error logs | Technical description of the error, the request address, IP address | Legitimate interest — running and fixing the service | 14 days |
| Public leaderboard | Hero name, score and faction | Performance of a contract | For as long as the account exists |
| Player activity layer on the map | Grid cell identifier (roughly 170 × 170 metres) and the hour a player spent in it; the player identity only temporarily, until the entry is folded into a headcount | Legitimate interest (Art. 6(1)(f) GDPR) — showing that other people play the game too | 6 hours with the player identity, then 7 days as an anonymous count only |
You can object to any processing based on a legitimate interest at any time — see Your rights for how. Measuring how the game is used stays off until you switch it on, and you can switch it off again in the game's Settings whenever you like.
Without your email, password, date of birth and location we cannot provide the game — they are needed to enter into and perform the contract. Without them no account is created, or the game cannot be played. Push notifications and usage measurement are optional and the game runs without them.
Kokume is a game about conquering real territory, so location is not an add-on — it is the game mechanic itself. That is why we process it on the basis of the contract you enter into when you register, not on the basis of a withdrawable consent. The exception is the optional location with the screen off described below — that rests on your consent and is off by default. The app also asks for location access separately in Android; you can revoke that at any time in your phone settings, but the game will then not work.
If you sign in with a Google account, Google gives us your account identifier and your email address. We do not request any other data from Google and we have no further access to your Google account.
We may also receive data about you from another player who reports you — a description of the situation they wrote themselves. We assess such a report and use it solely for moderation; the rules are in the terms of service.
We do not sell personal data and we do not pass it to anyone for advertising or marketing purposes. Apart from us, only these recipients see it, and only to the extent their service needs:
We may also pass data to public authorities where the law requires it or where it is necessary to pursue our legal claims. If you want to know exactly who we passed your data to, write to us and we will tell you.
We do not embed any third-party advertising or analytics package in the game. Usage measurement and error reporting are handled by us, on our own servers.
Our servers and databases are in the European Union. Transfers outside the EU concern only Google services (push notifications, reCAPTCHA, sign-in with Google), where data may also be processed in the United States.
These transfers rely on the European Commission's adequacy decision under the EU–U.S. Data Privacy Framework and, additionally, on standard contractual clauses approved by the European Commission. You can ask for a copy of these safeguards at info@kokume.eu.
Map tiles are loaded straight into your device from content delivery networks that may have servers outside the EU. All that leaves is your device's IP address and which part of the map is being loaded. Avatar images, by contrast, are fetched by our server, so your IP address never leaves for those.
The specific periods for each purpose are in the table above. As a rule, data tied to an account is kept for as long as the account exists and is deleted together with it.
You can close your account in two ways, both leading to the same result:
Once confirmed, we handle the request without undue delay, within 30 days at the latest. We delete the account, game progress, location history, sign-in tokens, push registrations, registration records and anti-cheat records. The following may remain, on these terms:
An account on which nobody starts playing within 30 days of registration — no building constructed, no hero experience gained — is deleted automatically. We send an email warning seven days in advance; just sign in and start playing and the account stays. This clean-up does not touch an account that has been played, even if you take a longer break.
Should a security breach nevertheless occur with a risk to your rights, we will report it to the Office for Personal Data Protection (Úřad pro ochranu osobních údajů) within 72 hours, and where the risk is high, to you as well.
The game automatically assesses whether a reported location is plausible — it compares the distance and time between fixes and rejects a location that would mean an impossibly fast move. This protects against spoofed location that would ruin the game for other players.
The consequence is that a particular location report is rejected and the incident is logged, not an automatic action against your account. Restricting an account, such as blocking it, is always a human decision, and we will always tell you the reason and how to challenge it — the details are in the terms of service. We carry out no profiling and no automated decision-making with legal effects within the meaning of Art. 22 GDPR.
In connection with the processing of personal data you have the following rights:
Send your request to info@kokume.eu. We will handle it without undue delay, within one month at the latest; in complex cases we may extend the deadline by a further two months, which we will tell you about in advance. So that we do not hand your data to a stranger, we may verify that the request really comes from you.
If you think we are handling your data badly, you can lodge a complaint with the supervisory authority: Office for Personal Data Protection (Úřad pro ochranu osobních údajů), Pplk. Sochora 27, 170 00 Prague 7, uoou.gov.cz. We would be glad, though, if you let us know first — most things we can sort out right away.
Kokume is intended for players aged 16 and over. We do not knowingly create accounts for younger players and do not knowingly process their data.
That is why we ask for your date of birth when you register. It is used solely to check that you meet the condition — it is never stored and is discarded once the form is submitted.
If we find that someone younger has created an account, we will close the account and delete the data. If you are a parent and find that your child has created an account anyway, write to us at info@kokume.eu and we will delete the account together with its data.
The kokume.eu website uses no advertising or analytics cookies and does not track visitors. We store nothing on it that is not necessary to run the site — which is why you will not find a cookie consent bar there either.
The game app keeps in its own storage the sign-in token, your settings (including the usage measurement switch) and an installation identifier, which the device fingerprint against multiple accounts is built from. This data disappears when you uninstall the game or clear its data.
We will update this policy whenever the way we handle data changes. Every version carries its number and effective date at the top.
We will tell you about any substantial change at least 30 days in advance, by email or by a notice in the game when you sign in. If the change concerns processing based on your consent, we will ask for that consent again — we will not treat silence as consent. Minor edits, such as fixing a typo or wording something more clearly, will show only as a shifted date.