Last updated: October 20, 2026
This policy explains what data the Discord bot Miyu (application ID 851859544559714336) collects, why, how long we keep it and how you can get it deleted. It applies wherever Miyu is used: in servers it has been added to and in direct messages with it.
Miyu is developed and operated by TeamQuantum. The person responsible for your data (the "controller" under the GDPR) is:
Miyu is not affiliated with or endorsed by Discord Inc. Your use of Discord itself is governed by Discord's Privacy Policy.
To work, Miyu receives events from Discord about the servers it is in. Most of this is handled in memory and is never written to our database. Section 3 lists what we do store, and section 6 covers our log files.
| What Miyu reads | When | What happens to it |
|---|---|---|
| Text of messages in channels Miyu can see | Every message | Checked for a Miyu command and, if the server has quote embeds on, for links to other messages in the same server. With text levels on, the message only counts towards your XP. The text is discarded afterwards. |
| Linked messages (quote embeds) | When someone posts a link to a message in the same server | Miyu fetches that message and re-posts its text in the channel. It only does this if the person posting the link can read the original channel. |
| Ticket channel messages and attachments | When a ticket is closed | Miyu writes a transcript (.txt) and a zip of the attachments and posts both to the ticket log channel the server's staff set up. We keep no copy; the transcript then lives in that server on Discord. |
| Members joining and leaving | Join roles or event logging turned on | Join roles: Miyu gives new members the server's default roles. Event logging: Miyu posts a join or leave note to the server's staff log channel, including which invite was used. |
| Server member lists | While Miyu is running | Miyu keeps the member lists of the servers it is in in memory to look members up. They are not written to our database. |
| Your Discord activity (presence) | Twitch auto-promote turned on in a server you are in | Miyu only looks for a "Streaming" activity with a Twitch link. When you go live, it posts an announcement in the server's chosen channel, at most once every 12 hours. To enforce that limit it remembers your user ID and the time of the last announcement in memory for 12 hours. |
| Reactions, channel changes and invites | Event logging turned on | Posted as notes to the server's staff log channel. Invites are also stored for invite tracking (section 3). |
| Keywords in specific channels of servers we run | In those channels only | Miyu replies automatically, for example with links to crisis hotlines in a venting channel. |
Server admins decide which of these features are active in their server.
We store the data below in our own database. We do not store message content from conversations, presence or activity data, or server member lists. The only text we keep is what you or a moderator deliberately enter for a feature (a reminder, a moderation reason, a verification message).
| Data | What exactly | When it is created |
|---|---|---|
| User record | Discord user ID, username, time of your last command, anti-spam counters | The first time you use a Miyu command |
| Command log | Command name, whether it worked, error reason, run time, time, your user ID, server ID | Each time you use a text command |
| Levels | Per server: text XP and level, voice XP and level | Levels are on and you chat or use voice |
| Voice sessions | User ID, server ID, session ID, start and end time | Voice levels are on and you join a voice channel |
| Action counters | Who used a social command (such as hug or pat) on whom, which one, how often | You use one of these commands |
| Moderation records | User ID, moderator ID, sanction type, reason entered by the moderator, duration, time, who pardoned it | A moderator warns, mutes, kicks or bans someone with Miyu |
| Reminders | Your user ID, who set it, channel, reminder text, time, repeat interval | You or someone else sets a reminder for you |
| Invite tracking | Invite code, channel, creator's user ID, uses, maximum uses, expiry | Event logging is on and an invite is created or used |
| Scheduled jobs | Member ID and server ID | A new member is waiting for delayed join roles (removed from the queue about a day after the job has run) |
| Server data | Server ID, name, member count, date Miyu joined or left, settings (prefix, enabled modules, channel and role IDs, verification message, ticket categories, staff and join roles) | Miyu is added to a server or an admin changes a setting |
This data is stored on servers we control at OVH Groupe SA, France. Certain data is also cached in memory (Redis) for speed.
We only use your data to run Miyu's features, keep servers safe and keep the bot working.
| Purpose | Data used | Legal basis (GDPR) |
|---|---|---|
| Features you use yourself: commands, reminders, tickets, quotes | User record, reminders, message text in memory | Art. 6(1)(b): providing the service you ask for |
| Features a server's admins turn on: levels, join roles, event logs, Twitch announcements | Levels, voice sessions, action counters, member events, presence in memory | Art. 6(1)(f): the legitimate interest of server admins and us in running their community |
| Moderation and safety: sanctions, invite tracking, spam protection | Moderation records, invite tracking, anti-spam counters | Art. 6(1)(f): keeping servers safe from abuse and raids |
| Keeping Miyu running: finding and fixing errors | Command log, application logs | Art. 6(1)(f): operating a reliable service |
We do not use your data for advertising or profiling, and we do not sell it.
We do not sell your data, share it with advertisers or use it to train AI or machine-learning models. It only reaches others in these cases:
Stored data is kept until someone asks us to delete it. There is currently no automatic expiry for most of it.
| Data | How long |
|---|---|
| One-time reminders | Deleted once sent, or when the channel or the member is gone |
| Recurring reminders | Until removed with the reminder commands |
| All other data in section 3 | Until you, the server's admins or Discord ask us to delete it, including after Miyu leaves a server |
| Application logs | Kept in size-limited files; the oldest are deleted once 480 MB is reached. They contain user and server IDs, usernames, server names, errors, the text of text commands that fail, and the Twitch channel name of members Miyu announced as live |
| Data held in memory (section 2) | Lost when Miyu restarts; the Twitch announcement limit after 12 hours |
We will also delete stored data when it is no longer needed for Miyu's features, if Discord asks us to, or if we stop running Miyu.
If your data is ever accessed without permission, we will inform Discord and, where the law requires it, the affected users and the data protection authority.
To get a copy of your data or have it deleted, open a ticket in our support server or email [email protected]. We answer within one month.
We will ask you to confirm the request from the Discord account the data belongs to, so nobody else can request it. Moderation records about you are kept if a server's staff still need them for safety; we will tell you if that applies.
Under the GDPR you have the right to:
Server admins can turn individual features off with the modules command (m!modules disable <module>). Removing Miyu from a server does not delete that server's data yet. The server owner can ask us to delete it the same way.
Miyu is only for people who meet Discord's minimum age in their country. We do not knowingly collect data about anyone younger. If you think we hold such data, contact us and we will delete it.
When this policy changes, we update the date at the top and announce larger changes in our support server.
Questions about this policy: [email protected] or our support server.