Last updated: 6 November 2026
This Privacy Policy describes how ARVEE collects, uses, shares, stores and deletes personal data when you use our website, ARVEE Hub, connected Discord bot and RPG features, and supported Minecraft integrations (together, the “Services”). It also explains your rights under applicable data protection law, including the EU General Data Protection Regulation (GDPR). Third-party services have their own privacy policies.
ARVEE is a community project operated by private individuals, not a registered company. The public privacy contact for ARVEE is Isadev, based in the Netherlands. The individual operators who decide why and how ARVEE processes personal information are responsible for that processing. For privacy questions or controller identification and correspondence details, email privacy@arvee.world. Services such as Discord may be independent controllers for the data they handle under their own policies.
We only seek information that is relevant to delivering, supporting and securing the Services. The following categories describe our main purposes and the corresponding GDPR lawful bases. An OAuth permission screen does not, by itself, mean that consent is the GDPR legal basis for every use of the resulting information.
Data: Random tab-session identifiers, grouped pageviews, external referrer hostname, broad device/browser/operating-system families, time engaged, community-link actions, performance measurements and error categories. No message contents, raw IP addresses, Discord IDs, share tokens, URL query strings, error messages or stack traces are retained in this analytics dataset.
Purpose: Understand website usage and improve performance and navigation. Operational API counts, timings and response-status groups are measured separately without visitor identifiers.
Legal basis: Consent for optional browser measurements, which you can withdraw below; legitimate interests in reliability for aggregate operational measurements.
Data: Discord user ID, username, display name, avatar, authorised guild/server list, relevant role or permission information, login timestamps, OAuth access and refresh tokens where issued.
Purpose: Sign you in, maintain secure sessions, identify servers you can manage, and enable authorised dashboard features.
Legal basis: Contract necessity (Article 6(1)(b)) for account features; legitimate interests (Article 6(1)(f)) for protecting sessions and preventing abuse.
Data: ARVEE player ID, linked Discord ID, progress, inventory, achievements, settings, gameplay actions, activity records and leaderboard eligibility.
Purpose: Operate the shared game account, validate gameplay through the bot service, save progress, provide features and show eligible public rankings.
Legal basis: Contract necessity (Article 6(1)(b)); legitimate interests (Article 6(1)(f)) in integrity, anti-cheat and abuse prevention.
Data: Minecraft username and UUID, linked ARVEE/Discord account identifiers, one-time verification codes, connection and gameplay statistics supplied by installed server adapters.
Purpose: Verify Minecraft account control, connect accounts and display only data supported by connected Minecraft servers.
Legal basis: Contract necessity (Article 6(1)(b)); legitimate interests (Article 6(1)(f)) in account security.
Data: Support subjects, messages, replies, request status, relevant account identifiers, private staff notes, reports and moderation records.
Purpose: Respond to requests, investigate reports, protect community members and maintain an accountable support workflow.
Legal basis: Contract necessity (Article 6(1)(b)) where support relates to the service; legitimate interests (Article 6(1)(f)) in support and safety; legal obligation (Article 6(1)(c)) where applicable.
Data: Discord account identity, selected volunteer role, experience, motivation, availability, optional public portfolio link, review status and internal reviewer notes.
Purpose: Review voluntary applications and communicate outcomes through Discord. Applications are visible only to the ARVEE owner and are not published publicly.
Legal basis: Consent (Article 6(1)(a)) for submitting application details; legitimate interests (Article 6(1)(f)) in managing community volunteering.
Data: IP addresses, device/browser information, request times, errors, relevant event and access records, configuration changes and sensitive staff actions, to the extent logged by our systems.
Purpose: Keep ARVEE operational, troubleshoot incidents, prevent attacks, limit access and review privileged actions.
Legal basis: Legitimate interests (Article 6(1)(f)) in service reliability and security; legal obligation (Article 6(1)(c)) where applicable.
Where we rely on legitimate interests, these include protecting accounts and players, enforcing permissions, investigating misuse and operating reliable services. We must balance those interests against your rights and interests. Where a processing activity requires consent, we will ask for it separately and allow withdrawal without affecting processing already lawfully carried out.
We obtain information directly from you, from your interaction with ARVEE, from Discord when you authorise its connection, from authenticated Minecraft server integrations, and from other users who submit relevant support or abuse reports. We do not treat a Minecraft username alone as proof of account ownership.
Discord authentication information is needed for Discord sign-in. Certain gameplay records are needed to maintain progression, and Minecraft identifiers are needed only if you choose to link a Minecraft account. You can choose not to use optional features, but the corresponding functionality may then be unavailable.
ARVEE uses Discord authentication to identify your account and, where authorised, read the list of servers you belong to so that we can identify servers you have permission to manage and check whether the ARVEE bot is installed. Access and refresh tokens are held server-side and are designed to be encrypted at rest; they are not intentionally exposed to your browser. Access to dashboard functions is checked server-side.
Signing out ends your current Hub session; it does not necessarily delete your RPG account, unlink Minecraft, delete Discord messages, or immediately erase server logs. You may also manage app authorisations in Discord. Discord separately handles personal information according to its Privacy Policy.
The browser RPG and Discord RPG use a shared ARVEE player record. Gameplay actions are checked by the authoritative bot service. Eligible account names and game statistics may appear in public leaderboards. Private profiles and sandbox characters are excluded from the Hub’s public rankings. Other players may still see information that you choose to share inside the game or Discord.
Linking requires an expiring, one-time code generated during an authenticated Minecraft session using an ARVEE bridge. Only supported data supplied by connected Minecraft adapters is displayed. Unavailable or unsupported statistics are not fabricated. Unlinking an account and deleting account history are separate operations and may require a privacy request.
We keep information only for as long as needed for the purpose for which it was collected, including necessary security, dispute resolution and legal requirements. Different systems have different retention periods. Account deletion does not necessarily remove information from independent Discord systems or from all backups immediately.
| Data category | Retention period / criteria |
|---|---|
| Sessions and Discord tokens | Hub login sessions expire after seven days, or sooner when you sign out. OAuth sign-in state expires after ten minutes. Expired session and OAuth records are cleaned up periodically. Discord access tokens may be refreshed only while a Hub session is valid. |
| Account, RPG and Minecraft-link records | Account, linked Minecraft and RPG progression records are used while the corresponding account is active. You may request account deletion at any time. The available code does not establish a separate automatic inactivity-deletion deadline; legal or abuse-prevention exceptions may apply. |
| Website support conversations and staff notes | Website support conversations and private staff notes remain available for the support workflow while required, and account deletion removes reports owned by that account. The current Hub source does not define a fixed time-based purge for ordinary support conversations. |
| Volunteer team applications | Volunteer applications contain role preferences, experience, motivation, time availability, and optional public portfolio links. Applicants may withdraw and delete pending applications. Other submissions remain for review until deleted by the operator or through account erasure; a fixed automatic purge period is not implemented. |
| Staff actions and security audit events | Discord guild module action records, relevant guild audit events and closed/failed ticket metadata are removed after 30 days. Other website security and staff audit records do not have a single verified automatic retention period; the deletion workflow anonymises certain records when a user account is erased. |
| Server access and diagnostic logs | Hub service-status samples are purged after seven days. Retention for Mac web access/error logs, Discord bot logs and Minecraft server logs depends on their actual configuration and has not yet been verified as a single fixed period. |
| Encrypted or otherwise protected backups | Backup copies may temporarily retain deleted information until the corresponding backup is removed or replaced. The current backup rotation and deletion interval has not yet been verified, so no specific duration is claimed. |
Where a lawful exception applies, such as an unresolved abuse investigation or a legal obligation, we may preserve only the necessary records for the applicable period. Backup deletion also depends on the actual rotation schedule. We do not currently publish a backup deletion period that has not been independently verified.
You can request deletion through the Discord bot at /settings → Privacy → Delete account, or contact us using the privacy details below. The current website support deletion workflow removes conversations and request receipts owned by the deleted account; messages you authored in another user’s conversation are replaced with a deletion notice. Where applicable law requires or permits some data to remain, we limit the retained information accordingly.
Discord support tickets and Minecraft server logs are separate systems and may contain messages, files or connection details not held by the website. Requests can also cover those systems. Independent platforms may need to be contacted separately; we will explain what action ARVEE can take and any applicable legal exceptions.
Analytics stays off until you allow it. We respect Do Not Track and Global Privacy Control signals. You can change your choice here at any time; turning it off stops new optional measurements and removes the tab identifier. Analytics is disabled inside the Discord Activity. We do not use this data for advertising or join it to your Discord account.
Consented visit and event data is retained for 30 UTC calendar days, including today. Aggregate API operational totals are retained for 90 UTC calendar days. Daily cleanup removes older records while the service runs. Historical measurements already recorded cannot be linked back to an account after the random tab identifier is removed.
Optional website analytics: off.
We use technical and organisational measures intended to reduce risks, such as access controls, server-side checks, encrypted transport where configured, token protection and relevant audit logging. No online service can guarantee absolute security. If we become aware of a personal-data incident, we assess and respond to it under applicable data-protection requirements, including notifications where legally required.
Subject to applicable conditions and exceptions, you can request access to your data, correction, deletion, restriction of processing, data portability, and object to processing based on legitimate interests. Where processing is based on consent, you may withdraw it at any time. You can also object to direct marketing, if used.
Send your request to privacy@arvee.world or use ARVEE Discord support. We may need reasonable proof of account ownership before disclosing or changing information. We generally respond within one month, subject to permitted extensions. Exercising your rights is normally free, although the GDPR provides limited exceptions.
You have the right to complain to your competent data protection authority. In the Netherlands, this is the Autoriteit Persoonsgegevens.
Our Services may be used only in accordance with the age rules of the applicable game platforms and local law. Where parental authorisation is required for consent-based processing, we must obtain valid authorisation before proceeding. Please contact us if you believe a child’s information is processed without the required legal basis.
Automated game rules, anti-abuse checks and permission checks may determine whether a gameplay action or website function is allowed. You can contact us to ask about or challenge an access restriction. If ARVEE introduces decision-making that has legal or similarly significant effects within the meaning of GDPR Article 22, we will provide the additional notices and safeguards required by law.
We may update this policy as our Services or legal obligations change. We publish the revised policy with an updated date and, where appropriate, give additional notice about material changes. An updated policy does not remove rights you have under law.
Project: ARVEE (run by private individuals, not a company)
Privacy contact: Isadev
Country: the Netherlands
Email: privacy@arvee.world
Community support: ARVEE Discord