Privacy Policy
Effective November 3, 2026
This policy covers neebo.org, our Minecraft server, and the Neebo community integrations we operate. Visiting the site and playing on the server create records. Here is what those records contain and where they go.
What we collect and why
Website visits
Our web server records connection addresses, request times, requested pages or downloads, response codes, transfer sizes, and error or connection details. A request can include a URL’s query text. These records help deliver the site, troubleshoot problems, and investigate abuse. With a proxy in use, a local log may record the proxy’s address rather than the visitor’s address.
Cloudflare handles website traffic and receives visitor IP addresses and request or browser metadata for delivery and security. The homepage also contacts the Minecraft Server Status API directly from your browser when opened and about once a minute while open. That provider receives your connection/request information and the server address being checked.
The main community pages do not have a Neebo account-registration or payment system. Some older pages load images from Unsplash, which receives the image request and associated browser/connection information. A legacy email form opens your email application; it does not submit to a Neebo order database.
Minecraft
We process Minecraft usernames and UUIDs, connection IP addresses, login results, join/leave events, chat, achievements, deaths, and other game activity. Saves include inventories, progress, statistics, builds and in-game positions. Our death history includes the time, username/UUID, dimension, exact in-game coordinates, and cause of death. These are game locations, not your phone’s GPS location.
We use this information to run the world, save progress, manage whitelist and operator access, help with gameplay issues, recover death locations, and investigate crashes or abuse. Whitelist, username-cache and moderation records may remain after you stop playing. Minecraft authentication and profile lookups involve Microsoft/Mojang; Neebo does not receive your Minecraft account password.
Discord and community tools
Our integrations process Discord account IDs, usernames/display names, membership and role information, button choices, command arguments, and messages involved in their features. Optional region, interest and color roles reflect what you choose. Welcome messages, polls and command replies may be visible to the channel’s audience. Whitelist administration logs include the administrator’s Discord ID and the requested Minecraft name and UUID.
Chat is bridged both ways: Minecraft chat and player events are posted to Discord; messages, display names, reply context and attachment links from the bridge channel can appear in Minecraft and its logs. Community members and players can see and copy that content. Deleting or editing an original message does not automatically update every relayed copy.
Management accounts
People given management access have separate account records, including a username, configured email, password hash, permissions, preferences, login times and addresses, authentication/session records, and audit or command activity. Multi-factor authentication records are stored when configured. These records support sign-in, access control and administration.
Cookies, analytics and browser signals
The community website’s own page code does not set tracking cookies or include a separate advertising or behavioral-analytics tag. Cloudflare can process traffic information and set security cookies; provider-side settings and retention are not fully verified. Management sign-in uses authentication cookies. These are different from a public website account.
The site does not currently change its behavior in response to browser Do Not Track or Global Privacy Control signals. We have not implemented cross-site advertising profiles in the website or custom bots. This statement does not describe how independent providers respond to those signals.
How long information stays
There is no single automatic deletion period for all Neebo information. Website logs, Minecraft logs, death history, game saves, whitelist records, manual backups and incident records can remain until manually removed. Some management and bot logs rotate by size; that does not guarantee deletion after a particular number of days. Management performance history is configured for approximately seven days, but account and audit records are separate.
Discord posts remain subject to channel moderation, user controls and Discord’s policies. Third-party services set their own retention periods, which we have not independently verified. A correction or deletion from the live system may leave older data in archives, backups, logs or recipients’ copies. Leaving the server or removing whitelist access does not automatically erase those copies.
Your choices and privacy requests
Contact candyfreezer, the Neebo owner, in our Discord community to ask what information we hold about you, request a correction, or request deletion. Use a private message where possible. If you cannot message the owner, ask in server-conversation for a private way to contact them; do not post personal details publicly.
Tell us the relevant Minecraft username or Discord account and what you want reviewed. We may need to verify that you control that identity. Do not send passwords, authentication codes or government identification in an initial request.
Requests are handled manually. Deleting game saves can permanently reset progress, so we will clarify the scope first. Some records may need to remain for security, investigations, legal obligations, shared-world integrity or retained backups. We will explain relevant limitations. We cannot promise to erase independent providers’ or other users’ copies; requests to those providers may also be needed.
California users can use this same route. Any additional rights and response requirements under California law depend on the law’s applicability and the circumstances. This policy does not claim that every California consumer privacy law applies to Neebo.
Children’s information
Parents or guardians concerned that a child has provided personal information to Neebo should contact the owner through the route above. Discord participation must also meet Discord’s applicable age requirements. We do not represent that every community member’s age has been verified.
Changes to this policy
We will update this page and its effective date when this policy changes. Check it again when deciding what to share with the community. Separate private applications linked from the site are outside this public community policy.