Security & Privacy

How K4068 protects citizens

The portal is designed so that identity, ownership, and performance data are separated — and privileged data is only accessible to roles that require it.

  • Citizens cannot access DKP until a Governor is verified

    Provisional accounts see only the claim flow. No power, kills, deads, or DKP is revealed before verification succeeds.

  • Citizens cannot view other citizens' private data

    Leaderboards are positive-only. Deads, negatives, and personal notes are never shown across citizens.

  • Council is read-only for DKP

    Council can view scans, filter, and generate DM lists — but cannot edit DKP, thresholds, or verification outcomes.

  • Raw StatsMaster XLSX and payment details are admin-only

    Only Admins/King can access source XLSX files, uploader identity, and any support/donation records.

  • Every privileged action is audited

    Imports, verifications, bans, transfers, role changes, DM generation, and admin reads write to an immutable audit log.

SUPPORT INDEPENDENCE

Support and donations never affect DKP, rewards, migration priority, MGE priority, council influence, or requirements. Ever.

Verification code handling

Codes are generated server-side, hashed, and stored with a 12-hour TTL. Only the hash is persisted. Wrong entry locks the claim and requires King review. One attempt per claim.