Enderbeam for Discord — privacy

1. It cannot read your messages

Not “we choose not to”. There are two separate locks in Discord and this bot is on the wrong side of both. It was never granted Read Message History, which is the permission Discord checks before it will hand any application the messages in a channel. And it does not hold the Message Content intent, the second gate, which it has never asked for.

There is also no code in Enderbeam that would do anything with a message if one somehow arrived. But that is the weakest of the three reasons, because it is a promise about our software rather than a limit Discord enforces, and you have no way to check it. The other two you can check.

The same goes for the other two gated permissions. It cannot see your presence — whether you are online, what you are playing — and it cannot download the member list of a server it is in.

So check rather than believe. Server Settings, Integrations, Enderbeam lists every permission the bot holds in your server. Read Message History is not among them, and Discord decides that, not us.

2. What it does read

Four things, all of them about the server rather than about the people in it.

• The server's name, icon, and id — so your website can show which Discord it belongs to.
• The list of channels, so whoever set this up could pick one from a menu instead of pasting an id.
• The list of roles, for the same reason: so an Enderbeam rank can be pointed at a Discord role by name.
• The member count and how many are online. These are two numbers Discord gives out with the server itself. They are not a list, and they never become one.

When somebody runs the leaderboard command, it also receives what they typed — which leaderboard and how many places. That is not stored.

It also holds permission to send messages and embed links, granted when it was added. Nothing uses them yet; they are for a future feature that forwards a site’s news posts into a channel. Discord does not let a bot gain a permission after it joins, which is why it was asked for early rather than when the feature lands.

3. What is kept, and for how long

One row, written when an owner connects a Discord server to their Enderbeam site: the Discord server's id, name and icon, which Enderbeam account connected it, the date, and the channel chosen in settings.

The member and online counts are held in memory for a few minutes at a time so that a busy page does not ask Discord the same question repeatedly. They are not written down and they do not accumulate into a history.

Nothing else persists. No messages, no member lists, no record of who ran a command.

Removing the bot from your Discord server stops all of it immediately. Deleting the connection in the site's settings, or deleting the project, removes that row.

4. Roles, and the Discord account behind them

If a site owner has pointed an Enderbeam rank at a Discord role, the bot adds and removes that role as the rank changes. To do that it needs to know which Discord account a member is.

It does not find that out. It is told. A member who signs in to a community's website using Discord links the two accounts themselves, and that sign-in is a different Discord application from this bot — the one the website's login runs on. The bot receives an account id from that link and nothing else. It does not see your email, your profile, your other servers or your friends.

A member who has never signed in with Discord simply gets no Discord roles, which is the case for most members of most sites. Nothing is looked up to try to match them.

The role it grants is the one the owner chose. A Discord role is a real permission in a real server, and the person who mapped it decided what it carries.

5. Leaderboards, and the players on them

The leaderboard command shows the same board the community's website shows, read through the same code, with the same consent rules applied.

A player who has opted out of leaderboards on the website is not on the Discord one either. That is not a second setting we remembered to honour — it is the same filter, running in the same place, which is the only arrangement that cannot drift apart.

Boards carry a Minecraft username and one number. They do not carry Discord accounts, and there is nothing in the embed that connects a player to a person in your server.

If you want your own name off, there is a page about how at enderbeam.com/privacy-request, and it applies everywhere at once.

6. Where the rest of it is written down

This page is about the bot. Enderbeam's full privacy notice — what a community website stores, the lawful bases, how long things are kept, who it is shared with, and your rights under UK and EU data protection law — is at enderbeam.com/privacy.

Discord is its own company with its own privacy policy, and what Discord does with your account is between you and them. We are a bot in a server you chose to add us to.

Questions, or a request about your own data: support@enderbeam.com. A person reads it.