Privacy in the forest

Vulpes separates private account data from public game identity. This notice describes the intended prototype behaviour and must be completed with deployment-specific contacts and jurisdictional terms before launch.

Account data

We store your username, email, password hash, verification status, accepted policy versions, role, sessions, and last safe position. Passwords and raw session tokens are never stored. Other players only receive your public player ID and username.

World and connection data

Short-lived position, input, region, latency, and connection records operate the multiplayer world and diagnose faults. Live movement checkpoints expire quickly and movement ticks are not written to long-term account storage.

Chat and safety

Nearby chat normally expires after 24 hours. A report may preserve the reported message and limited nearby context while moderators investigate. Closed evidence expires under the service retention schedule.

Email and security

Email is used for verification, password recovery, and essential account security. We use secure cookies, CSRF controls, rate limits, and access logs to protect accounts.

Your choices

You can sign out all sessions, verify your email, change your password, mute or block players, and ask the deployment operator about access or deletion rights.

Return to registration