Privacy information.

How this website is designed to handle your account and whitelist application.

Pre-launch privacy draft. Operator identity, contact route, legal basis, retention schedule and hosting arrangements must be confirmed before public launch.

What the website collects

Discord sign-in provides a stable Discord account ID, display name, and profile image when available. We use these to identify your account and show your profile. We do not ask for your Discord password or personal email address.

Your application includes your stated Minecraft edition and Java username or Bedrock gamertag, motivation, interests, play style, any optional information you share, and acknowledgements of the rules and privacy information. Please do not include sensitive or unnecessary personal details.

Why this information is used

Account information supports sign-in and access control. Application information supports manual community review, applicant messages, and application history. When account linking is enabled, a short-lived code proves control of your Minecraft account in-game. We then store its UUID, edition and profile name, together with requested and confirmed Member access for Minecraft and Discord. Only a hash of an unused link code is stored, and codes expire after ten minutes.

Who can see it

You can see your own application and messages shared with you. Authorised reviewers and administrators can access application information needed for their roles. Internal staff notes and security audit history are restricted to authorised staff. Application text is not published as public site content.

Cookies and service providers

This website uses necessary session and authentication cookies. The first release has no analytics pixels, marketing cookies, or advertising tracking. Discord handles its own authorisation page under its own privacy policy. Hosting and database providers must be documented before deployment.

Storage and retention

Account records, application decisions, and limited audit events are stored in the website database. Operational guidance proposes regular review and deletion of information that is no longer needed; the final retention periods must be approved before launch. Backups may retain deleted records until their rotation expires.

Your choices and requests

You may withdraw an eligible application through your player area. Withdrawal changes its status; it does not immediately delete its historical record. To request access, correction, or deletion of your data, contact the HoneyCraft operator through the official community support route once published. Staff must verify ownership before acting on a request.

Before public launch

This draft is not a completed legal assessment. The operator must publish an identifiable contact, confirm the applicable privacy basis and rights, select retention periods, and review provider and international-transfer arrangements before accepting public users.