Crownlands
1. Who controls your data
Crownlands is operated by Kiryl Yasinski in Lithuania, who is the controller for personal data described in this policy.
Privacy requests can be sent to thecrownlandsgame@gmail.com. Please do not send a password, session token or Google credential by email.
2. Data we process
| Category | Examples | Source |
|---|---|---|
| Account and sign-in | Username, email, email verification state, password salt and hash, Google account subject identifier, session token and timestamps | You, Google Sign-In and the service |
| Profile and content | Profile text, location you choose to publish, avatar or uploaded image, custom map names, descriptions and map data | You |
| Gameplay | Room membership, match state, actions, results, ratings, match history, replays and replay analysis | Your play and server game rules |
| Support and safety | Feedback message, category, source hash, limited app/release context, account name, status and moderator notes | You and service administrators |
| Technical and security | IP address used for rate limits and anti-abuse checks, request timing, error and operational events | Your device and hosting infrastructure |
| Device-local settings | Language, theme, piece style, sound, tutorial progress, map drafts, guest credential and signed-in session token | Stored in your browser or app storage |
Crownlands does not currently integrate advertising trackers or third-party product analytics SDKs. Functional browser storage is used to keep you signed in and remember your settings.
Usernames, profile fields you publish, public maps, ratings and selected match information can be visible to other players. A shared finished replay can contain the historical player name used in that match.
3. Why we process data
Provide the service and perform our agreement
We use account, profile, map and gameplay data to create accounts, authenticate users, run rooms and matches, calculate results, show profiles and preserve shared replays.
Legitimate interests
We process limited technical, security and feedback data to prevent abuse, diagnose failures, protect accounts, enforce game rules and improve reliability. We balance these interests against user rights and keep the data limited to what is needed.
Legal obligations and consent
We may retain or disclose information where law requires it. Optional Google Sign-In and optional profile fields are initiated by you and can be removed by deleting the account or editing the profile, subject to shared replay history described below.
5. How long data is kept
Account data remains while the account is active. Sessions expire after up to 90 days by default; unverified accounts expire after 48 hours; feedback expires after 180 days. A confirmed deletion request has a seven-day cancellation window.
Finished shared replays do not currently have a fixed automatic expiry because they form the match record for all participants. After account deletion, stable account identifiers and avatars are removed from those replays, but the historical player name and game actions remain.
See the complete current schedule in Data & Retention.
6. Your choices and rights
Depending on applicable law, including the GDPR, you may ask to access, correct, erase, restrict or receive a portable copy of your personal data, and you may object to processing based on legitimate interests. You can edit public profile fields and delete your account through Account Settings.
We may need to verify that a requester controls the relevant account. You may complain to the Lithuanian State Data Protection Inspectorate or your local supervisory authority.
7. Account deletion
In the web game, open your profile, choose Account settings, then use Delete account. Confirm with your current password or the linked Google account. Final deletion occurs seven days later unless you cancel.
The process removes sign-in data, profile data, avatar, owned custom maps, sessions and authored feedback; removes you from lobbies; and records a resignation in active matches. Finished shared match records retain only the historical player name and gameplay needed by the other participants.
8. Security
Crownlands uses salted password hashing, limited-lifetime sessions, verified email flows, encrypted transport, request limits and restricted administration. No system is risk-free, so please use a unique password and report suspected account compromise promptly.
9. Age
Crownlands is for users aged 13 and older and is not directed to children. If local law requires parental authorization for a minor to use an online service, that authorization must be obtained before creating an account. Contact us to request deletion of a minor's data.
10. Changes and contact
Material policy changes will be published here with a new effective date. Where appropriate, notice will also be shown in the service.
Controller: Kiryl Yasinski, Lithuania
Email: thecrownlandsgame@gmail.com