Privacy policy
Last updated 4 October 2026
What NatchGSM collects about you, why, how long it's kept, who else handles it and what you can do about it.
The short version
- The app and the service run on your own machines. Your game servers, worlds, backups, logs and settings stay there. We never see them, unless you copy backups to the cloud, which we store for you without opening them.
- On their own they only ask us for updates and for the settings people use most. Those requests carry nothing about you.
- An account is an email address and a password we can't read.
- Linking a host lets your web dashboard reach it through our servers. What passes through isn't stored.
- A linked host tells us which of a game's settings people change or search for, never the values or what was typed.
- If you add the Discord bot, what it passes between your servers and Discord isn't stored, apart from a 30 day log of what it did for you. A player who links Steam leaves us only their verified Steam id.
- No ads, no analytics, no tracking. We never sell your data.
1. Who we are
NatchGSM is made by Natchland Studios, a sole trader in the United Kingdom trading as Natchland ("we", "us", "our"). We're the controller of the personal data this policy describes. Write to us at support@natchgsm.com about anything here.
2. What stays on your machine
The app, the background service, the helper and the command line tool run on machines you control. Your game servers, their worlds and saves, their backups, logs and settings are stored there and never sent to us.
- A linked host keeps its secret key for natchgsm.com, your account id and your email address in its own data folder, in a file only the service can read.
- The app keeps your sign-in in your user settings folder, encrypted on Windows.
- When you pair the app with another of your machines, they connect to each other directly. That doesn't go through us.
- If you sign in to Hytale for a Hytale server, that sign-in is kept on the host and talks to Hytale's own services, not ours.
3. What the software sends on its own
- Update checks. An installed service asks natchland.com for the newest version two minutes after it starts and once a day after that. The request names NatchGSM's version (like NatchGSM/0.2.0) and nothing else. An update is only downloaded when you choose to install it.
- Popular settings. Now and then the service asks natchgsm.com which settings people use most for its games, whether or not it's linked to an account. Like an update check, it sends nothing beyond the request itself.
There are no analytics, crash reports, hardware identifiers or IP address lookups. The only id the service has is a random one it makes the first time it runs. Like any request on the internet, these come from your IP address, which Cloudflare sees to deliver them.
When you install or update a game server, your machine downloads what it needs straight from the source: Valve's SteamCMD signed in anonymously, Java from Adoptium on GitHub, Oxide or Carbon from GitHub, plugins from uMod and Hytale's own downloader. Webhooks you set up send what you picked, like server and player names, to the address you gave, like a Discord channel. Those go from your machine to them, under their own privacy policies. We never see them. When NatchGSM installs Carbon for a Rust server, it turns Carbon's own analytics off.
4. Your account
When you make an account we keep:
- your email address
- your password as a PBKDF2 hash with a salt of its own, so we can't read it or get it back
- when the account was made, when you confirmed your email and whether it's an admin account
- which version of the terms of service and this policy you agreed to and when
- if we suspend the account, when and the reason we gave you, until the suspension is lifted
- for each browser or app you're signed in on, a hash of its session key, whether it's a browser or an app, an app's name with your computer's name in it (like "NatchGSM on Charlie's PC"), when it was made, when it was last used and whether it was signed in with a two-factor code
- if you turn on two-factor sign-in: the key your authenticator app makes its codes from, encrypted, when you turned it on and which 30 second window the last code you used was from, so no code works twice. Your ten recovery codes are kept only as keyed hashes, with when each was used. While you're setting it up, the key is kept for 30 minutes and deleted within two hours if you don't finish. All of it is deleted when you turn two-factor sign-in off or delete the account. Making new recovery codes deletes the old ones
- between your password (or the code from a password reset email) and your two-factor code, a hash of a short-lived key for that step, how many wrong codes it's had and, for a reset, a hash of the new password you picked. It lasts 5 minutes and is deleted when it's used or within an hour after it runs out
- the six digit codes we email you, only as hashes, with how many wrong tries each has had
- a record of each email we send you (the address, what it was for and when), so a retry never sends it twice
5. Device sign-in and linked hosts
- When the app, the command line tool or a host asks to be linked, we keep hashes of its codes, what kind of device it is, its name (your computer's name), its operating system, processor type and NatchGSM version, a host's random id, then who approved or refused it and when.
- For a linked host we keep its id, name, operating system, processor type, NatchGSM version, which features that version says it has, a hash of its secret key, when it was linked and when it was last seen.
- A linked host keeps a connection to natchgsm.com open. When you open the web dashboard, what it shows passes through our servers between the host and your browser: your servers, their consoles, players, settings and the machine's processor, memory and disk use. None of it is stored. The host is told the email address of the account that opened each dashboard session and writes it to its own log.
- When you share a host with someone, we keep the email address you invited, the role and servers you picked and when, until they accept or decline it, you cancel it or it runs out a week later. We email that address once for each invite, with your email address and the host's name in it.
- For each person a host is shared with we keep their account, the role, the servers and when they were added. They see your email address and the host's name, you see their email address. What they do on the host goes in its own activity log on your machine, under their email address, like anything done from the dashboard.
6. The Discord bot
If you add NatchGSM's bot to a Discord server, it works for you and for the people in that Discord server.
- For each Discord server you add it to, we keep its id and name, the Discord user id of whoever added it and when, which Discord roles you gave a NatchGSM role, which of your game servers it reaches with each one's name, game and what it can do, the channel joins, leaves and chat go to and the role players get for playing there.
- Adding it goes through Discord's own page. Discord gives us a key to read who added it. We read their user id once and hand the key straight back.
- When someone uses one of its commands or buttons, Discord sends us their Discord user id, their name in that server and their roles. We pass the command to your host, which writes their name and Discord user id in its own activity log on your machine. We keep a log of what the bot did for 30 days: when, their name in that server, the command, whether it worked and a short detail like the server's name, a console command or a player's name. You see it on the dashboard's Discord page.
- Joins, leaves, public chat and wipes from the servers you picked pass through our servers to the channel you picked. They're never stored. A team's own chat is never passed on, nor is anything else a game marks as private.
- A player who uses /link goes to Discord's own page, which asks them to share their connected accounts with us. We keep only the Steam account ids Discord has as verified, with their Discord user id and when, hand Discord's key straight back and keep nothing else. It's kept until they use /unlink. When the bot sees that Steam id on a server with a player role, it gives them the role and keeps which role it gave whom, so a wipe takes back only those.
7. Settings usage
A linked host tells us which of a game's own settings people change and search for, like decay.scale for Rust. For each one we keep the game, the setting's name, whether it was changed or searched for, the host's account and when that was first and last seen. We never get the value a setting was given or what was typed into a search.
It's counted per account, so it only says how many accounts use a setting. We use it to rank each game's most used settings, which the app shows first for everyone. A setting only appears in that ranking once at least three accounts use it and the ranking only ever shows counts, never who.
A host only sends this while its account has agreed to the current terms of service and this policy. The rows are deleted with the account. To stop it, unlink your hosts, or ask us and we'll delete what's been recorded for your account.
8. Moderation across servers
With the NatchGSM subscription, your Rust servers ask natchgsm.com about each player who joins and send it the reports players make in the game with F7. You and the people you share a host with can keep notes on players too. That means we keep details about your players for you. We use them only to run moderation for your servers, never for anything else. They're only ever shown to you and the people you've shared a host with.
- For each of your servers that asks: its id and name, which host it's on, a hash of the key in its addresses and how many times it asked in the current minute, day and hour, to hold it to its limits.
- Bans you share to every server: the player's Steam id and name, the reason, when it ends, who made it and from which server, until it ends or is lifted.
- Reports: the Steam id of the player who sent it, the Steam id and name of the player it's about, the kind of report, its subject and message, which server and when, plus who marked it dealt with and any note your staff added. The screenshot and the details of the server's machine the game adds are thrown away, never stored.
- Notes: the player's Steam id and name, the note, who wrote it and when.
- History: each kick, ban, mute and lifted ban or mute your servers made, with the player's Steam id and name, the reason, when it ends, the server and who did it.
- Whether a ban is shared to every server unless whoever bans says otherwise.
A game server asks from its own IP address, which Cloudflare sees to deliver it. We don't keep it. If your subscription ends, nothing here is deleted, it just stops being used until you subscribe again.
9. Cloud backups
With the NatchGSM subscription, your hosts can copy their backups to the cloud: by hand, every backup or one a day, as you set it for each server. A backup holds the server's world and saves as the game writes them, which can include your players' ids, names and what they built. We store it for you and never open it, look inside it or use it for anything else. You reach it through any of your hosts and on the dashboard's Cloud backups page. People you share a server with reach that server's own backups through the host, as their role allows.
- The backup itself, a zip file, in Cloudflare R2 storage under your account.
- About each one: the host and server it came from with their names at the time, the game, the backup's own name and when it was made, why it was taken (by hand, on the schedule and so on), how many files it holds, its size, its SHA-256 checksum, whether your setting or a person copied it and when it was stored.
- While one is going up: which parts have arrived, each with its checksum, so it carries on after a restart. An upload nothing arrives for in a day is given up and its parts deleted.
- How many backups and bytes your account copied up in the current day, to hold it to its limits.
A backup stays until you remove it, your server's keep count replaces it with a newer one, or your account is deleted. Unlinking a host, or losing the machine, doesn't delete its backups, they belong to your account. If your subscription ends, nothing is deleted: you can still download and restore every backup you have, only new copies stop. Downloading never costs anything. Deleting your account deletes every backup from storage first.
10. Game requests and votes
When you ask for a game we keep its name, the Steam app id if you gave one, your note and that you asked. Only we see the note. For each vote we keep which request, your account and when. The public list shows each request's name, status, vote count and any note we've added. It never shows who asked or voted.
11. Getting help
The contact form emails us your topic, your message and your email address, or your account's address if you're signed in. It adds your account id when you're signed in and what your browser says it is (its user agent), so we can help with the right thing. It goes to support@natchgsm.com, which Cloudflare forwards to our own inbox. It isn't stored in our database. Emails you send us, through the form or directly, stay in our inbox as long as we need them to help you.
12. Keeping accounts safe
- To stop password guessing and spam, we count sign-ins, codes, two-factor codes, sign-ups and contact messages per IP address, per email address and per account. Those counters are deleted within about a day.
- We email you when two-factor sign-in is turned on or off and when one of your recovery codes is used, so you'd know if it wasn't you.
- When something goes wrong, our code writes a short log line that can include an account id, a host id or the email address a message was going to. We read these live to fix problems and don't store them.
- Changes our admins make to game requests and accounts are logged with the admin's name. An entry about an account, like a suspension, keeps its email address and the reason for a year, even if the account is deleted, then both are removed.
13. Payments
Nothing is paid for yet. When paid plans arrive, payments go through Stripe. Starting a checkout makes a Stripe customer with your email address and account id. We then keep the Stripe customer id, the checkout's id and your subscription's status, plan, whether it's monthly or yearly, when it renews, whether it's set to cancel and when a payment failed. Your card details go straight to Stripe. We never see or store them.
14. Cookies and your browser
- One cookie,
__Host-ns_session, keeps you signed in. It's only sent to natchgsm.com, scripts can't read it and it runs out 30 days after you last used it. The site needs it to work, so it doesn't ask first. - Your browser's local storage keeps your theme choice under
ns-theme. Nothing else is kept there. - The pages load nothing from anyone else. No analytics, ads, tracking pixels or outside scripts, fonts included.
15. Who else handles it
- Cloudflare runs natchgsm.com: the website, our database, the connections between linked hosts and the dashboard, the emails we send, the cloud backups you copy up and the forwarding of email to support@natchgsm.com. Every request to the site passes through Cloudflare, with your IP address. Cloudflare's Privacy Policy
- Stripe will handle payments once paid plans exist. Nothing goes to Stripe before you start a checkout. Stripe's Privacy Policy
- Google holds the support emails you send us, since our inbox is in Gmail. Google's Privacy Policy
- Discord carries the bot's commands, its replies and the messages it posts, if you add it to a Discord server or use it in one. Discord's Privacy Policy
- Our own server holds the update files. Update checks reach it through Cloudflare.
We don't sell your data or share it with anyone else. Nothing is ever used for ads.
Our database is in Western Europe. Cloudflare, Stripe, Google and Discord are US companies that handle data in data centres around the world. Where your data leaves the UK, it's covered by the safeguards in their own data processing terms.
16. Why we use it
UK data protection law asks for a reason for each use, called a lawful basis.
- To give you what you asked for (contract): your account and sign-in, emailed codes, linking devices, the web dashboard, sharing a host, moderation across your servers, the Discord bot, cloud backups, game requests and replies when you ask for help.
- Your players: for the details of your players that moderation keeps, we act for you, running it as you and your staff set it up. Keeping order on your servers is your legitimate interest, so tell your players in your server rules that bans, reports and notes are kept this way.
- Legitimate interests: keeping accounts safe with rate limits, session records and error logs, ranking the settings people use most and keeping a record of admin changes. You can object to these, see your rights below.
- Legal obligation: keeping payment records for tax, once there are payments.
17. How long it's kept
- Your account
- Until you delete it from your account page or ask us to
- Sessions
- 30 days after you last used them, or until you sign out
- Email codes
- 15 minutes to use, deleted a day after that
- Two-factor key and recovery codes
- Until you turn two-factor sign-in off or delete the account. An unfinished setup, two hours at most
- Two-factor sign-in steps
- 5 minutes to finish, deleted within an hour after that
- Device sign-ins
- 10 minutes to approve, deleted a day after that
- Linked hosts
- Until they're unlinked or the account is deleted
- Invites to share a host
- Until they're accepted, declined or cancelled, or a week, then deleted within an hour
- People a host is shared with
- Until the owner removes them, they leave, the host is unlinked or moves to another account, or either account is deleted
- Discord servers the bot is in
- Until you remove it or the account is deleted, then it leaves them
- What the Discord bot did
- 30 days
- A player's linked Steam ids
- Until they use /unlink
- Player roles the bot gave
- Until it takes them back at a wipe, the server is taken off the bot or the bot is removed
- Discord sign-in links
- 10 minutes to use, deleted within an hour after that
- Settings usage
- Until the account is deleted
- Reports from your game servers
- 30 days at most, fewer when an account has more than 3,000, then deleted within an hour
- Moderation history
- A year at most, less when an account has more than 50,000 entries, then deleted within an hour
- Shared bans
- Until they end or are lifted, then deleted within an hour
- Notes on players and your servers' moderation addresses
- Until they're removed, the host is unlinked (for the addresses) or the account is deleted
- Cloud backups
- Until you remove them, your server's keep count replaces them or the account is deleted. Never because a subscription ended
- Cloud uploads that stop
- A day after the last part arrived, then given up and deleted within an hour
- Votes
- Until you take them back or the account is deleted
- Game requests
- They stay on the list, with nothing linking them to you once your account is deleted
- Emails we sent you
- The record of who and when, 30 days
- Admin log entries about an account
- The email address and reason in them, a year
- Rate limit counters
- About a day
- Support emails
- As long as we need them to help you
- Payment records
- As long as UK tax law requires
- Database history
- Cloudflare keeps a rolling history of our database for restores, so anything deleted is gone from it within 30 days
18. Your rights
Under UK data protection law you can ask us for a copy of what we hold about you, ask us to correct it, delete it, limit what we do with it or give it to you in a form you can take elsewhere. You can also object to anything we do for legitimate interests. It's free.
Email support@natchgsm.com from the address on your account. We may ask you to confirm it's you. We answer within a month.
To delete your account, use Delete account on your account page, or ask us the same way and we'll do it for you. If you're subscribed, cancel the subscription first. Deleting it removes it along with its sessions, codes, device sign-ins, linked hosts (which then stop connecting), the invites it sent, who its hosts are shared with, the hosts shared with it, the Discord bot's settings and log (the bot leaves those Discord servers), votes, settings usage, everything kept for moderation across servers and every cloud backup. What stays: a game you asked for stays on the list without your name on it, payment records the law says we keep and emails in our inbox. Our database history rolls off within 30 days.
If you're unhappy with how we've handled your data, tell us first so we can put it right. You can also complain to the Information Commissioner's Office at ico.org.uk.
19. Children
There's no minimum age. A child's account holds exactly what anyone else's does, the things listed above and nothing more. None of it is used for ads or profiling. A parent or guardian can ask us for a copy of what a child's account holds or for it to be deleted, by emailing support@natchgsm.com. We may ask them to confirm they're the parent or guardian first.
20. Changes to this policy
The date at the top says when this policy last changed. When a change matters, you'll be asked to agree to the new version the next time you use your account on natchgsm.com.
21. Contact
Questions about your data go to support@natchgsm.com, or use the contact page.