Crown City

Privacy policy

Updated 14 September 2026 · English

Crown City is published by Richard Elms, who is responsible for the player data described here. Contact: richardelms@gmail.com.

Single-player test version

The separately labelled single-player test runs matches on your device. It does not connect to our multiplayer server, create a multiplayer guest profile, or send match actions, scores or progression to our database. Round results are temporary. Nickname, language, audio and controls preferences can still be stored in your browser. When hosted on Poki, the platform SDK and its fixed loading/gameplay checkpoints described below remain active.

What the multiplayer game uses

You can play as a guest without supplying an email address or creating an account. Please use a nickname rather than your real name.

• Guest profile: a random browser identifier, stored as a hash in our database; the platform you play on; nickname; first and latest visit; session count; XP, level and cosmetic choices.
• Game records: daily-contract progress and round statistics, including kills, deaths, crown time, crown takes, position and whether touch controls were used.
• Gameplay diagnostics: server-observed match admissions, capacity rejections, round starts and ends, disconnects and reconnects; timestamps, match identifiers, human/bot counts, touch-control use, server build and limited round outcomes. Hashed guest and browser-session identifiers help us compare completion and subsequent rounds. These records do not contain raw nicknames, guest tokens, IP addresses or continuous movement histories.
• During a match: movement and actions are sent to the authoritative game server. Other players see your nickname, appearance and match information.
• Connection information: our hosting provider processes network information such as IP addresses to deliver and protect the service. Operational logs help diagnose connection errors and faults.

We use this data to run multiplayer matches, remember earned progress and preferences, diagnose problems, and understand how players start, complete and replay rounds so we can improve the game. Our legal basis is our legitimate interest in providing and maintaining these requested game features and a reliable service. You can object to processing based on legitimate interests by contacting us.

Optional development performance diagnostics

Local development enables coarse timings for renderer readiness, loading-screen dismissal, server welcome and the first game-state update. One small report is sent through the existing game connection after successful admission. It flags whether the page was observed in the background or the loading screen timed out. These records have no attached guest, session or match identifiers, resource URLs, browser/device details or IP addresses; receipt times are rounded to the hour. They use the same 30-day diagnostics cleanup and help identify slow loading. No additional browser storage or third-party analytics service is used.

This optional collection defaults off in distributed builds and on the server. Before enabling it for public players, we will complete the applicable privacy and device-access assessment, update this notice, and provide any required consent or objection controls.

How long records are kept

• Profiles, XP and cosmetics: deleted after 12 months without playing.
• Round statistics, gameplay diagnostics and daily-contract history: deleted once older than 30 days. Removing this history does not remove earned XP or cosmetics.
• Cleanup: runs at startup and daily, normally removing eligible records within the following 24 hours. Contract history uses UTC calendar dates. A service outage can delay cleanup until it recovers.
• Operational application logs: retained by Railway for seven days on our current hosting plan.
• Backups: scheduled database backups are not currently enabled. The selected policy for daily backups, when enabled, is six days; deleted records can remain in a backup until it expires.

Storage in your browser

The game uses local storage for the guest identifier, nickname, language, audio preferences and first-play settings. These stay until you clear site data or your browser removes them. Clearing site data may prevent us from recognising your saved profile; it does not itself delete server records. If browser storage is unavailable, persistent guest recognition may not work.

When played on Poki, the game loads the official Poki SDK and reports loading completion and gameplay start/stop events to the platform. It also reports fixed gameplay checkpoints: Play and Replay button use, round starts and completion or explicit departure, and first crown acquisition and car use in each round. These help Poki measure loading and engagement. These checkpoint values do not contain your nickname, guest identifier, position or free text. This integration does not request advertisements or rewards. Poki handles platform data under its privacy statement. The standalone build does not load the Poki SDK. We do not sell player data.

Hosting and contact services

The game server and player database are hosted with Railway in Amsterdam, EU West. Railway provides the infrastructure and may process service and security metadata under its privacy policy. Its data-processing terms describe international processing and safeguards. An EU server location does not mean every provider operation takes place in the EU.

If you email us, your message and email address are handled through Gmail to respond to your request. We keep correspondence only as needed to resolve and document the request or meet applicable legal obligations. Please do not send passwords or your game's guest token. A website or platform hosting the game may also process data under its own privacy policy.

Your choices and rights

Contact richardelms@gmail.com to request access, correction, deletion, restriction or a portable copy of your data, or to object to processing, where these rights apply. Because profiles are guest-based, we may need additional information to locate your records and verify that they belong to you. A nickname alone may not uniquely identify a profile.

You can also complain to your local data-protection authority. See the European Commission's explanation of your rights. Parents or guardians may contact us about a child's data.

We will update this notice if the game's data practices change. The date above identifies the current version.