Who operates BedrockRelay

BedrockRelay is operated by BedrockRelay, part of the myGen network. For privacy questions or requests, contact privacy@bedrockrelay.com.

Information we handle

Dashboard sign-in

When you sign in with Discord, we ask only for the identify and guilds permissions. We receive your Discord user ID, display name, avatar and the Discord servers you belong to, including the permissions needed to identify servers you can manage. We do not receive your email address. We store an encrypted Discord access token and refresh token in a server-side session so the dashboard can recheck your permissions. We also keep a list of everyone who has signed in, with their Discord user ID, display name, avatar and when they first and last signed in, so that we can show a message to a particular member on their dashboard.

Relayed messages and events

To deliver the features an administrator enables, we process Minecraft player names, chat, join, leave, death and other addon event content; Discord message text, display names, channel and server identifiers, avatar URLs and attachment links; and command requests. The bot reads messages only in channels an administrator has connected, and sends them only to that Minecraft world. Optional shared chat can also copy human Discord messages to other connected channels when it is switched on at both ends.

Commands and plugins

When someone uses /relay run or a plugin command in Discord, we pass the command, the options they gave and their Discord display name to the Minecraft world, and return its answer. Plugin answers are shown only to the person who asked, except for commands made to be shared, such as leaderboards, which are shown in the channel. If the person has linked their account, we also pass their linked Minecraft name. Plugins run on the Minecraft server, not on our systems. Some plugins post to Discord by themselves, such as a playtime milestone, but only in channels the owner chooses. Some reveal information about players, such as their location or inventory. The dashboard shows what each plugin reveals beside its switch, and the owner chooses which Discord roles may use it.

An owner can also upload a plugin of their own. We store its code against their Discord account so it can be installed on their servers. These private plugins are not reviewed before use, so the service operator can read their code to keep the service safe. A private plugin is never shown to anyone else unless its owner submits it to the public catalog: we then keep the code they submitted, the credit, category and links they gave, and when they agreed to its licence, and if it's published, it appears in the public plugins repository under the name they gave.

Player details and moderation

A Minecraft world's owner can look up a player from the dashboard: their position, health, experience, effects, equipment, inventory and ender chest. While the player is online, this is read from the game when the owner asks. As each player leaves, the pack sends the same details, and we keep only that latest copy for each player so the owner can see what they had when they were last online. An owner can also warn, kick, mute or ban a player, or take them off the world's allowlist or Realm members, from the dashboard; members with a Discord role the owner chooses can do the same with /relay mod. We log each action: the player, the reason, for how long, the result, and who did it (their Discord user ID, and their display name when it wasn't the owner). For each ban or mute in force we keep the player's name and the account ID their world reports, so that it follows them if they change their gamertag: on a dedicated server, the ID of their Minecraft account that the server gives the pack; on a Realm, their Xbox user ID. To ban someone from a Realm who hasn't played there, we look up their gamertag's Xbox user ID with one of our relay bots. A ban or mute is deleted when it's lifted or runs out; the log keeps the line about it. We also keep the Discord role IDs the owner chose for moderating.

Linked accounts

A Discord member can use /relay link to link their Discord account to their Minecraft name on one Minecraft world. To prove it's them, they sign in with Microsoft on a one-time page, as for verification (below): we read their gamertag and Xbox user ID and discard the sign-in. Once linked, we store their Discord user ID, their display name at the time, their Minecraft name and Xbox user ID for that world. Links made before 1 October 2026 were proved with a one-time code sent to the player in the game, and have no Xbox user ID. The owner can see and remove links in the dashboard, and the member can undo theirs at any time with /relay link.

Proximity voice

If an owner enables proximity voice, the pack sends the names, dimensions and current coordinates of online players to the gateway, about once a second on a dedicated server and every few seconds on a Realm. We compare those positions with verified account links and Discord voice-channel membership to decide which opted-in members should share a voice room. We use these live coordinates only for that grouping, do not write them to the database, and discard them when updates stop. They are not sent to Discord. Discord receives the voice-room and permission changes needed to move opted-in members.

Minecraft Realms

A Realm can't run BedrockRelay's pack the way a dedicated server does, so one of our own Microsoft accounts joins it as a player (a relay bot) and relays it. Connecting one works like this.

The owner's Microsoft sign-in. The Realm's owner signs in with Microsoft. We ask for Xbox Live sign-in and offline access, and Microsoft's sign-in also asks to see their basic profile, which we don't keep. We receive their gamertag and Xbox user ID; we do not keep their email address. To show their Xbox profile picture on their dashboard, we look it up with one of our relay bots, not with their sign-in, and keep its address; their browser loads the picture from Microsoft. We keep the sign-in, encrypted with a key held only on our server, so that the pack can be installed and updated later without asking again. We use it only with the Realms service and only on that owner's own Realms: to list them, to invite our relay bot and make it an operator, to close the Realm, copy its world, add the pack and open it again (by itself too, if the owner turns on keeping the pack up to date: then only when the pack is missing or out of date and nobody is on the Realm), to invite players who ask to join through the Realm's invite link, to ban, unban or remove players when the owner or their moderators ask, and to find the Realm's latest backup for BedrockMap when the owner keeps a map up to date. If the owner chooses to have their own account relay a Realm instead of our relay bot, we also use it to join that Realm as the relay bot does: hidden, and never to play. Otherwise we never use it to join a Realm, and we never use it to sign in anywhere else as the owner. Each time we use it, we note when.

The relay bot in the Realm. Our relay bot sees what any player in the Realm sees: players' names, gamertags, Xbox user IDs, skins, chat, joins and deaths. It relays these as the owner's routes say. If one of the owner's channels takes the Realm's Stories, the relay bot also reads the Realm's story feed, as any member can, every few minutes: the game's own events, such as a player first reaching the End, with the gamertags of the players involved, and what members post there, text and screenshots, with their gamertag. Each new story is posted to those channels, screenshots included; we keep only which stories we've posted, for two weeks, so none posts twice. We never pass on the coordinates the feed can carry. From a player's skin we cut the face to show as their picture in Discord, kept in memory for up to a day. We also read which Character Creator items a skin uses, for mcBedrock (below). The bot takes one of the Realm's player slots.

The Realm pack. The pack we add to the Realm's world hides our relay bot, runs commands sent from Discord, and every few seconds tells the relay bot which players are online and where, for proximity voice and player details. It speaks only to our relay bot, using a secret unique to that Realm.

Adding the pack. To add or update the pack, we close the Realm, download a copy of its world to our server, add the pack's files, upload it and open the Realm again. We do not look at or keep anything else from the world, and our copy is deleted as soon as the install finishes, whether or not it succeeds. An owner can instead download the pack and add it to the Realm themselves in Minecraft.

Invite links

A world's owner can make an invite link on bedrockrelay.link. The page is public and shows what the owner chooses: the world's name and the owner's own heading and description, whether it's online and how many are playing, a dedicated server's address, and a Discord server's name, icon and member counts from Discord. It never lists who is playing.

Joining a Realm through an invite link. The person joining signs in with Microsoft. We ask for the same as for a Realm owner, because that's what the Realms service needs. We receive their gamertag and Xbox user ID, use the sign-in once to accept the Realm's invite, and then discard it: it is held in memory only while they join and is never written to disk. The owner's sign-in sends the invite. We record the gamertag and the outcome in the world's audit log and count the join.

Adding a server to a BedrockGo list. On a dedicated server's invite page, a player can add the server to their list on BedrockGo (bedrockgo.com, another myGen service), which lets console and mobile players join servers from Minecraft's Friends tab. They sign in with Microsoft, asking for the same as for joining a Realm. We read their gamertag and Xbox user ID, then discard the sign-in. We send BedrockGo their Xbox user ID with the server's name, address and port, so that it appears in their BedrockGo list. We don't keep their Xbox user ID; we record their gamertag in the world's audit log. If the owner later changes the server's address or the invite page's heading, we send BedrockGo the new details, without any player's details. BedrockGo's own privacy policy governs what it keeps.

Joining a Discord server through an invite link. The person joining signs in with Discord. We ask only to know who they are and to add them to a Discord server. We use that sign-in once, for our bot to add them to the Discord server the owner chose, and then revoke it. We record their Discord username and user ID in the world's audit log and count the join. Discord's own rules still apply: someone banned there is not added.

Our Discord server

Joining it. A member can join our own Discord server from their Account page. Only then do we ask Discord to let us add them to a server; we use that once, for our bot to add them, and then revoke it. Signing in to the dashboard never adds anyone.

The World Owner role. A member who owns a connected world gets the World Owner role in our server, and loses it when they no longer own one. To keep it right, our bot looks up whether each world owner is a member of our server, using their Discord user ID, and remembers the answer.

Asking for help there. When someone starts a post in our help or bug-report forums, our bot posts a note for our staff in a channel only they can see: who posted, when they first and last signed in to the dashboard, and their worlds' names, kind, whether they're online, pack and Minecraft versions, number of channels and whether relaying is switched off. It never includes chat, players or SFTP details.

Verification

A world's owner can turn on verification: a Verify button in their Discord server. Someone who presses it signs in with Microsoft, asking for the same as an invite link. We read their gamertag, Xbox user ID, Gamerscore and the address of their gamer picture from their own Xbox profile, then discard the sign-in: it is held in memory only and never written to disk. There is one exception: for a Realm whose owner reviews each request, we keep the sign-in in memory until an admin decides, for seven days at most, so that approving can accept the Realm's invite for them and add them straight away. It is discarded when the request is decided, after seven days, or if our service restarts, and it is used only to accept that one Realm's invite. An approved player whose invite is still waiting can sign in once more to be added; that sign-in is used once, only if it's the approved Xbox account, and then discarded. We keep those details with their Discord user ID and name, as a request for that world. The owner chooses a Discord channel where the request is shown; anyone who can see that channel can approve or deny it, and we record who did and when. On approval we add them to the world's allowlist or invite them to the Realm (with the owner's sign-in), link their Discord account to that player, and give them the role the owner chose. The request also lists other Discord members who asked for that world with the same Xbox account, and other Xbox accounts the same member asked with, so admins can spot alternative accounts; this never looks across other owners' worlds. The owner can revoke an approval, which undoes only what we did.

Linked services and map sync

A world's owner can link it to a map on BedrockMap (bedrockmap.net, another myGen service) by choosing Connect your world in BedrockMap, which hands us a key for that map. We keep the key, encrypted, until they unlink the map or remove the world. While live players are switched on for the map in BedrockMap, every few seconds we send BedrockMap the names, positions and dimension of the players online, which way they face on a Realm, and the account ID we know for each (their Xbox user ID on a Realm, the ID of their Minecraft account on a dedicated server). BedrockMap shows them on that world's map, which can be public. The owner switches this on and off in BedrockMap; while it's off, nothing is sent.

An owner can also start from BedrockMap, without Discord. BedrockMap then sends us their BedrockMap user ID, the name they use there, the world's name and its key, and signs them in to our dashboard. We keep the user ID and name as their account here, and which BedrockMap world each of their worlds was connected for, so BedrockMap can bring them back to it; nothing else about them comes from BedrockMap. If someone signed in with Discord connects a world this way, we also keep which BedrockMap user their account is, so the next time BedrockMap sends them here, they sign in to that same account.

If the owner turns on keeping the map up to date in BedrockMap, a copy of the world goes to BedrockMap each time it asks, on the schedule the owner sets in BedrockMap. For a dedicated server, the pack briefly pauses saving while we copy the world's files over SFTP, so we keep that server's SFTP password or private key for this, encrypted with a key held only on our server, used only to copy that world for its map. The copy is deleted from our server once it's sent. For a Realm, we use the owner's Microsoft sign-in to get the address of the Realm's latest backup, and give it to BedrockMap, which downloads it. BedrockMap's own privacy policy governs what it keeps.

mcBedrock

mcBedrock (mcbedrock.net, another myGen service) shows Minecraft Bedrock players' profiles and statistics, and lists worlds. Most of what we send it depends on the world's owner listing their world there; two small feeds, described last, come from every world.

Listing a world. A world's owner can list it on mcBedrock from its Integrations tab. While it's listed, every few minutes, and straight away when someone joins or leaves, we send mcBedrock whether the world is online, how many are playing, its peak and its Minecraft version, and for each player who has played there: their gamertag, whether they're online, and the account IDs we know (their Xbox user ID, and on a dedicated server the ID of their Minecraft account). If the owner also installs our Statistics plugin, we send each player's statistics from it, such as blocks mined, distance travelled and time played. The plugin keeps those statistics in the world itself; we hold changes only until mcBedrock confirms it has them. We also send what the owner has set or shared on BedrockRelay for the listing: the world's name, Minecraft version and player limit, the join address they entered, their invite link's heading and their Discord server's name and member count, and the map's link if they show it. For a listed Realm, we also send which Character Creator items each player's skin uses and their colours, when our relay bot first sees them and when they change. We never send the skin's image. We never send chat, positions, IP addresses or anything from Discord about players. When the owner lists a world that was on mcBedrock before, mcBedrock may send back the statistics it already holds for that world, so the plugin can carry on from them.

Unlisting. The owner can unlist the world at any time from its Integrations tab, or on mcBedrock. We stop sending at once, and mcBedrock hides the listing but keeps what it has already received. Removing the world on BedrockRelay stops sending at once, and unlists it once the removal can no longer be undone.

Names from every world. Once a day, we send mcBedrock the gamertags of players seen on any world connected to BedrockRelay, with their Xbox user IDs where we know them, so that mcBedrock can look up their public Xbox profiles, as it would if someone searched for them. We send each name once, mixed with names from other worlds, without the world it came from or when, so mcBedrock can't tell where or when anyone played. Our relay bots and FarmBots are never sent.

Character Creator items from every Realm. Once a day, we send mcBedrock a list of the Marketplace Character Creator items our relay bots have seen in any Realm, to build its catalogue of items. This is the items alone: never who wore them, which Realm, when, or their colours.

Opting out. Any player can opt out on their mcBedrock profile page. mcBedrock then drops their data, and tells us, so we stop sending anything about them, including their name.

Claiming a profile on mcBedrock. Players claim their mcBedrock profile, and sign in to mcBedrock, by signing in with Microsoft on our site, asking for the same as for joining a Realm through an invite link. We read their gamertag and Xbox user ID, give them to mcBedrock, and discard the sign-in. This doesn't create a BedrockRelay account; we keep only a line in our audit log.

Signing in to mcBedrock with BedrockRelay. A world's owner can sign in to mcBedrock with their BedrockRelay account, to manage their listings there. The first time, we ask whether they agree, and remember that they did. We then tell mcBedrock their BedrockRelay account ID, display name and avatar, and which of their worlds are listed there. mcBedrock's own privacy policy governs what it keeps.

Server status and statistics

We keep the list of player names currently online in each Minecraft world so /relay online and the dashboard can show it. We also remember the names of players who have played there, and when they were last seen, to suggest names when someone types a plugin command. For each world we also count, per day, messages in each direction, joins, deaths and the peak number of players. These are counts, not the messages themselves. When a world stops checking in for a minute, and again when it returns, we post a notice in channels that have the Status event switched on.

Reachability checks

For a dedicated server, to show whether players can join, we record the IP address the pack connects from, the game ports in server.properties when an SFTP visit reads them, and any join address the owner enters. About once a minute we send Minecraft's standard status check to that address and store the result. We never check addresses on private networks.

Messages from us

We post messages on dashboards, such as planned maintenance, a problem with a member's server, or news. A message goes to everyone who signs in, or only to chosen members. For a message sent to chosen members, we record when each of them first saw it and whether they hid it, so we know it reached them. We do not have members' email addresses and our bot never sends direct messages on Discord, so this is how we contact members.

What the gateway stores

Minecraft world registrations (name, whether it's a dedicated server or a Realm, Minecraft and pack versions, last check-in); channel routes, their names, event filters and Discord webhook credentials; command and plugin rules, including Discord role IDs; installed plugins and the commands the pack reports; owners' private plugins; hashed installation tokens; the status, statistics and reachability data above; players' latest details, the moderation log, bans and mutes in force and the roles chosen for moderating; for Realms, the Realm's ID and name, which relay bot serves it, the owner's encrypted Microsoft sign-in with their gamertag, Xbox user ID and the address of their Xbox profile picture, and the pack's install history; invite links, with their address, what they show, the owner's heading and description, and how many have joined through them; verification settings and requests, as described above; the list of dashboard members and messages to them; and audit records. Audit records note which Discord user made a dashboard change, ran a command (with the command text) or used a plugin (with the options given), and when.

Installation and technical data

If you install, update or uninstall the pack or a plugin over SFTP, the host, port, username, password or private key and server path are used for that one connection, and the password or key isn't saved or logged. The only exception is keeping a BedrockMap map up to date, which the owner turns on, as described above: then that world's password or key is kept, encrypted, until the owner forgets it, unlinks the map or removes the world. After a connection works, we keep its host, port, username and server path with that Minecraft world, so next time only the password needs typing; the owner can forget them at any time, and they go when the world is removed. An audit entry records the host, username and selected world for troubleshooting. Gateway and web-server logs may contain IP addresses, request paths, timestamps and errors.

We use essential cookies only: for your dashboard session, for the security of the Discord and Microsoft sign-ins, the bot invitation and joining through an invite link, and to remember your chosen language. Your browser's local storage keeps a few preferences on your device, such as updates you've hidden. SFTP details a browser kept before 1 October 2026 are read until we hold them for that world, then removed from the browser. We do not run advertising or analytics cookies on this site. We count visits to these pages with Cloudflare Web Analytics, which sets no cookies, keeps nothing on your device and does not follow you across sites: it tells us how many people visit which pages and where they came from.

Why we use it

For dashboard users, we process identity, permissions and configuration to provide the service they ask for and to manage their installations, including status, statistics, reachability checks and, for a Realm, the owner's Microsoft sign-in. For players and Discord members whose messages are relayed, whose details an owner looks up, or who are removed from a world, we rely on our legitimate interest in providing the tools the world's owner has chosen, with controls on what is relayed and short-lived delivery queues. We also use limited technical and audit data, and messages to members, for our legitimate interests in running the service well, keeping it secure, diagnosing faults and preventing abuse. Owners should tell their community which channels are linked, which plugins are switched on, and that owners can look up player details, before enabling the relay.

Where information goes

Some of these providers may process data outside the UK. Their privacy notices describe their own processing. Contact us if you need details of safeguards for a transfer we control. We do not share data with data brokers or advertising networks.

How long we keep it

Security

Discord sign-in tokens are stored encrypted. Realm owners' Microsoft sign-ins are stored encrypted with a key kept only on our server, and only the part of the service that talks to Minecraft uses them. Installation tokens are stored only as hashes, so they cannot be read back, even by us. SFTP passwords and keys are stored only for a BedrockMap map an owner keeps up to date, encrypted with a key kept only on our server; otherwise they're used for one connection and never stored. BedrockMap keys are stored encrypted the same way. Each Realm's pack answers only our relay bot, using a secret unique to that Realm. Traffic to the site and the gateway is encrypted in transit. Every dashboard change rechecks that you still manage the Discord server concerned. If personal data is accessed without authorisation, we will tell the people affected and Discord, as the law and Discord's developer terms require.

Children

The dashboard and bot are for Discord users, who must meet Discord's minimum age. BedrockRelay is not directed at children. Minecraft players' names, chat and details are handled only as the world's owner configures, and a Realm owner signing in with Microsoft must be able to use that account online.

Your choices and rights

A Minecraft world's owner can change or switch off routes, direction, events, shared chat, proximity voice, command rules and plugins in the dashboard. They can also revoke every pack token, uninstall the pack and remove the world there. A Realm owner can sign out of Microsoft on their Account page at any time, which deletes their kept sign-in. A player opts in to proximity voice only by joining its lobby and can opt out by leaving voice. Anyone who manages a Discord server can disconnect a Minecraft world from it, using the dashboard or /relay disconnect, or remove the bot. A member can hide a message sent to them. You can sign out of the dashboard at any time, on one device or all of them, from your Account page.

You may ask us to access, correct, delete or restrict your personal data, and you may object to processing based on legitimate interests. If you are a player and want your details removed from a world, you can also ask its owner. Rights depend on the circumstances and applicable law. Contact privacy@bedrockrelay.com with your request.

If you are in the UK, you can also complain to the Information Commissioner's Office. We do not make decisions about people solely by automated processing that have legal or similarly significant effects.

Changes

We will update this page when the service or its data handling materially changes, and show the new effective date here.