PLAYER DATA, EXPLAINED
Privacy Notice
Cube Survival uses the minimum practical data needed to secure accounts, operate the game, fulfil optional purchases, moderate fairly, and recover from incidents. Last updated August 16, 2026.
Data we use
Why we use it
- Authenticate the correct player without storing a password.
- Connect website purchases and benefits to the intended Minecraft identity.
- Prevent abuse, investigate griefing or fraud, and apply the community rules consistently.
- Monitor reliability, create recovery points, and diagnose service incidents.
- Meet payment, accounting, security, and legal obligations that apply to the operator.
Sharing and processors
Data is shared only where needed to operate the service—for example Mailgun for transactional email, Airwallex for payment processing, and infrastructure or backup providers for hosting and recovery. We do not sell player personal data. Public chat, builds, and player names may naturally be visible to other players inside the game.
Retention and security
Retention depends on purpose: short-lived login codes expire quickly; sessions have defined expiry; payment, audit, moderation, and backup records may be kept longer for security, dispute, recovery, or legal needs. Access is restricted by role, sensitive credentials are not returned to browsers, and payment delivery is separated from payment verification. No internet service can promise absolute security.
Your choices and requests
You may ask about, correct, or request deletion of eligible account data, or raise a privacy concern. Sign in and use the monitored support address displayed in your player dashboard. Some records may need to be retained when required for security, disputes, accounting, or law. Parents or guardians may use the same channel for a child's account concern.
Cookies
The account system uses a secure, HttpOnly session cookie that is necessary to keep you signed in. Cube Survival should obtain any consent required before adding non-essential advertising or analytics cookies; none are required for the core account flow described here.