Privacy Policy

Kaelmoor.io · Last updated: 3 August 2026
The short version. Kaelmoor.io has no accounts, no sign-up, no email collection, no tracking, no analytics and no advertising. To play, your browser connects to our server, which necessarily sees your IP address. Your settings stay in your own browser. That is all of it.

1. Who is responsible for your data

The controller of the personal data described here is Daniel Kiss, contactable at kaelmoor.io@gmail.com.

If you have any question about this policy, or want to exercise any of the rights in section 8, write to that email address. We answer within one month.

2. What we process, and why

DataWhere it comes fromWhy we need itHow long
IP address Automatically, from your connection Unavoidable: it is how the internet delivers the game to you. Also written to server logs so we can diagnose faults and identify abuse or attacks. Logs are kept no longer than 30 days, then deleted
Kingdom name You type it before joining It is shown to other players on the map, the leaderboard and the final standings. Choose a name that does not identify you and it will not identify you. Held in memory during the match only. Gone when the match ends or the server restarts
Chosen people / race You pick it in the menu It decides what your kingdom can build Same as above
Game state (territory, troops, buildings) Generated as you play It is the game Memory only. Never written to disk, never kept after the match

There is no chat. Kaelmoor.io deliberately has no text chat, no private messages and no free-form profiles. Teams coordinate with map pings, which use a fixed set of phrases the server itself writes. Nothing you type is ever shown to another player except your kingdom name.

3. What we do not do

4. Cookies and local storage

Kaelmoor.io sets no cookies. It stores a handful of preferences in your browser's local storage, which never leaves your device and is not readable by us:

These are strictly necessary functional settings, so no consent banner is required for them. You can clear them at any time through your browser's site-data settings.

5. Legal basis

We rely on legitimate interests under Article 6(1)(f) GDPR: operating the game you asked to play, keeping the service available, and protecting it from abuse and attack. We have weighed this against your interests and consider it proportionate, because the processing is the minimum the service cannot function without, and because nothing is used for any secondary purpose.

6. Who else sees it

Our hosting provider necessarily processes the traffic that reaches the server, acting as our processor under a data processing agreement. Nobody else. We use no advertising network, no analytics provider and no third-party service inside the game.

7. Children

Kaelmoor.io is not directed at children under 16. We do not knowingly process the data of anyone under 16. Since we ask for no personal details at all, the only thing a child could reveal is a kingdom name — please do not use your real name. If you believe a child's data has reached us, write to the address in section 1 and we will delete it.

8. Your rights

Under the GDPR you have the right to:

An honest limitation: because the game has no accounts, we normally cannot connect an IP address in a log to a particular person, and we will not collect extra data in order to try. If we cannot identify you from what we hold, we may be unable to act on a request — Article 11 GDPR. In practice, log entries expire within 30 days regardless.

Our supervisory authority is the Slovak data protection office — Úrad na ochranu osobných údajov Slovenskej republiky, Hraničná 12, 820 07 Bratislava. You may also complain to the supervisory authority in your own country of residence.

9. Security

Traffic is encrypted in transit (HTTPS and WSS). The game keeps no database: match state exists only in the server's memory and is destroyed when the match ends. The less we keep, the less there is to lose.

10. Changes

If this policy changes, the date at the top changes with it. If we ever begin processing data for a genuinely new purpose — advertising is the obvious candidate — we will say so here before it starts, and where consent is required we will ask for it first.