Games server status — Privacy Policy
This policy explains what the Games server status Discord bot ("the bot") stores, why, for how long, and how to have it removed. It is written to match what the bot actually does; if the bot changes, this page will be updated.
Who operates it
The bot is operated by an individual in the United Kingdom ("the operator"), reachable on Discord as patryk3327. It is a hobby project, not a company.
What is stored
| Data | Why | Who provides it |
|---|---|---|
| Discord server (guild) IDs, channel IDs, message IDs and the ID and token of the webhook the bot creates in a status channel | To post and keep updating status messages, alerts and voice-channel names in the right place | Created when an administrator uses /addserver, /addstatus or related commands |
| Game server addresses (hostname or IP and port), display names, server type, optional icon URL and trigger words | To query the game server and display its status | Entered by the server administrator |
| Discord user IDs chosen to receive offline alerts | To mention those users when a server goes offline | Entered by the server administrator |
Discord user IDs with a weekly count of /server wake uses | To enforce the five-per-week wake limit | Generated when someone uses that option |
Audit entries for the Start button, /server checks and /server wake: the user's Discord tag and ID, the Discord server and channel IDs where it was used (or that it was a direct message), the address checked, the result and the time | So the operator and (optionally) a log channel chosen by the operator can see who is checking and waking servers, and act on misuse | Generated when the feature is used, including from direct messages and from servers the bot is not in when added as a user app |
| Command-usage lines (Discord tag and command name) in the bot's log file | Troubleshooting | Generated on each command |
| Names of the players currently online, as the game server itself publishes them in its public status (Minecraft Java's player sample, Eaglercraft's player list) | Shown at the bottom of /server replies and status messages so people can see who is playing | Published by the game server. The bot holds them only in memory to notice changes and does not save them to disk or write them to its logs. They stay visible in Discord as part of the message: a status message shows the current list at each update, and a /server reply keeps the last list it showed. |
| Per-server availability history (online / offline / sleeping / starting / unknown and when) | Uptime figures for the last 7, 31 and 365 days and the /uptime history | Generated by the bot; contains no personal data |
What is not stored
- Message content. The bot may receive message content from Discord in order to answer its text command, but it does not store, log or analyse messages. It reads only message metadata (author, timestamps) to keep its own status messages at the bottom of a channel.
- The text of direct messages or group chats. When the bot is added as a user app its slash commands work there, and only the command, its options and the audit entry above are recorded. Voice and presence information are never received.
- No analytics, tracking, advertising identifiers or profiling of any kind.
Who it is shared with
- Discord, necessarily, to post messages — subject to Discord's privacy policy.
- The game servers being monitored or checked: the bot connects to their public status port to check whether they are online, which reveals the bot's own IP address to them. Monitored servers are checked every 30 seconds; a
/servercheck is repeated every 30 seconds for up to 10 minutes so its reply stays up to date. No user data is sent. - Cloudflare (1.1.1.1) and Google (8.8.8.8): the bot sends a network ping to 1.1.1.1 every 30 seconds, and briefly connects to both when several servers stop answering at once, to tell whether its own internet connection is up. Only the bot's IP address is revealed; no user data is involved.
- mcsrvstat.us: server icons on
/serverreplies and status messages are loaded fromapi.mcsrvstat.us, so the hostname of the game server is sent there (by the bot when a server is added, and by Discord when it shows the picture). No user data is sent. - Audit entries may be delivered to the operator's Discord DMs and to a log channel configured by the operator.
- Nothing is sold, and nothing is shared with anyone else.
Where it is kept
All data is held in files on hardware owned and operated by the operator in the United Kingdom. It is not stored with any cloud provider. Access is limited to the operator.
How long it is kept
- Server and channel configuration: until an administrator removes it (
/removeserver,/removestatus) or the bot is removed from the Discord server. - Availability history: 366 days (it feeds the 365-day uptime figure).
- Weekly wake counts: reset every Monday 00:00 UTC.
- Log files: rotated by size, about a week of history is kept.
- Audit messages sent to Discord remain there until deleted by the operator.
Your choices and rights
- Removing the bot from a Discord server stops all monitoring of that server and automatically deletes that server's configuration, availability history and the status messages the bot can still reach; an administrator can also delete configuration first with the commands above.
- Removing the bot from your own account (Discord settings, Authorized Apps) stops its commands working for you in direct messages and in servers it is not in. Wake counts and audit entries already created are kept until they expire or you ask for them to be deleted.
- Players who do not want their name shown can turn off Allow Server Listings in Minecraft Java's settings; the bot then only counts them. Server owners can hide the whole list (for example
hide-online-players=trueinserver.properties), in which case only the player count is shown. - To have a user ID removed from alert pings, ask the server's administrator, who can edit the server with
/editserver. - To ask what the bot holds about you or to have it deleted, message the operator on Discord — patryk3327. Requests are handled manually and without charge.
Age
The bot is for use on Discord and follows Discord's minimum-age requirements. It does not knowingly collect anything from anyone below that age.
Changes
This policy may be updated when the bot changes. The date at the top shows the current version.