This bot (“the Bot”) is a Discord application that runs DiscordSRV, an open-source plugin that builds a two-way bridge between our Minecraft server and a set of channels in this Discord community. It copies chat and events between the game and Discord so that both sides can talk to each other in real time.
This policy explains what content the Bot handles, what it keeps, why, for how long, and what choices you have.
Who operates the Bot
The Bot is operated by our server administration team for the single Minecraft and Discord community where it is installed. It is not a public, multi-server product that you can invite elsewhere.
DiscordSRV itself is free, open-source software. The developers of DiscordSRV do not receive your data — the plugin runs entirely on our own server, and only our administrators control it.
For privacy questions or data requests, contact the server administration team through the community’s designated support or moderation channel.
How the bridge works
DiscordSRV connects two places you already use:
- In-game chat → Discord: When you type in Minecraft chat, the Bot posts a copy of that message into the linked Discord channel, usually with your Minecraft username and player-head avatar.
- Discord → in-game chat: When you send a message in the linked Discord channel, the Bot relays it into Minecraft chat so players in the game can read it.
- Server events: Join, leave, death, and (optionally) advancement messages from Minecraft may be announced in Discord.
- Console channel (staff only): Where enabled, the Bot mirrors the Minecraft server console into a restricted staff channel and can run permitted console commands sent from that channel.
Because the bridge runs in both directions, anything you say in the linked Minecraft chat may appear in Discord, and anything you say in the linked Discord channel may appear in Minecraft. Treat both as public to the community.
Information we process
Information stored by the Bot
The Bot keeps very little on disk. What it does save is the link between your Minecraft and Discord accounts, so that features like role syncing and personalized display names work.
| Data | Why we process it | Where it is stored |
|---|---|---|
| Account link (your Minecraft UUID paired with your Discord user ID) | Recognize that a Minecraft player and a Discord member are the same person, so chat display, role/group sync, and rewards work correctly | A linkedaccounts.json file in the plugin’s /plugins/DiscordSRV/ folder, or a private MySQL database, on our own server host |
| Link verification codes | Confirm that a Minecraft account and a Discord account belong to the same person before the link is saved | Held in memory only until the link is completed or the code expires |
| Configuration (channel IDs, role/group mappings, banned words, message formats) | Tell the Bot which channels to bridge and how to display messages | config.yml and related plugin files on our server |
Information processed but not permanently stored
Most of what the Bot handles passes through it in the moment and is never written to its own storage.
| Data | Why we process it | Retention |
|---|---|---|
| Minecraft chat messages | Relayed to the linked Discord channel so Discord members can read them | Processed in memory at send time. The resulting Discord message lives in the Discord channel under Discord’s retention, not in the Bot’s own storage |
| Discord messages in the linked channel | Relayed into Minecraft chat so players in-game can read them | Processed in memory at receive time, shown in game, then discarded by the Bot. The original stays in Discord under Discord’s retention |
| Your Discord username, nickname, and avatar | Displayed alongside relayed messages and (optionally) synced as your in-game display name | Read from Discord at message time, or taken from a short-lived cache. Not stored long term by the Bot |
| Your Minecraft username and UUID | Shown as the author of bridged messages and used to fetch your player-head avatar | Read from the game server at message time |
| Server console output, where the console channel is enabled | Mirrored to a restricted staff channel for administration | Streamed to the staff channel. Retention there is governed by Discord and our channel settings |
| Role and group membership | Keep Discord roles and Minecraft permission groups in sync (“group sync”) | Read from Discord and the game server when a change happens. Only the resulting role or group state is applied; the Bot keeps no history of changes |
What we do not collect
- We do not keep a long-term database of your chat messages. The Bot relays them; it does not archive them.
- We do not record voice or video. DiscordSRV bridges text chat only.
- We do not read your private direct messages, except the single link-confirmation DM you choose to send the Bot when connecting your account.
- We do not track your Discord online/offline status or activity — the Bot does not request the Presence intent.
- We do not sell your data or use it for advertising or profiling.
Discord privileged intents
Discord requires bots to declare “privileged intents” before they can access certain sensitive data. The Bot requests only the two that the bridge needs:
Message Content Intent
Required so the Bot can read the text of messages in the linked Discord channels and relay them into Minecraft. Without it, the bridge could not carry Discord messages into the game. Message content is used at the moment of relaying and is not stored by the Bot.
Server Members Intent
Used to:
- Keep Discord roles and Minecraft groups in sync (group sync) when a member’s roles change.
- Read nicknames and display names so bridged messages and synced names appear correctly.
- Detect when a linked member joins or leaves the Discord server, so the correct roles and groups are applied or removed.
Intents we do not request
The Bot does not request the Guild Presences intent. It does not need your online status, current game, or activity.
Third-party services
Discord
The Bot runs on Discord’s platform. Discord processes data according to Discord’s Privacy Policy. We receive data from Discord’s APIs only as needed to operate the bridge.
Avatar (player-head) service
To show your Minecraft player head next to bridged messages, the Bot asks a public avatar service — Crafatar — to render the head for your UUID. Only your Minecraft UUID, a public identifier, is sent to that service. Your Discord data and message content are never sent.
Anonymous statistics (bStats)
DiscordSRV reports anonymous, aggregate usage statistics to bStats — for example, the plugin version and the server software in use. This contains no personal information about you.
How we protect data
- The Discord bot token and any database credentials are kept in server-side configuration that only administrators can read. They are never shared publicly.
- Account links and configuration files live on the server host that runs Minecraft and the Bot, not in any third-party analytics system.
- The console channel and staff commands are restricted to authorized staff roles.
No system is perfectly secure. If you believe there has been unauthorized access, contact the administration team promptly.
Data retention
| Data type | Retention period |
|---|---|
| Account link (Minecraft UUID ↔ Discord ID) | Kept until you unlink it or an administrator removes it |
| Link verification codes | Expire shortly after they are generated |
| Relayed chat messages | Not retained by the Bot. Copies posted in Discord or shown in Minecraft follow Discord’s retention and our server settings |
| Console channel output | Governed by Discord’s message retention and our channel settings |
| Configuration files | Kept for as long as the Bot is in use |
We keep identifiable data only for as long as the purpose it was collected for still applies.
Your choices and data deletion
The main piece of personal data the Bot stores is your account link. You are in control of it.
Unlink yourself at any time: run /discord unlink in game. This removes the pairing between your Minecraft and Discord accounts.
To request access or deletion:
- Contact the server administration team through the community’s support or moderation channel.
- Provide your Discord user ID and/or Minecraft username so we can identify your link.
- Tell us what you are requesting (access, correction, or deletion).
What we can delete: your account link — the record tying your Minecraft and Discord accounts together. This is the only personal record the Bot holds about you.
What may remain outside our control:
- Messages already relayed into Discord channels or shown in Minecraft chat are governed by Discord and by our server logging settings, not by the Bot’s storage.
- Aggregate bStats statistics contain no personal data and cannot be traced back to you.
We will respond to reasonable requests within 30 days.
Children’s privacy
The Bot is intended for use within a Discord community subject to Discord’s Terms of Service and minimum age requirements. We do not knowingly collect information from children under the minimum age required by Discord or applicable law.
International users
The community may include members in different countries. Data is processed on the server where the Bot and Minecraft server are hosted. By using the community, you understand that data may be processed in that location.
Changes to this policy
We may update this policy when the Bot’s features or data practices change. The “Last updated” date at the top will be revised. Significant changes may be announced in the community.
Continued use of the bridge after an update constitutes acceptance of the revised policy.
Contact
For privacy questions, data access requests, or deletion requests:
Contact the server administration team through the community’s designated support or moderation channel.