Legal
Privacy Policy
BimmerLink is a Discord bot that connects a Minecraft server to a Discord server. This policy explains what information passes through it, what is kept, what is not, and what you can ask for.
Last updated 7 August 2026 · Applies to the BimmerLink Discord application
The short version
- BimmerLink does not keep a copy of the chat it relays.
- It stores no user profiles, and it builds none.
- Nothing about your account is touched until you start the linking process.
- No advertising, no analytics, no tracking, no selling or sharing of data.
- The only things written down are the settings administrators configure and short-lived error logs.
Who is responsible
BimmerLink is built and operated by Plebbian for use in Minecraft communities. It is a small, non-commercial project, not a company product, and it runs on infrastructure belonging to the operator of the Minecraft server it is installed on.
The administrators of the Discord and Minecraft servers you join decide whether BimmerLink is installed, which channels it relays, and which roles it manages. They are responsible for those choices and for how their own community is run.
What BimmerLink does
- Relays Minecraft game chat into an administrator-configured Discord channel.
- Relays messages posted in those configured Discord channels into Minecraft.
- Relays Minecraft server console output into a channel administrators set aside for it.
- Optionally links a Discord account to a Minecraft account, only when a user starts that process themselves, so that Minecraft permissions and Discord roles can be kept in step.
It works alongside the EssentialsX Discord and EssentialsX DiscordLink plugins installed on the Minecraft server; those plugins are not ours, and the Minecraft server operator is responsible for running them.
Information BimmerLink handles
"Handled" and "stored" are different things, and the difference matters here. Most of what BimmerLink touches passes through it and is gone — it is read from one side, delivered to the other, and not written down anywhere by the bot.
| Information | When | Why | Stored by BimmerLink? |
|---|---|---|---|
| Discord user ID and display name | When you post in a relayed channel, or start linking | To attribute a relayed message, and to know which account is linking | No |
| Message content in relayed channels | When you post in a channel configured for relaying | To deliver the message to the other side | No |
| Discord roles and server membership | During linking and role synchronisation | To grant or remove the roles that match your Minecraft permissions | No |
| Minecraft username and account identifier (UUID) | During linking and role synchronisation | To apply permissions to the correct Minecraft account | No — see the link record |
| Minecraft chat and server console output | While the server is running | To relay it to the configured Discord channels | No |
| Channel, role and server IDs; role mappings | When an administrator configures the bot | To know where to relay and which roles correspond to which ranks | Yes — configuration |
| Error and diagnostic log entries | When something goes wrong | To find and fix faults | Yes — briefly |
Configuration
The configuration BimmerLink stores is about the server, not about people: which channels to relay, and which Minecraft ranks correspond to which Discord roles. It is written by administrators and contains no personal profiles.
The link record
When you link your accounts, the association between your Discord account and your Minecraft account is created and held by the EssentialsX DiscordLink plugin on the Minecraft server itself, under the control of that server's operator. BimmerLink uses that association to apply roles and permissions; it does not keep a separate copy of its own.
Logs
Operational logs are kept so that faults can be diagnosed. A log line may incidentally include a Discord ID or a Minecraft username — for example when a role change fails. Logs are kept only while they are useful for diagnosing a problem and are then discarded. They are not analysed, aggregated, or used for any purpose other than keeping the bot working.
What BimmerLink never does
- It does not read direct messages.
- It does not read channels it has not been configured to relay.
- It does not store a copy of relayed chat, on either side.
- It does not build profiles, score behaviour, or track anyone across servers or services.
- It runs no advertising and no analytics, and contains no third-party trackers.
- It does not sell, rent or trade information about you. There is nobody to sell it to and nothing to sell.
- It does not use your messages to train machine-learning models.
- It collects nothing at all from people who never interact with it.
Where information goes
Only two places, both of them obvious from what the bot is for:
- Discord. Everything BimmerLink sends to Discord is stored by Discord as ordinary message history, under Discord's Privacy Policy. Deleting messages there is done through Discord, not through us.
- The Minecraft server. Relayed messages appear in the game and in that server's own logs, which the server operator controls and retains under their own practices.
Nothing is sent anywhere else. There are no third-party processors, no external analytics services, and no data exports.
Linking is voluntary
Role synchronisation happens only for accounts that have been linked, and linking only ever begins with a deliberate action by the person whose accounts they are. If you never link, BimmerLink never changes your roles or your permissions, and you can still use the Discord server normally.
You can unlink at any time — the Minecraft server's EssentialsX DiscordLink command does this, and an administrator can do it for you. After unlinking, role synchronisation stops for your account.
How long things are kept
- Relayed messages: not retained by BimmerLink at all. Copies live in Discord and in the Minecraft server's logs, as described above.
- Configuration: for as long as the bot is installed, or until an administrator changes it.
- Link records: until you or an administrator unlinks the accounts, held by the Minecraft server's plugin.
- Operational logs: only while useful for diagnosing a problem.
Why this is lawful
Where data-protection law such as the GDPR or South Africa's POPIA applies, the processing described here rests on the legitimate interest of running a functioning community server — relaying the chat a channel was created to relay — and, for account linking and role synchronisation, on your consent, which is the act of starting the linking process. Consent can be withdrawn by unlinking.
Your choices and your rights
Depending on where you live, you may have the right to:
- ask what information about you the bot holds;
- ask for it to be corrected or deleted;
- withdraw consent for account linking, by unlinking;
- object to processing, or ask that it be restricted;
- complain to your local data-protection authority.
In practice the requests people make are small, because so little is kept: unlink my accounts, remove my link record, delete a message. Ask an administrator in the Discord server where BimmerLink is installed — see Contact.
One limit worth stating plainly: messages already delivered cannot be recalled from the other side. A message relayed into Minecraft has been seen by the players who were online and may sit in the server's logs; a message relayed into Discord is Discord's to delete. Removing a message is a request to the platform that holds it, not to the bot that carried it.
Children
BimmerLink is used through Discord, which requires its users to be at least 13 years old, or older where local law sets a higher minimum. It is not directed at children under that age, and it does not knowingly process their information. If you believe a child too young to use Discord has interacted with the bot, tell an administrator so the account can be removed.
Security
The bot's credentials are kept secret and are never published in code or configuration that others can read. BimmerLink asks Discord for the permissions it needs and no more. That said, no internet service is perfectly secure, and this is a community project rather than a hardened commercial platform — please do not treat a relayed channel as a private or confidential place.
Changes to this policy
If what the bot does changes, this page changes with it, and the date at the top is updated. Material changes will be announced in the Discord server where the bot is installed. Continuing to use BimmerLink after a change means the updated policy applies to you.
Contact
Privacy questions and requests go through the Discord server where BimmerLink is installed: message an administrator or the server owner there, and it will reach the operator of the bot. That is deliberate — it keeps requests with the people who can actually act on them for your community.
See also the Terms of Service, which cover what the bot is and the rules that come with using it.