Milsim.ee Private game publishing and protected play
Legal

Privacy and data deletion

This page explains what account data the website stores, how a user can erase it, and where manual follow-up may still be needed.

Cookie policy
Stored data

What the site keeps

Accounts store a username, optional email, optional display name, password hash, theme preference, rank-related assignments, and authentication tokens needed to keep the portal secure.

Collaboration features also store game memberships, regiment memberships, invite records, game audit events, and game-server runtime records tied to your account or the games you own.

Self-service rights

What you can do in the site

You can already update your email, display name, theme preference, and password from the settings page.

You can also submit a verified account-erasure request from settings. That flow requires your current password and a typed confirmation phrase before anything is deleted.

Erasure scope

What the automated deletion flow removes

Direct account data
The user record, password reset tokens, API tokens, sessions stored in the database, and current sign-in state.
Owned game data
Games you own are permanently removed together with their memberships, invites, published artifacts, draft files, thumbnails, builds, server records, logs, and audit trail linked to those games.
Invite records you created elsewhere
Invite links you created for games you do not own are deleted so your account is no longer attached to those invitation records.
Shared regiment ownership
Regiments you own become unclaimed instead of being deleted, so the shared regiment record can be claimed or managed by someone else later.
Audit references
Where a surviving audit event stores your user ID inside metadata, the automated erasure flow clears that direct identifier.
Manual review

What may still need administrator review

Some collaborative or operational records can contain free-text names supplied by players or game servers, especially chat logs and admin logs for games you do not own. Those entries are not always safely attributable to a single account record, so they may require manual review if a user asks for deeper redaction beyond direct account-linked data.

Privacy contact: hello@example.com

Cookie settings

Choose how cookies work on this site

Essential cookies keep authentication, CSRF protection, sign-out, and your saved cookie choice working. Optional cookies stay off unless you explicitly allow them, and none are active in the current build.

Read policy