Privacy Policy

Last updated 29 October 2026

Undefined Moderation (“the Bot”, “we”, “us”) is a moderation and community-management bot for Discord servers, together with this web dashboard. It is run by Undefiend Studios. This policy explains what information the Bot handles, why, who can see it, how long it is kept, and what you can ask us to do. By adding the Bot to a server, using its commands, or signing in to the dashboard you accept this policy. If you don't, please don't use the Bot.

1. What we handle and keep

The Bot only stores what is listed here. Everything is stored per server, so one server's data is never shown to another server.

Server settings. Choices made by a server's admins: log and report channels, Staff and Management roles (as IDs), AutoMod rules and word lists, welcome and verification text, reason templates, lockdown options, and similar. Stored as Discord IDs and the text the admins typed.
Moderation cases. When a moderator warns, times out, kicks, bans or unbans someone, adds a note, or when AutoMod or another automatic feature acts, we record: the member's Discord user ID and username at that moment, the moderator's ID and username, the type of action, the reason text, the duration (if any), the time, and anything staff later add: evidence links, comments, and the previous wording if a reason was edited. Private moderator notes are stored the same way. Warning points are calculated from these cases rather than stored separately.
Custom commands. The commands a server creates (people run them with /cc): their names, responses, options, the roles and channels they refer to, how many times they were used and when last, and the ID and username of the person who created them.
Premium slots. If you are given a Premium slot we store your Discord user ID and username, when the slot was given and when it ends, which server you put it on and when, who gave it to you, and an optional note from us (such as a purchase reference). We don't take payments or payment details on this website.
Temporary working data. The channels the Bot has locked and who locked them (so they can be unlocked correctly), and, for servers that kick members who don't verify in time, the member's user ID, the server ID and the deadline.
Dashboard sign-in. If you sign in with Discord we ask for the identify and guilds permissions. We store your user ID, username, avatar identifier and the IDs of the servers you are in, for up to 7 days or until you log out. We use Discord's access token only during sign-in and then revoke it. We keep only a one-way hash of your session identifier. Which servers you can manage is checked again live with Discord each time.

2. Messages and other things we read but do not store

Message content. In servers where the feature is on, the Bot reads messages as they are sent to run AutoMod and to write message edit and delete logs. Messages are checked and then discarded. They are not saved in our database. To detect spam and repeated messages, AutoMod keeps timing information and a simplified fingerprint of recent messages in memory for about two minutes; it is lost whenever the Bot restarts.
Logs and reports inside Discord. If a server turns on event logs, the Bot posts the content of edited or deleted messages, joins, leaves and role or nickname changes to the log channel that server chose. Reports sent with /report (reporter, reported person, message text and reason) are posted to that server's staff channel. Once posted, that content lives in Discord, under that server's control, and is not copied into our database.
Other Discord information. To do its job the Bot reads server, channel, role and member information that Discord provides (for example your roles, to know whether you may run a command). Unless it is listed in section 1, we don't store it.
Direct messages. The Bot may DM you, for example to tell you that you were warned, timed out, kicked or banned, to send a welcome message, or when you use a custom command that answers privately.
Technical logs. The software writes operational logs (errors, the server and command involved, and, when our support team uses its access, who used it and where). If error reporting is enabled, the same errors are posted to a private Discord channel with passwords and tokens removed. When you open this website your IP address is visible to the server that hosts it. We use it only for short-lived, in-memory rate limiting and do not store it in our database. Our hosting provider may keep ordinary server logs.

3. Cookies

The dashboard uses two cookies and nothing else: oauth_state (for the few minutes a sign-in takes, to protect against forged logins) and sid (your login session, up to 7 days). Both are strictly necessary. We don't use analytics, advertising or tracking cookies, and the dashboard loads no third-party scripts.

4. Why we use it

To provide the Bot's features (moderation commands, AutoMod, logs, verification, welcome messages, custom commands, reports, the dashboard), to keep it secure and prevent abuse, to find and fix problems, and to answer your questions. We do not sell your information, use it for advertising, or build profiles of people for other purposes.

5. Who can see it

The server you are in. Moderators and admins of a server (people with moderation permissions or the server's Staff or Management roles) can see that server's cases, notes and settings through commands and the dashboard. Server owners and admins decide what is recorded and why; they are responsible for telling their members and for following the rules that apply to them. Members can't see other members' cases or private notes.
Our support team. To provide support and investigate abuse, our support team can run any command in any server the Bot is in, and can therefore see and change that server's data. This access is logged.
Service providers. The Bot's data is held in a database and on a host operated by providers we choose, who may process it only to run those services for us.
Discord. The Bot runs on Discord, which receives everything the Bot sends through it and has its own Privacy Policy.
Others, only if required. We may disclose information if the law requires it, or to protect people from serious harm or to protect the Bot from abuse.

6. How long we keep it

Settings, cases, notes and custom commands are kept while the Bot is in the server.
If the Bot is removed from a server, that server's data is deleted automatically after 30 days. Adding the Bot back within that time cancels the deletion.
Warnings that moderators pardon and notes they remove are marked inactive; they can remain in the record and in the case history until the server's data is deleted or you ask us to delete them.
Premium slot records are kept as a record of what was given while they are needed to run Premium and deal with questions about it. A slot's link to a server is removed when that server's data is deleted.
Dashboard sessions end after 7 days (or when you log out) and are then deleted automatically.
Channel locks and pending verifications are removed when they are resolved, and with the rest of the server's data.
Backups kept by our database provider, if any, are overwritten on their normal schedule.

7. Your choices and rights

Ask us. You can ask us what we hold about you, to correct it, or to delete it. Contact us by email at [email protected], or in our Discord support server with your Discord user ID and, if you can, the server ID. We may need to confirm it's you. A server may have a legitimate reason to keep a record of moderation (for example keeping a community safe); we will take that into account and tell you what we can and can't do.
Depending on where you live you may have further rights, such as to object to or restrict processing, or to complain to your data-protection authority. We'll respect those that apply to you.
Stop dashboard access. Log out, or remove the app under Discord → User Settings → Authorized Apps.
Server owners can remove the Bot at any time, which starts the deletion described above.

8. Security

We take reasonable steps to protect the data: session identifiers are stored only as hashes, dashboard changes are protected against forged requests, and access to a server's data is limited to people who hold the right permissions there. No system is perfectly secure, so we can't promise absolute security.

9. Children

The Bot is not directed at children. You must meet Discord's minimum age (13, or higher where your local law says so) to use Discord and therefore the Bot. If you believe we hold information about a child who is too young, contact us and we will delete it.

10. Where data is processed

Data is processed and stored where our hosting and database providers operate, which may be outside your country. Discord itself is based in the United States.

11. Changes

We may update this policy as the Bot changes. The date at the top shows when it last changed, and we will make any important change visible, for example in the Bot's announcements. Using the Bot after a change means you accept the new version.

12. Contact

Questions or requests about this policy: contact us by email at [email protected], or in our Discord support server.