Last updated August 25, 2026

Privacy Policy

We do not sell, rent, or trade your data. Ever, to anyone.
We do not serve advertising or share data with advertisers or data brokers.
We do not use your data to train machine learning or AI models.
We do not build profiles of individuals for any purpose beyond the specific feature that a server has enabled.
We do not read direct messages between users, and we do not store message content from channels where no relevant feature is enabled.

Data we receive from Discord

Discord gates certain categories of data behind “privileged gateway intents”, which an application must be approved to use. mira requests three. Each one powers specific features that cannot work without it — none of them are used for bulk collection or analysis.

Server Members

Lets mira see when someone joins, leaves, or has their roles or nickname changed. This is what makes welcome and goodbye messages, automatic role assignment on join, sticky roles that survive a rejoin, level-based role rewards, birthday announcements, boost tracking, and raid detection possible. Without it, mira cannot react to a member arriving at all.

Presence

Used for status-based role automation. A server can offer a role to members who advertise the server’s invite in their custom status, and mira must observe status changes to grant that role when the invite appears and revoke it when the member removes it. There is no command or interaction that fires when someone edits their status, so this cannot work without the intent.

Presence data is evaluated at the moment it changes and is not retained. We do not log online and offline history, and we do not store any record of a member’s status or activity.

Message Content

A number of mira’s features have to evaluate messages from members who never invoked a command, which is something slash commands and interactions structurally cannot do. These are:

Automated moderation — detecting spam, mass mentions, invite links, flood attacks, and configurable banned-phrase filters, and applying escalating timeouts.
Anti-raid honeypot — comparing content posted in a decoy channel against known spam and phishing patterns to catch compromised accounts before they reach real channels.
Response triggers — server-defined phrases that produce an automatic reply or reaction.
Keyword highlights — notifying a member by DM when a word they subscribed to is mentioned, which requires checking messages they will never see.
Activity levels — awarding experience for participation, weighted by the effort a message represents. A server can configure a character-length threshold above which a message earns a bonus multiplier, which requires measuring the message itself rather than merely counting that one was sent.
Starboard, counting, sticky messages, and AFK detection, each of which reacts to ordinary messages rather than to a command.

Message content is evaluated in memory as messages arrive and then discarded. The one exception is described in the next section.

When message content is stored

One feature stores message content rather than only evaluating it. Snipe lets a moderator recover a message that was just deleted or edited in a channel, which is used to catch slurs, scam links, and harassment that a bad actor deletes seconds after posting.

Stored for 30 minutes, then deleted automatically.

Recently deleted and edited messages are held for a maximum of 30 minutes and are then purged by an automatic job. There is no archive, no backup copy, and no way for us or anyone else to retrieve a message after that window has passed.

Only the most recent messages in a channel are retained, and only for that channel and server.
Server administrators can disable the feature entirely, or restrict it to specific channels and roles.
Clearing a channel's snipe history through mira deletes those records immediately.

Separately, mira records that a message was sent — its identifiers and a timestamp, without any content — so that features like activity statistics and moderation purge tools can function. That record contains nothing you wrote.

Voice recording

One optional feature records a voice channel and produces a written summary. It only runs when a member explicitly starts it, participants are notified while it is active, and any member can opt out permanently — opted-out members are excluded from recording entirely.

Recordings and transcripts expire automatically and can be deleted on request at any time. They are never used to train models and are never shared outside the server that created them.

Data at a glance

What we store	Why	How long
Server and channel IDs	Storing per-server configuration and knowing where features are enabled	Until mira leaves the server
User IDs	Linking settings, levels, cases, and opt-outs to the right person	Until removed on request or the feature is disabled
Deleted / edited message content	Snipe, used for moderation recovery	30 minutes, then purged automatically
Message metadata (no content)	Activity counts and moderation tooling	Until mira leaves the server
Command usage	Debugging, abuse detection, and rate limiting	Rolling window, then discarded
Moderation cases	Giving moderators a durable record of warnings, mutes, and bans	Until deleted by the server or mira leaves
Submitted content	Tickets, confessions, tags, and custom messages you or your server created	Until deleted by you or the server

Username history

mira records public username, and display name changes so that moderators can see whether an account has recently changed identity. This is a standard moderation signal: ban evasion and impersonation almost always involve a rename, and the history is what makes it visible.

Only public profile information is recorded — nothing private, and nothing you have not already displayed to everyone who can see your profile.
You can request removal of your own history at any time using the contact methods below, and it will be deleted.

The website and dashboard

If you sign in at mira.party, you authorise us through Discord’s OAuth2 flow. We receive your user ID, username, avatar, and the list of servers you can manage — only so the dashboard can show you the right servers. We never receive or store your Discord password or IP address.

Session tokens are stored in your browser and expire. We use privacy-preserving, aggregate analytics to understand page traffic; it does not build a profile of you or follow you across other sites.

How we protect data

All traffic between mira, Discord, and our website is encrypted in transit.
Databases are not publicly reachable and are restricted to our own infrastructure.
Credentials you supply for optional features are encrypted at rest.
Access to production systems is limited to the operators who maintain the service.

No system is perfectly secure, and we cannot guarantee absolute protection. If a breach ever affects your data, we will disclose it in our support server as promptly as we are able.

Your choices

Almost every feature is off by default and must be deliberately enabled by a server administrator.
Administrators can disable any feature, restrict it to certain channels, or exclude specific roles and members.
Individual features that act on members provide their own opt-outs where relevant.
You can unlink any third-party account you have connected, at any time.
You can leave a server, or ask its administrators to remove mira, to stop all processing for that server.

Deletion and data requests

You can ask us what data we hold about you, ask for it to be corrected, or ask for it to be deleted. Contact us through either route below and tell us your Discord user ID. We will verify that the request comes from the account in question and act on it within 30 days.

When mira is removed from a server, that server’s configuration and associated records are deleted. Data required for abuse prevention — for example a record that a server was terminated for breaching our terms — may be retained for as long as necessary to enforce that decision.

Children

mira is not directed at children below Discord’s minimum age requirement, and we do not knowingly collect data from them. If we learn that we hold data belonging to someone below that age, we will delete it. If you believe this has happened, contact us and we will act on it.

Changes to this policy

As mira’s features change, this policy will change with them. The date at the top of this page always reflects the current version, and material changes will be announced in our support server before they take effect.

Contact

For privacy questions, data requests, or anything else covered by this policy, reach us at either route below.

Support server: discord.gg/SFBA7WVCvw
Email: 1@dra1n.ing