Nexus MC Hosting Team
Privacy Policy
Last updated: November 5, 2026
Who this policy covers
This page explains how the Nexus MC public Discord bot and its connection to the Nexus MC website and Minecraft server tools process information. The public operator name is Nexus MC Hosting Team. The legal completion note below identifies operator details that have not yet been supplied.
Information the bot handles
- Discord server setup: Discord server (guild) ID and name, the server owner's Discord ID, the linked Nexus account and Minecraft server, and setup-code records. Setup codes stop working after 15 minutes.
- Channel availability: while the bot is online, it reports server and text-channel IDs and names, whether it can view or send messages in each channel, and whether Discord message content access is enabled. The API keeps this heartbeat snapshot in memory for connection diagnostics; it is refreshed regularly and is not written to the database by that endpoint.
- Commands and permissions: the Discord user ID and server ID are checked when someone uses a command. Command names and results are written to operational logs. The bot uses the linked server's permission records and, where relevant, the Nexus account's subscription status to decide what the user can do.
- Server controls: requested operations, such as checking status or sending a server-control command, may include the user ID, operation, command text, and result in a queued job or operational log so the connected server can process the request.
- Chat bridge: the bot sends eligible human messages it can read, along with the sender's display name, to the Nexus API for routing checks. Messages from the configured bridge channel may be relayed into Minecraft. The bot is not intended to create a searchable Discord chat archive, but message text can appear in a queued job or operational log while it is being processed.
The public bot does not build a complete list of every Discord member. It processes a person's Discord ID when checking that person's command permissions. Avoid placing the bot in sensitive channels or enabling the chat bridge where messages should not be relayed.
How information is used
Nexus MC uses this information to connect a Discord server to a Minecraft server, check command permissions, show server information, process authorized controls, relay messages when the chat bridge is enabled, troubleshoot failures, and protect the service from misuse.
Where information is processed
- Discord: Discord operates the bot platform and processes Discord accounts, servers, messages, and interactions under its own Privacy Policy.
- Nexus MC and Supabase: the Nexus website/API processes integration records and server requests. The production app uses Supabase PostgreSQL for its database.
- Replit: the website and API run on Replit. The application writes command events to operational logs; this app does not set a fixed log-retention period.
- Tebex: if you buy a subscription, Tebex handles checkout and payment. The Nexus bot/API uses subscription status for access checks; the bot does not receive your payment-card details.
Nexus MC does not control the privacy practices or retention settings of Discord, Supabase, Replit, or Tebex. Their own policies and service terms also apply.
Storage, expiration, and deletion
Linked-server settings and permission mappings are stored in the service database. Disconnecting a server from the Nexus website removes its link and member-permission mappings. The app does not currently provide a self-service delete tool for all bot-related information.
Nexus MC has not established a fixed retention schedule. Setup codes become unusable after 15 minutes. Queued official-server jobs expire after two minutes, but expiry does not mean the database record is automatically erased. Command events are written to operational logs, and the app does not define how long those logs are kept. The service therefore cannot promise an exact deletion date for every record.
To ask what information is associated with your Discord server or to request a correction or deletion, join the official Nexus MC Discord support server and contact the team. Do not post private information in a public channel. Requests are reviewed individually; some information may remain in logs, backups, or records needed to operate or secure the service.
Security and changes
Nexus MC uses access checks and encrypted connections where supported by the service, but no online service can guarantee perfect security. This page will show the date of its latest update. Check it again if the bot or its data practices change.
Contact
For privacy questions, use the official Discord support server. A separate legal contact email has not been provided.