Player privacy

Agent defaults continue to collect player data. Set collect-player-data: false to keep performance snapshots and aggregate player counts while suppressing join/leave events, session metrics, pings, proxy switches, extensions and geolocation. Environment override: SERVERSPULSE_COLLECT_PLAYER_DATA; JVM override: -Dserverspulse.collect-player-data=false.

For pseudonymous player history, set hash-player-identifiers: true. Environment: SERVERSPULSE_HASH_PLAYER_IDENTIFIERS; JVM: -Dserverspulse.hash-player-identifiers=true. JVM properties override environment, which overrides YAML. Defaults are true for collection and false for hashing.

The agent persists a random HMAC key in player-identity.key in its resolved data folder. UUIDs become deterministic UUID-shaped pseudonyms; usernames become 16-character pseudonyms derived from UUIDs. Back up and protect the key. Deleting it breaks history continuity; rotating the API key does not. Do not copy this key between servers. Someone possessing it can test known UUIDs, so these are pseudonyms rather than anonymous identities. Proxy/backend identities cannot be correlated across different keys. Hashed mode also suppresses extensions, geolocation and join hostnames to avoid free-text identity leaks.

The agent reports performance_only and hashed_player_identifiers in its capability metadata. On the server settings page, disabling Collect player data drops player events, sessions, switches, extensions and snapshot pings even from older agents. The setting is checked directly in the database at ingestion so API-key cache entries cannot postpone it. Existing history remains accessible; player and network pages explain that new collection is disabled. Discover still uses aggregate server status; new player-derived analytics stop updating.

The server setting is collectPlayerData in the existing owner-authorized server PATCH API. It defaults to true. These settings do not remove historical data or redact arbitrary custom telemetry: do not include personal information in custom names, events or annotations. Configure the agent as well as backend enforcement to avoid transmitting player data at all.