Last updated 13 October 2026
MC Server Manager ("the App") is developed by Natchland Studios. This policy explains what information we collect when you use the App and our online services, why we collect it and how it is used.
The desktop App runs your servers without an account. A few requests go out on their own: it checks for updates and for our announcements, it looks up your public IP address so it can show it to you and once per install it sends one anonymous number when a friend first joins. Everything else only happens when you use an online feature: an account, a licence, a relay, Plus, the web dashboard, error reports or the AI tools. The full list is under Network Requests Made by the App below.
When you register an account on mcservermanager.com we collect:
All card payments are processed by Stripe. We never see, store, or transmit your card number, CVV, or expiry date. We store Stripe customer references and session IDs so that your payment history can be linked to your account and refunds can be processed if needed.
When you use paid features we record:
This data is needed to operate billing, resolve disputes, investigate abuse and provide support.
When you activate a licence key in the App, a hashed machine identifier is stored alongside the key so we can enforce the per-key device limit and detect duplicate activations. We do not store any personally identifiable hardware information, only a one-way hash.
The Linux edition works differently. When you pair a Linux machine it sends that machine's /etc/machine-id as it is, not hashed, along with its hostname, OS name, architecture and the edition's version, so the dashboard can tell your machines apart and a machine that's reinstalled is recognised as the same one.
When you sign in we issue a session token that is stored on your device and on our servers. A token lasts 30 days and one you keep using renews itself partway through, so a session you stop using ends somewhere between 15 and 30 days later. Signing out clears that device's token, resetting your password clears all of them and we can end them in response to a support or security issue.
Our support team may add internal notes to your account to track support interactions or known issues. These notes are not visible to you and are never shared with third parties.
If you apply to join our affiliate program at mcservermanager.com/affiliates, we collect additional information needed to legally pay you out:
This information is only visible to MC Server Manager admin staff and Stripe. It is never shared publicly or with other affiliates. You can request deletion of your affiliate record by emailing support@mcservermanager.com, although we may retain anonymised payout records as long as required by HMRC for tax compliance.
When a customer clicks an affiliate referral link on mcservermanager.com, we set a cookie named mcsm_ref that stores only the affiliate's referral code. The cookie expires after 3 days and is used solely to attribute commissions. If a user clicks more than one affiliate's link in that window, only the most recent one counts. We do not use it for advertising or cross-site tracking.
If you arrive from an ad, a link someone shared or another site, we note where you came from. Your browser keeps that in its own local storage under mcsm_attrib for 90 days. It's stored against your account only if you go on to create one. What gets kept is the marketing markers (the ad network's click id, the campaign name, which image was in the ad), the address of the page you first landed on and the address of the page that linked you here. Separately, the first page of each visit sends us one small note saying where the visit came from (the campaign markers or the name of the site that linked here, not its full address), which page it landed on and whether your browser has been here before. We add it to a daily count by country and keep nothing else, no IP address, no browser details, nothing that could identify you. No cookies are involved and no third party can read any of it. We don't use it to follow you around other sites. Clearing your site data removes what's in your browser.
We use this for one thing: working out whether an ad actually sold anything rather than guessing from the dates. If you would rather not have it kept, clearing site data for mcservermanager.com before you sign up leaves nothing to store.
If you apply to join our beta testing programme at mcservermanager.com/testers, we collect the answers you give on the form: your Discord username (if you provide one), your date of birth, which edition and server types you run, how often you can test, your experience level and anything else you choose to tell us. Your date of birth is used only to check you are old enough to agree to the tester terms.
Beta ("tester") builds of the app also report two things to us that the normal release does not, so we can protect unreleased builds from being leaked:
We use this only to detect and stop leaks of pre-release builds. If a tester build is leaked, we may permanently block the device identifiers and network addresses involved from using our products and we may end the responsible tester's access. This data is visible only to MC Server Manager admin staff and is never shared publicly or sold. Tester application data is kept while you remain in the programme and is removed on request.
If you list a server on the Server List we store what you write about it: the title, the description, the tags you pick, the address players type to join, plus a Discord invite and website if you add them. All of that is public. Anyone can read it at mcservermanager.com/nexus without an account.
Whether the server is running, what it runs and how many players are on it are not stored. They are read from your own copy of the App each time the public list is rebuilt, which is why the list can show a server as stopped or offline.
If your server has an icon (the server-icon.png file in its folder) the App sends a copy so it can be shown beside your listing. It is the same image players already see next to your server in their own Minecraft server list. Nothing else from the server folder is sent. Taking a listing off the list removes both the listing and the icon.
Account holders with a verified email can vote a listing up or down. We store one row for each account and listing: which account voted, which server, which way and when. Individual votes are never shown to anyone, only the totals. Voting again changes your vote, voting the same way twice takes it back and removes the row. You cannot vote on your own server.
This section is about the people who play on a server rather than the person who runs it, so it is worth reading either way.
It is off unless a server owner turns it on, per listed server. They can turn it off again at any time. With it on, the App sends us an identifier for each player currently on that server: a Minecraft Java UUID, or an Xbox XUID on Bedrock. We store that identifier, the player's current in-game name so the record can be read by a person, which server they were seen on, plus a first and last seen date.
We do not collect chat, commands, IP addresses, locations, session lengths, builds or anything else about what a player does on a server. The record answers one question, whether an account has been seen and on how many different servers. It is built on the account identifier rather than the name, because a name can be changed.
It exists so that we can build a shared list of accounts banned for griefing, cheating or similar, which server owners can choose to use to keep those accounts off their own servers. Our lawful basis is legitimate interests, specifically protecting server owners and their communities from repeat bad actors.
The record is not published anywhere. It is never sold or shared with advertisers or any other company. It is not used for anything except the purpose above. Only MC Server Manager admin staff can reach it. It is stored on the same infrastructure as the rest of our account data.
What's already recorded stays when a server stops sharing, because the ban list has to remember an account that was banned. If you play on a server and you would rather not be in this record, ask the owner of that server to turn sharing off, which stops anything new being added. Then contact us at the address at the bottom of this page with your account identifier and we will remove your rows.
A server owner can turn on a message that tells players they can vote for the server. The record of who has already been told is kept on the owner's own computer and is never sent to us. Turning it on does not send us anything about your players.
We do not use your data for advertising or marketing and we do not sell it.
Account data, billing history and relay subscription records are stored on Cloudflare's infrastructure (Workers, D1, KV and Durable Objects) and files like error reports, cloud backups and hosted modpacks in Cloudflare R2. Data may be processed in their global network, including EU and US regions. Cloudflare Privacy Policy.
All payments are processed by Stripe. Card data is handled solely by Stripe (PCI DSS Level 1 certified). Affiliate payouts are sent through Stripe Connect Express, which means Stripe collects identity, tax and bank information directly from affiliates during onboarding, we never see or store that data. Stripe Privacy Policy.
When we run ads on Reddit, we tell Reddit when someone creates an account and when a purchase happens, so it can work out which ads are worth running. This is sent for every new account, whether or not an ad brought you here. When you create an account we send your email address as a SHA-256 hash (never in the clear), the ad click id and landing page from your first visit if there was one, plus the IP address and browser details of that sign up, which Reddit uses to match it to an ad click. We don't keep that IP address ourselves. When you pay we send the amount, the currency, the same hashed email and the click id. We do not run Reddit's tracking pixel on this site, so nothing is sent while you browse. Reddit Privacy Policy.
A few buttons ask another service something on your behalf and only run when you click them: Check External on the web dashboard asks api.mcsrvstat.us whether your server can be reached from outside (it's sent your address and port) and the dashboard's player list shows heads from mc-heads.net (it's sent each player's name or ID). The relay map on the home and relay pages times your connection to each relay region when it scrolls into view. That only reaches our own relay servers.
Servers we host for you run on Hetzner Cloud in Falkenstein, Germany. Hetzner is only given a label for each machine, not your name or email. We aren't selling new hosted servers at the moment, this covers the ones still running. Hetzner Privacy Policy.
Transactional email (verification codes, billing notifications, support replies) is delivered through Resend. Your email address is shared with Resend each time we send you a message. Resend Privacy Policy.
The support chat on this website and inside the app is powered by DeepSeek, a third-party AI provider, which generates the replies. To protect your privacy, we automatically remove email addresses, IP addresses and the user name inside folder paths (like C:\Users\yourname) from your messages before they are sent to DeepSeek. Other names you type, like your Minecraft or Discord name, are not removed. DeepSeek may process this data on servers outside the UK, including in China, so do not share passwords, payment details, or other sensitive personal information in the chat. We store support conversations so we can review them and improve our help and the app. If you need to share account or personal details with us, the assistant will point you to open a ticket on our Discord instead. DeepSeek Privacy Policy.
When a server stops unexpectedly, the app can offer to diagnose it. This only runs when you click the button. It sends the last part of that server's log, the top of its newest crash report, the names of its mod and plugin files and its settings (server type, Minecraft and Java versions, memory, port, exit code) to DeepSeek, which works out the likely cause. Before anything leaves your computer the app removes email addresses, IP addresses, player UUIDs and your Windows user folder from the text. Your account email and the server's name are never sent to DeepSeek. We keep each diagnosis (what was sent and what came back) against your account so you can see past diagnoses in the app, so we can check the answers are good and to improve what the app knows about common crashes. Each licence includes a fixed number of diagnoses, subscriptions add a monthly number and packs can be bought on the account page. Pack payments go through Stripe like every other purchase and we record which pack or allowance each diagnosis came out of.
Our support staff can use an AI assistant in our admin panel to help answer your questions. It can only read, it never changes anything on your account and it only reads what the staff member asking is allowed to see. To answer it can look up your account (email, licences, relays, subscriptions and billing history, the audit log described above, notes, linked Discord), your error reports and app logs, crash diagnoses, bug reports and support chats. None of that is redacted before it reaches the AI provider. It currently runs on DeepSeek, which may process data outside the UK including in China and at other times on Anthropic (Claude), in the United States. The conversation is kept for 12 hours and every lookup is recorded in our staff audit log. Anthropic Privacy Policy.
Relay game traffic is routed through relay servers we operate in multiple regions. Minecraft game packets pass through these servers during relay sessions in order to reach your server. The region is chosen by you when you start the relay:
What the relay servers record about connections:
The system logs stay on each relay server, aren't sent anywhere else and are deleted after 7 days.
The App makes the following outbound requests:
api.mcservermanager.com, our own service. On launch and about every 12 minutes the App fetches our settings and announcements, which sends nothing about you. Signed in, it's also used for your account, licence checks, relays, billing, the Server List and the AI toolsapi.ipify.org, which the App asks for your public IP address when you open a server, so it can show it on the Network tab. Nothing else is sent, ipify sees the request come from your addressmc-heads.net, for player heads (it's sent the player's name or ID)pack.mcservermanager.com, our own file storage, where a listed server's icon is kept so the Server List can show itWhile the App is in Limited Mode (Lite, or the direct download before a licence is on it) it sends us how long it's been used in the current session, whether the timer ran out, the App's version and edition and a hashed device identifier, which is what the Limited Mode timer runs on.
The normal release of the App does not collect analytics or transmit any data beyond what is described above and under Error reports below, with two exceptions. Beta tester builds send a device identifier and your IP address on launch to protect unreleased builds, as described under Beta testing data above.
And once per install, the first time someone joins a server you run, the App sends one anonymous report to api.mcservermanager.com: how many minutes that took from the first time you opened the App, the App's version and edition, the server type and whether a relay and the Getting started card were in use. It carries no email, licence, device identifier, server name or player name. We don't keep your IP address with it, it's only held for 15 minutes to stop the same address sending hundreds. We use it to see how long it takes a new user to get a friend on, so we can make that quicker.
The App keeps a log of what it does on your computer, in its own data folder, for three days. That log includes the console output of the Minecraft servers it runs. Two things can send parts of it to us, both only with your say so:
api.mcservermanager.com with your account email. Each time it starts it also sends the end of the previous session's log, whether or not anything went wrong.Before either leaves your computer the App removes email addresses, licence keys, dashboard codes, IP and MAC addresses and your Windows username from paths. Server names, player names and your PC's name are left in. Reports are used only to find and fix problems, are never sold or shared with anyone else, are kept for 30 days and then deleted. Every request for full logs is recorded on your account's log, with whether it was allowed or refused.
All Minecraft server files, world data, automatic backups and local application settings are stored on your computer. They don't leave it unless you send them yourself: a backup or modpack you put in Cloud Storage, a file you upload through the web dashboard, or logs you allow support to have.
On this website your browser keeps a few things in its own local storage: your sign in, the two-factor remembered browser token if you tick it, where your visit came from (above), your last support chat so it's there if you come back and display choices like the dashboard theme. Clearing site data for mcservermanager.com removes all of it.
That includes the record of which players have already been shown the in-game vote message, which the App keeps in its own data folder so that a restart does not start the messages over.
If you are based in the UK or EU, you have the right to:
To exercise any of these rights, contact us at support@mcservermanager.com or via our Discord. We aim to respond within 30 days.
These rights are not only for account holders. If you play on somebody else's server and you are in the shared player record described above, the same rights apply. Tell us your Minecraft account identifier, or your in-game name and which server it was, then we will find and remove your rows. You do not need an account with us to ask.
You must be at least 13 years old to create an account. We do not knowingly collect personal data from children under 13. If you believe a child has created an account, contact us and we will remove it. Beta testing involves agreeing to the tester terms, so testers are reviewed for age and normally need to be 18 or older.
We will notify users of significant changes via email or an in-app notification. The "Last updated" date at the top of this page reflects the most recent revision.
Questions or concerns about this policy can be sent to support@mcservermanager.com.
© 2026 Natchland Studios. All rights reserved.