Privacy & your ARVEE data.

This page explains the platform’s technical data handling. Before a public launch, the ARVEE operator must add their legal identity, complete retention schedule, and applicable privacy details.

Discord sign-in

ARVEE requests your Discord identity and server list. The server list is used to check which servers you can manage and whether ARVEE is installed. Access and refresh tokens stay on the secure service, encrypted at rest. They are not returned to your browser.

Your game account

The Discord and browser RPG use the same ARVEE player record. Gameplay actions are checked by the authoritative bot service. Private profiles and sandbox characters are excluded from the Hub’s public leaderboards.

Minecraft linking

Linking requires an expiring one-time code issued inside an authenticated Minecraft session by an installed ARVEE bridge. A Minecraft username alone cannot establish account ownership. Statistics shown in the portal come from connected server adapters; unsupported data is left unavailable.

Settings, logs & support

Server configuration changes and sensitive staff actions are recorded in an audit history. Reports contain the text you submit. Support tickets in Discord are a separate system and may have their own retained messages and attachments.

Access or delete your data

Account deletion is available in the Discord bot under /settings → Privacy → Delete account. Existing backups, logs, Discord/support content, and payment-provider records require separate handling. Contact the ARVEE team through Discord support to request access, correction, or erasure across those systems.

Signing out revokes your current Hub session. Return to your dashboard →