Privacy Policy

Core Mita reads messages so it can filter out content that breaks the law or the server rules. This page explains exactly what it reads, what it leaves behind in Discord, and how to have it removed.

Effective 3 November 2026

Reads

Messages in channels it can see, and the text inside images and attachments it scans. Handled in memory and dropped.

Stores

Nothing about you. Only server settings — channel IDs, keyword lists. Every moderation notice goes to a private staff channel, and the bot keeps no copy.

Never does

No selling, no advertising, no profiling, no content sent to outside analysis services, no AI training on your messages.

1Who this policy is about#

Core Mita is a moderation and utility bot run by the administration of this server (“we”, “us”). It runs only here.

This page covers Core Mita only. Discord processes your data under Discord’s Privacy Policy; other bots in a server have their own policies.
Where data protection law such as the GDPR applies, we are the controller of the data described on this page.
The bot is an independent community project. It is not operated by, endorsed by, or affiliated with Discord Inc.

2What Core Mita does#

Core Mita watches messages posted in channels it can access and compares their text against filters — keywords and patterns — looking for content that may break the law or the server rules. Where applicable, it also reads the text inside images and attachments. Matches are posted to a private staff channel, where moderators decide what to do: remove the message, warn, time out, ban, or nothing at all.

The check happens inside the bot, on the machine that runs it. Core Mita has no separate website or backend, and it does not send message content to any outside service for analysis, translation or storage.

When a moderator acts, Core Mita posts a short notice in that staff channel: the action taken, the reason, your user ID, who acted, and a link to the message. The notice is an ordinary Discord message. The bot keeps no copy of it, and it disappears when staff delete it.

Core Mita may also send you a direct message when something happens to your account — a warning, a timeout, a ban. These notices are one-way, and nothing in them is recorded.

3What Core Mita handles, and where it goes#

This is the complete list. The bot’s own database holds exactly one thing: server settings.

Data handled by Core Mita, whether the bot stores it, and where it ends up
Data	What it involves	Bot stores	Where it ends up
Message text	The text, embeds and link previews the bot receives from channels it can see.	No	Checked in memory, then dropped.
Images & attachments	Files downloaded to the bot’s own machine and read for text (OCR). They are never uploaded anywhere.	No	Deleted right after reading.
Match details	Which rule or keyword matched.	No	Written into the staff notice when action is taken.
Moderation notice	Action taken, reason, your user ID, the moderator’s ID, timestamp, a link to the message, and any note.	No	Posted in a private staff channel; stays there until staff delete it.
Sanctions	Warnings, timeouts and bans, with their expiry.	No	Timeouts and bans are enforced by Discord. Warnings and notes exist only as notices in the staff channel.
Server settings	Server, channel and role IDs, keyword and filter lists, log channel.	Yes	The bot’s own database; deleted when the bot leaves the server.
Notification DM	A message telling you that action was taken on your account.	No	Not recorded.

The bot’s database contains server settings and nothing else: no user IDs, no message text, no history of who said what. The notices live in the staff channel, where nothing expires automatically — the bot stores nothing it could expire. Staff delete them once a case no longer needs them, and you can ask us to delete yours at any time (section 8).

4What we never do#

We do not sell or license your data, and we do not share it with data brokers or advertising networks.
We do not use it for advertising or marketing, and the bot does not message you about anything unrelated to moderation.
We do not profile you or map your relationships with other users, and we do not combine them with anything else to build a picture of you.
We do not send message text, images or attachments to any external API — no cloud OCR, no translation service, no AI provider.
We do not use your messages to train machine learning or AI models.
We do not keep message history, and we do not retain content after a message is removed.
We do not keep a database of moderation records. There is no archive of your messages and no profile of you on our side.
We never ask for your password, token or any other login credential.

5Why we are allowed to process it#

Legitimate interests (GDPR Art. 6(1)(f)): keeping the community safe, applying the rules consistently, preventing ban evasion and handling appeals. We keep almost nothing on our own systems, so this interest does not outweigh your rights.
Legal obligation (Art. 6(1)(c)): where we must keep or disclose something to comply with the law or a valid legal request.
Consent: we do not rely on consent to screen messages, because moderation is a condition of taking part in the server. If the law requires consent for something specific, we will ask for it separately.
Special categories: a filter may incidentally match content that reveals sensitive information, but that content is not stored, so it is not retained. Staff are told not to write such details into notes; if one slips through, you can ask us to remove it.
Automated filtering: the first pass is automatic, but it does not decide your standing in the server on its own. Warnings, timeouts and bans are applied by a moderator, and you can ask for any action to be reviewed.

6Who can see it#

Moderators and administrators who can read the staff channel, and the bot’s operator. Anyone without access to that channel cannot see the notices.
Our hosting provider, which supplies the machine the bot runs on. It processes only the traffic needed to run the bot and is not permitted to use it for anything else; the notices are not on its machines. If you need its name, ask staff.
Discord — messages pass through Discord’s systems regardless of the bot; see Discord’s Privacy Policy.
Authorities, only where the law requires it or where it is necessary to protect someone from harm.

Nobody else. There are no advertising partners, analytics vendors or data brokers in this picture.

7Your rights#

If the GDPR or UK GDPR applies to you, you have the right to access your data, correct it, have it erased, restrict or object to processing, and receive it in a portable format. You also have the right not to be subject to a decision based solely on automated processing, and the right to complain to your national supervisory authority.

If you are in California, you have the right to know what we hold, to delete it, to correct it, to opt out of sale or sharing (we do neither), and not to be treated differently for exercising those rights.

To use any of these rights, contact the moderators as described in section 8. We answer within 30 days, at no cost, and we may ask you to confirm that the account is yours before we act.

8Access and deletion requests#

How to make a request

Contact any moderator — through the server’s support or ticket channel, or by direct message to a staff member.
Include your Discord user ID, what you want (a copy, a correction, deletion), and anything else that helps us find the notice.
We may ask you to send the request from the account itself, so we can tell it is you.
We confirm and act within 30 days. If we need longer, we tell you why.

What we delete: the notices about you in the staff channel, including any note and the link to the message. Deleting the message is what deletion means here — the bot holds no other copy.

What we cannot delete: a ban. Timeouts and bans are Discord features rather than records we hold, so removing the notice does not lift them. If you want a sanction reviewed, say so in the same request.

Discord may keep a removed message in its own backups for a while. That copy is outside our control and covered by Discord’s Privacy Policy.

9How we protect it#

There is very little to protect. The bot’s database holds server settings, reachable only with credentials held by the operator. Moderation notices sit in a private channel guarded by Discord’s own permissions, so only staff who already have that access can read them. Message content is never written to disk. This page is served over HTTPS.

If unauthorised access occurs and it is likely to affect your rights, we will inform the affected users and Discord, as the Discord Developer Terms require, and we will fix the cause.

10Age#

Discord is for people aged 13 or older, or older still where local law sets a higher minimum. Core Mita is not directed at children, and we do not knowingly hold data about them. If you believe a minor’s data has ended up in a notice, tell the moderators and we will delete it.

11This website#

This page is a static document: no cookies, no analytics, no tracking pixels, no third-party scripts or fonts. Your browser fetches one file and that is all. Our hosting provider may keep standard access logs — IP address, browser, time of request — for security and abuse prevention; those logs are not used to identify visitors or combined with anything the bot holds.

12Changes#

This policy has an effective date at the top of the page. If we change how Core Mita handles data, we update that date and announce the change in the server. If you do not agree with a change, you can leave the server and ask us to delete your data.

13Contact#

Write to any moderator of the server — in the support or ticket channel, or by direct message to a staff member from the member list. That is the fastest route and the one we monitor.

Requests are accepted from current and former members alike. If you have left the server or been removed, message a moderator directly; if you cannot reach one, rejoin through the invite on the bot’s profile and open a ticket.

If you think Core Mita has made a mistake — a wrong match, a message removed by accident, a bug — tell the moderators the same way. The same people read it.