Crownlands1. Retention principles
Crownlands keeps personal data only for an operational purpose, a shared game record, safety, or a legal obligation. The schedule below describes the current application defaults. A shorter period can be used; a longer period is used only where reasonably necessary for a dispute, security investigation or law.
Crownlands currently has no advertising profile and no third-party product analytics dataset.
2. Current schedule
| Data | Default retention | End of period |
|---|---|---|
| Unverified account | 48 hours after creation | Account and pending verification data are pruned. |
| Email verification code | 15 minutes | Code becomes invalid and is pruned. |
| Password reset token | 30 minutes | Token becomes invalid and is pruned. |
| Signed-in session | Up to 90 days by default | Session expires; logout or security actions can revoke it earlier. |
| Active account, profile and avatar | Until changed or account deletion | Removed during final deletion, except the historical replay name described below. |
| Owned custom maps | Until the author deletes them or deletes the account | Map record is removed. |
| Feedback and its limited context | 180 days | Automatically pruned; authored feedback is also removed at account deletion. |
| Abandoned disposable lobby | 6 hours without participant activity | Lobby is deleted after an advance warning. |
| Abandoned disposable bot match | 72 hours without participant activity | Started game is operationally archived without rating or history; active room is removed. |
| Finished room in live room storage | Approximately 15 minutes | Transient room is removed; the finished replay remains. |
| Finished shared replay and match history | No fixed automatic expiry at present | May remain as the shared record for participants until service cleanup or lawful deletion. Local fallback storage keeps at most the newest 500 replay files. |
| Account deletion request | 7-day cancellation window | The deletion cascade runs after the scheduled time. |
| In-memory rate-limit records | Short request windows | Automatically expire from process memory. |
3. What final account deletion does
| Store | Action |
|---|---|
| Account and authentication | Deletes username mapping, email, Google subject, password hash/salt, account tokens and all sessions. |
| Profile and avatar | Deletes profile fields and uploaded avatar image. |
| Custom maps and feedback | Deletes maps owned by the account and feedback authored by it; clears the account as feedback handler where relevant. |
| Lobby or active game | Removes the lobby participant. In a started game, records a resignation and replaces the stable identity with a non-account tombstone. |
| Finished replays | Removes stable user ID and avatar, marks the participant as a deleted account, removes saved replay analysis, and retains the historical player name and actions. |
| Other players' match history | Removes the stable account ID while retaining the historical opponent name for the shared match. |
Final deletion cannot be undone. The account identity is deleted only after the other stores complete successfully; a failed partial run is retried while the deletion request remains pending.
4. Storage and recipients
Production account, room, map, feedback and replay records are stored in MySQL-backed infrastructure. Application assets and operational logs are handled by the hosting environment. Development and isolated test environments can use local JSON files instead.
Google receives credential verification requests and email delivery data when those features are used. Cloudflare Turnstile receives a challenge token and may receive the requesting IP address for configured anti-bot checks. See the Privacy Policy for transfer information.
5. Data on your device
The web client uses local storage for the session token, guest credential, language, visual and sound preferences, tutorial progress, local map drafts and replay interface preferences. This is functional storage, not advertising tracking.
Logging out removes the signed-in session token. Other preferences and drafts remain until you clear site data. Clearing browser or app storage removes those local copies but does not by itself delete a registered server account.
6. Changes and questions
Operational settings may be shortened as the service evolves. A material extension or new processing purpose will be reflected in this page and the Privacy Policy before it applies where notice is required.
Questions and verified data requests: thecrownlandsgame@gmail.com.