Privacy Policy

Effective October 3, 2026

MC Status is operated by fabra, who is responsible for the data described here. This policy covers the Discord bot and this website. It is meant to meet Discord’s Developer Terms, including a clear description of what we collect, how we use and share it, and how you can ask us to change or delete it.

What we collect

From Discord’s APIs we store only what the bot needs:

• Discord server (guild) IDs and the plan assigned to that server.
• Monitor settings, including poll interval, alert flags, and Discord channel or message IDs used for live status.
• The Discord user ID of a person who redeems a license key or submits a report through a Discord command.
• Reports you send with /privacy report or this website, including the category and your message.

From you and from public Minecraft queries we also store:

• Minecraft server addresses, ports, editions, and display names you add.
• Recent status snapshots such as online state, player counts, version, MOTD text, latency, and check times.
• Downtime incidents derived from those checks.
• License key hashes and prefixes, expiration or revocation times, and which Discord server redeemed a key. We do not store the full key after it is shown.

What we do not collect

The bot uses the Guilds gateway intent only. It does not request message content. It does not collect emails unless you put one in a report or we publish an operator email for contact. It does not ask for passwords, tokens, or Discord login details. This website does not use advertising cookies.

How we use data

We use this data to poll Minecraft servers you added, update status messages, enforce plan limits, issue and redeem licenses, receive and review reports, and keep the service working. We do not use Discord API data to profile people, advertise, train machine-learning models, or decide eligibility for housing, employment, or similar benefits. We do not sell API data or send it to data brokers or ad networks.

Why we process it

We process Discord API data because you invited the bot and asked it to monitor servers (to perform that service) and to meet Discord’s developer rules, including reviewing reports and deleting data when it is no longer needed. Minecraft queries are sent only to addresses someone added.

Sharing

Data is processed on the servers that run the bot, PostgreSQL, and Redis. Those hosts act only for this service. We also send or edit Discord messages through Discord. When a monitor is enabled, the bot queries the public Minecraft address you provided; that query is visible to the target server as ordinary status traffic. If MCSTATUS_BASE_URL is set, that provider sees the address being queried. We do not share data with advertisers.

Retention

• Status history is kept for 14 days, then pruned.
• Guild, monitor, channel, message, and license-redemption records stay until the bot is removed, someone with Manage Server runs /privacy delete, or we shut the service down.
• A global Minecraft server record and its history are deleted when no Discord server is still watching that address.
• Your Discord user ID on a license redemption or report is removed or anonymized when you run /privacy forget-me.
• Reports are kept for 90 days so they can be reviewed, then deleted.

Your choices

• Users with Manage Server can remove Minecraft servers with /server remove and wipe the Discord server’s stored data with /privacy delete.
• Anyone can remove their own user ID with /privacy forget-me.
• Removing the bot from a Discord server deletes that server’s stored data. A later cleanup also deletes records for Discord servers the bot is no longer in.
• Use /privacy policy in Discord, or this page, to see the policy. Use /privacy report or the report form to ask a question, report a problem, or request a change we cannot do with those commands.

Children

The bot is not directed at children under 13, or under the minimum age required in their country. We do not knowingly store Discord API data of children below that age.

Security

We use commercially reasonable safeguards, including hashed license keys and TLS when talking to Discord. Production database connections should use TLS. Encryption of disks at rest is the hosting operator’s responsibility. If we learn of unauthorized access to Discord API data, we will notify Discord and affected users as Discord’s Developer Terms and applicable law require.

International processing

Data may be processed in the country where the operator hosts the bot, PostgreSQL, and Redis. If that is outside your country, including transfers involving Discord users in the EEA or UK, we rely on Discord’s developer terms for those transfers and on the host’s safeguards.

Contact

Questions, deletion requests you cannot complete with the commands above, and privacy reports can go to fabra. Email fabra@olivr.cc. You can also use the report form or /privacy report in Discord.