Privacy and data
Last Command runs on enterprise-grade cloud infrastructure with data hosted in the EU. Alliance data is scoped per alliance — no member can see another alliance's data, and officers see their own alliance only. Every member has an export-and-delete flow on their profile that satisfies GDPR data-subject access requests.
What we store
For each member, the platform stores: in-game name, rank, the contribution data the alliance has chosen to capture (donation rankings, VS rankings, DS attendance, Marshal's Guard scores, hero builds, power snapshots), and the email address you signed in with.
For each alliance, we store: alliance name and tag, server number, branding, and the configuration described in Alliance settings. We also keep a short audit trail of officer actions (rank changes, member removals) for diagnostic purposes.
// NOTE
Who sees what
- Officers (R5/R4) see everything within their own alliance — Pulse, metrics, donations, attendance, hero data — but never another alliance's internal data.
- Members (R3 and below) see the public alliance overview, the schedule, the rankings, and their own personal data. They don't see Pulse, Metrics, or other officer-only views.
- Public visitors see only what your alliance opts into — the public marketing site, the docs you're reading now, and (if opted in) your alliance's entry in the server directory.
Export and deletion
Every member can export their personal data as a JSON archive from Settings → Privacy → Export my data. The archive contains your profile, all alliance memberships, and all attached records (donations, attendance, etc).
You can request account deletion from the same panel. The deletion runs asynchronously — your account is anonymised immediately, and the underlying records are scrubbed within a few days. Officers see deleted accounts as “[deleted]” on historic data.
Alliance-level deletion (R5 only) is in Settings → Danger zone → Delete alliance. It removes the alliance, all per-alliance member records, and all attached data. It can't be undone, and it ignores per-member deletion requests already in flight.
Public server-directory listing
The public server directory shows alliance name, tag, R5 leader name, member count, and total power for alliances that've opted in. It's opt-in per alliance from Settings → Server directory. When opted out the alliance simply doesn't appear there.
Active NAPs are public by default since they shape diplomacy across the server, but each individual NAP has a “hide” flag if officers want to keep a particular arrangement off the public chip list.