MCGateway stores service information so the gateway can work and improve.
MCGateway operates access bots, an in-game Hub, Discord services, a public website, and the MCGateway Warehouse backend. Some player and service history is retained so features can work across visits, reliability can be measured, problems can be diagnosed, and historical statistics can remain accurate.
MCGateway does not sell player information.
MCGateway does not need your Microsoft or Discord password.
- MCGateway does not ask you to submit your Microsoft password.
- MCGateway does not ask you to submit your Discord password.
- Minecraft-to-Discord linking uses a temporary code shown between the game and Discord instead of asking you to sign in through MCGateway.
- You should never send account passwords or authentication credentials to MCGateway staff or support channels.
MCGateway may retain information tied to normal service activity.
This can include Minecraft player identity information needed to recognize returning players, Hub sessions and activity, transfer events, saved MCGateway settings, server history needed for player features, bot-friend relationships, service reliability records, and Discord-link information when a player chooses to link accounts.
MCGateway may also retain aggregate and historical analytics derived from this activity, such as total transfers, unique-player counts, session activity, server usage, and reliability statistics.
Private server destinations are not automatically made public.
MCGateway may retain destination information needed to perform transfers, provide player history, maintain service records, or diagnose problems. A destination existing in MCGateway history does not automatically make its address public on the website.
Public server information, Featured Servers, Server Codes, or destinations otherwise confirmed for public use may be displayed as part of public MCGateway features.
The public site is built around aggregate and intentionally public information.
The website can show information such as total transfers, unique players, tracked server counts, recent aggregate transfer activity, current Hub population, gateway status, access-bot availability, and other public service statistics. Private account identifiers, credentials, and private destination details are not intended to be exposed through the public website.
Inactive access-bot friendships may be cleaned up to preserve capacity.
MCGateway access bots have finite friend capacity. Players who have been inactive for about one month may be removed from access-bot friend lists so active players can continue to use the service. If that happens, the player can add an available bot again when they return.
Service history supports features, reliability, safety, and accurate statistics.
MCGateway uses retained service information to operate persistent player features, measure growth and uptime, detect failures, troubleshoot transfers, prevent data loss, improve the system, support moderation where necessary, and preserve accurate historical totals.
Retention periods can vary depending on the type of record and the feature it supports. MCGateway may keep historical and aggregate records for long periods when they are needed to preserve accurate service history.
Information may be reviewed when needed to protect MCGateway or its users.
MCGateway is generally permissive about ordinary player behavior. Records may be used to investigate severe abuse such as attacks on the service, attempts to exploit systems, hacking, data theft, or repeated harmful behavior.
Questions about privacy or your MCGateway account can be directed to MCGateway support.
Use the official Discord for the fastest support, or email mcgatewaycontact@gmail.com. If you have a question about information associated with your MCGateway use, contact support so the request can be reviewed against the records and features involved.
Last updated: August 31, 2026.