IdleCraft is a Discord bot that runs AFK Minecraft bots from a control panel in Discord, and gives Discord server staff moderation, AutoMod and server tools. This policy explains what data IdleCraft handles, why, who can see it, and how to have it deleted. By using IdleCraft you agree to this policy and to the Terms of Service.

1. The short version

• IdleCraft keeps only what it needs to run your bot and the features a server turns on: your Discord user ID, the Discord server you registered in, the Minecraft server address and port you entered, your bot's username, and a generated in-game password. Server staff features also keep moderation records (section 2).
• IdleCraft can read messages in servers where it is present, so that commands typed as normal messages, AutoMod, auto-responses and similar features work. It does not save the text of ordinary messages and never sells it. Section 3 explains exactly what happens to message text.
• When your bot joins a Minecraft server, the full server address is posted in the official IdleCraft Discord server so other members can join (see section 5).
• You can delete your registration at any time with the Delete button on the panel.

2. Data we store

When you register a bot:

• Your Discord user ID
• The ID of the Discord server you registered through
• The Minecraft server address and port you entered
• Your bot's username (the one you chose, or a default)
• A random password for the bot's account on that Minecraft server. You never choose or see it, and it is not your Discord or Minecraft account password. We store it so your bot can log in.
• A session ID, when the registration was made, whether your bot is set to run, and when it was last used. This lets bots resume after a restart and lets us remove unused registrations.
• A short history of your bot's connection events (for example connected, kicked, reconnecting) with the short reason the Minecraft server gave. It never includes passwords or full server addresses.

When a server administrator or manager configures IdleCraft for their Discord server (for example with /panel setup):

• The server ID, panel channel ID and panel message ID
• Role and channel IDs for panel access, staff roles, log channels and manager roles
• Settings such as command on/off switches, command aliases and role or channel restrictions, session limits, the server's default Minecraft server, and shared-access settings
• AutoMod settings: which protections are on, thresholds, the server's own custom filter words, link rules, and exempt roles and channels
• Text the server's staff write for the bot to send: welcome and goodbye messages, custom commands, auto-responses, automatic reactions, and scheduled announcements, plus the roles given to new members
• The ID of the person who changed a setting, and timestamps

When moderators use moderation tools, or AutoMod acts:

• A case record: case number, type (for example warning, timeout, ban), the affected member's user ID, the moderator's user ID (or AutoMod), the reason text, the time, and any expiry time
• Schedules for temporary bans and similar timed actions, so they still run after a restart
• "Stop Ping" records: the user IDs of people who triggered mass-mention or repeated-ping protection. These IDs may also be written to a list file kept by the bot's operator.
• An audit log of administrative actions: who did what, in which server, when, and whether it worked, with a short note. It does not include message text.

Other data:

• Reports you send with /report: the text you write, your user ID, the server ID and the time
• Reminders you create: the reminder text, your user ID and the time it is due
• Blocks: when we block a server or a user for abuse, the ID, the reason, who added the block, and timestamps

3. Data we handle but do not store

• Discord interactions. Button presses, slash commands and form input are processed to carry out your request.
• Message text. In servers where IdleCraft is present, it can see the text of messages together with who sent them and where. It checks them to recognise commands typed as normal messages, to run AutoMod (word, link, invite, mention, spam, capital-letter and repeat checks) and to trigger auto-responses and automatic reactions the server has set up. IdleCraft does not save ordinary messages. When AutoMod acts, the record keeps the rule that triggered and a short note, not a copy of the message. Staff members with moderation permissions are exempt from AutoMod.
• Message logging (optional). If a server administrator turns on logging, the text of messages that are edited or deleted is copied into that server's own log channel, where Discord keeps it and the server's staff can read it. Only messages IdleCraft had already seen can be logged.
• Member joins and leaves. If a server has turned on welcome, goodbye, auto-role or logging features, IdleCraft uses the member's ID and username to send the message, assign the role or write the log entry.
• In-game chat. Your bot is a Minecraft client. It reads chat from the Minecraft server it is on, in real time, to spot login prompts and queue messages and to choose a short canned reply. IdleCraft does not save that chat or forward it to Discord.
• Join events in the official server. In the official IdleCraft server only, when someone joins, IdleCraft briefly mentions them in the welcome channels and deletes the message. It uses only the new member's user ID and stores nothing.
• Translation (optional). If the operator has connected a translation service, text you send with /translate is passed to that service to be translated, and nothing is stored by IdleCraft.
• Operational logs. Our hosting provider keeps logs with bot names, Discord IDs, status events (connected, kicked, reconnecting) and errors. We use them for troubleshooting and abuse prevention.

4. How we use data

• Run your bot and keep it connected, including restarting it after a redeploy
• Show panels, check permissions and run commands
• Run the moderation, AutoMod and server tools that a server's staff turn on, and keep the records those tools need
• Send timed actions (temporary-ban expiry, reminders, announcements)
• Send you status updates and moderation notices
• Keep one bot per user and one registration per Minecraft server address
• Remove unused registrations
• Troubleshoot problems, review reports and prevent abuse
• Answer support requests

5. Where your data appears

• Log channels. If your Discord server has one, IdleCraft posts status messages there: your mention, your bot's name, a partly hidden server address, and events such as connected, kicked or reconnecting, including the kick reason sent by the Minecraft server. If the server uses moderation, AutoMod or logging features, those records (who was warned, timed out or banned and why, AutoMod actions, joins, leaves, and edited or deleted messages if enabled) are posted there too. Anyone who can read that channel can see them.
• Direct messages. IdleCraft messages you when your bot joins, stops or gives up, and when a moderator or AutoMod warns, times out, kicks or bans you (if your DMs are open). Some commands that show private information, such as your account details, reply by direct message when used as a typed message instead of a slash command. If a DM can't be delivered, we do not retry it.
• Public join announcement. When your bot joins a Minecraft server, IdleCraft posts the full server address and port, your Discord mention and your bot's name in an announcement channel in the official IdleCraft Discord server. This happens even if you registered through a different Discord server. Repeat joins to the same address are announced at most once every 10 minutes. If you do not want a server address shared, do not register it.
• Bot head image. Status messages show a Minecraft head image loaded from mc-heads.net, using your bot's username in the image address.

6. Third parties

• Discord carries all bot messages and interactions.
• MongoDB Atlas hosts our database, which is encrypted at rest and in transit.
• HidenCloud hosts the bot.
• The Minecraft server you register receives your bot's username, its generated password (through the in-game /register and /login commands), and everything the bot does and says in game. That server's owner can see and log it, and their own policies apply.
• mc-heads.net serves the bot head image in status messages.
• A translation service, only if the operator has connected one, receives the text you ask to translate.

We do not sell your data, show ads or use analytics trackers.

7. Who can access your data

• Your registration belongs to the Discord server you registered in. Other servers' panels and administrators cannot view or control it.
• Administrators of the server you registered in can see when your bot connects and disconnects (event names only, not your server address or the reasons), and can stop your bot if you have given them access or they are authorized by that server's settings.
• Each server's moderators and administrators can see that server's moderation records, audit log, settings and AutoMod records. They cannot see another server's.
• The IdleCraft owner and staff of the official server can see who has an active bot, can stop or remove registrations, can view reports, and can block servers or users, for support and abuse prevention. The owner can also make a protected backup of the database on the hosting machine for recovery; backups contain the data listed in section 2 and are never sent through Discord.
• We share data with the providers above to run IdleCraft, and with authorities when the law requires it.

8. Retention and deletion

• Delete button. Pressing Delete on the panel removes your registration and stops your bot straight away.
• Automatic cleanup. A registration that has not been started for 7 days, and whose bot is not connected, is deleted automatically.
• Staff removal. Staff of the official server can remove a registration with /unregister.
• Connection history is deleted automatically after 30 days.
• Audit log entries are deleted automatically after 180 days.
• Reports are deleted automatically after 90 days.
• Reminders and scheduled announcements are removed 7 days after they have been delivered or cancelled.
• Moderation cases are kept so servers keep an accurate history. Servers can archive cases, which hides them from normal views but keeps them, and you can ask us to delete yours.
• Server settings. Panel, role, log channel, AutoMod and other server settings are kept until an administrator changes them or asks us to delete them.
• Block records are kept as a moderation history.
• Backups made by the owner keep only the most recent copies on the hosting machine; older ones are deleted automatically.
• Logs. Hosting logs are kept for as long as our hosting provider retains them.

To ask for access to or deletion of your data, contact us in the support server: https://discord.gg/MfwFebzdpc. We may need to verify who you are, and we may keep records we are legally required to keep or need to prevent abuse. Content that has been copied into a server's own log channel is controlled by that server's staff and Discord, and you should ask them to remove it.

9. Security

IdleCraft keeps its tokens and database credentials in environment variables, generates passwords with a secure random generator, checks permissions every time a command is used, keeps each Discord server's data separate from the others, and never shows bot passwords in Discord. No online service is completely secure, and we cannot control how a Minecraft server handles the data your bot sends it.

10. Children

IdleCraft is not for anyone under 13, or under the minimum age Discord allows in your country. If you think a child has used it, tell us in the support server and we will remove their data.

11. International processing

Our providers may process data in countries other than yours.

12. Changes

We may update this policy as IdleCraft changes. The new version will be posted on this page with a new "Last updated" date, and we will announce major changes in the support server.

13. Contact

Questions or requests: the support server at https://discord.gg/MfwFebzdpc.