Miku Open dashboard

Privacy Policy

Last updated: November 6, 2026

This explains what the Miku bot, the website at mikubot.app and the dashboard at dash.mikubot.app keep, why, and what you can do about it. "We" means the people who run Miku. The owner goes by Ozora on baff.

The short version

  • Miku doesn't listen to voice chat and never records audio
  • Miku doesn't save your messages. If a server turns on message logs, they're posted to that server's chosen log channel
  • We keep what's needed to run your server's music and your dashboard login
  • We don't sell your data, show ads or use analytics or trackers

What Miku keeps about servers

When Miku is in a server, we store:

  • Settings: server ID, station or mix, volume, shuffle, loop and 24/7 mode, plus the DJ role if you set one
  • Where it's working: the voice channel it's in, the text channel and message for the music panel, and the song and spot it's on so it can pick back up after a restart
  • Server details for the dashboard: the server name, the names and IDs of its text and voice channels, and the names and IDs of its roles

What Miku uses but doesn't keep

When you run a command or press a button, baff.gg sends Miku that action along with your user ID and permissions, so it can answer you and check that you're allowed to do it and that you're in the right voice channel. Miku also sees who is in voice channels so it can join your channel, notice when a channel is empty and show listener counts. We don't save this to our database or link it to you. Miku only keeps totals, like how many people are listening across all servers, and some of those totals appear on our public status page.

Voice and messages

Miku only sends music into voice channels. It's set up not to receive anyone's audio, so nothing you say reaches it, and nothing is ever recorded. Miku receives the messages in channels it can see, because baff.gg sends them to every bot. Without Logging set up, it ignores them.

If a server turns on Logging

Server admins can choose to have Miku post what happens in their server into a log channel. Depending on what they turn on, those posts can include message text, edits, deleted messages, file names, who joined or left, role and nickname changes, voice activity and moderation actions, with the user involved. Anyone who can see that log channel can see them, and those posts stay there like any other message until the server deletes them. To show what a deleted or edited message said, Miku holds the last 500 messages per channel in memory. That memory isn't saved to our database, and it's wiped whenever Miku restarts.

We save each server's log settings: the chosen channels, ignored channels and roles, and whether logging is on. The Dashboard Changes list also saves the user ID and name of whoever changed those settings, what they changed and when, keeping the latest 200 changes per server.

If a server uses Moderation

When moderators use Miku's moderation tools, Miku keeps a record so the server can look back on it. Server admins and moderators can see these records.

  • Cases: your user ID and username, the moderator's user ID and username, the action, the reason, any proof they attached, how long it lasts and when it happened. This includes bans, kicks and timeouts done outside of Miku, which Miku reads from the server's audit log.
  • Reports: who reported, who was reported, the reason, any comment or proof, and a copy of the reported message if one was attached.
  • Appeals: your user ID and username, your answers, the case you appealed and the decision.
  • Message histories: if a moderator runs /archive, Miku saves a copy of those messages, including who wrote them and links to any files. A moderator can turn on a link that lets anyone with that link read it.

Miku may also DM you about a punishment, a report you made or an appeal. Which details are in that DM is up to the server.

If a server uses Join Roles

Server admins can give people roles when they join. If an admin adds someone to the list for extra roles, we save that person's user ID and those roles until they get them or an admin removes them. While someone waits on a delay or the server's rules, we briefly save their user ID so Miku knows who to come back to.

If a server uses Reaction Roles

When you react to a Reaction Roles message, Miku reads that reaction to give or take the role. Miku doesn't save it.

If a server uses Auto Moderation

Miku reads messages in that server as they're sent to check them against the server's rules. It keeps a short recent history in memory to spot spam and doesn't write it to disk. Join Guard checks your name, avatar, account age and server tag when you join. Any action it takes can create a moderation case, which is kept like any other case.

If you log in to the dashboard

You log in through baff.gg. We ask for two permissions: identify and guilds. We never ask for your email, and we never see your baff password. We keep:

  • Your profile: your user ID, display name and avatar
  • Login tokens from baff.gg: these let the dashboard keep you logged in and check which servers you can manage

Your list of servers is fetched from baff.gg when needed and held in memory for about 30 seconds. We don't save it to our database. Changes you make in the dashboard are sent to the bot and saved as that server's settings, and we don't keep a history of who changed what.

Cookies and browser storage

We only use what's needed to make the site work:

  • miku_oauth keeps your login safe while it's happening, and lasts up to 10 minutes
  • miku_session keeps you logged in, until you close your browser or for up to 90 days if automatic login is on
  • miku_auto remembers automatic login, for up to 90 days

If you press "Don't show again" on a dashboard popup, that choice is saved in your own browser and never sent to us.

Visiting the website

You don't need an account to browse the public site. There are no analytics, ad networks or third-party scripts, and our fonts and images are served from our own server. We don't keep a log of page visits. Avatars and server icons in the dashboard load from baff.gg, so baff.gg can see those requests.

Why we use it

We use this information to play music, remember your settings, come back after restarts, log you in, check you're allowed to manage a server, keep Miku running and fix problems. That's all. We don't use it for ads or sell it to anyone.

Who else is involved

  • baff.gg is the platform Miku runs on and handles login, so its own privacy policy applies there
  • OVHcloud hosts our server in Canada, which is where this data is stored
  • Cloudflare handles our domain's DNS, but site traffic doesn't pass through it
  • Let's Encrypt provides the HTTPS certificates

We may also share information if the law requires it, or if it's needed to protect Miku or the people using it.

How long we keep it

  • Server settings stay until someone asks us to delete them, even after Miku leaves. That way your setup is still there if you add it back.
  • Channel and role names are removed when Miku leaves the server.
  • The current voice channel and song are cleared when you run /stop.
  • Login records are deleted when you log out, and we also ask baff.gg to cancel your tokens. If you never log out, the record is deleted automatically about 90 days after it stops being used.
  • Server logs are for fixing problems and can include server IDs and error details. Old entries are dropped as log space fills up.
  • Backups of our server are kept automatically by our host, so deleted data can remain in a backup for a while after we remove it.

Totals and uptime history aren't about any one person, and we keep those.

Moderation cases, reports and appeals stay until a server admin deletes them or asks us to remove the server's data. Message histories are deleted automatically after 2 years, or sooner if a moderator deletes them.

Your choices

  • Log out of the dashboard to delete your login record
  • Remove Miku from your server to stop it collecting anything there
  • Ask us to see, fix or delete your data, or a server's data if you manage that server

Depending on where you live, you may have other rights over your data, such as objecting to how it's used or complaining to a privacy regulator. To ask us for anything here, contact Ozora on baff. We handle these requests by hand, and we may need to confirm that you're the right person first.

To have a moderation record about you changed or removed, start by asking the server's admins, since they control those records. If that doesn't work, contact us.

Keeping it safe

The site uses HTTPS and our server is locked down, we only store a scrambled version of your session cookie, and your baff.gg login tokens are encrypted. No system is perfectly secure though, so we can't promise nothing will ever go wrong.

Kids

Miku isn't meant for anyone under 13, and we don't knowingly collect data from them. If you think a child's data is here, let us know and we'll remove it.

Changes to this policy

We'll update this page as Miku changes, especially when new features collect something new. We'll change the date at the top when we do.

Contact

Questions or requests? Reach out to the owner, Ozora, on baff.