Privacy
The bot keeps what it needs to play music correctly and remember your server's settings, and since version 2.0 it also records listening stats to power leaderboards, badges and Wrapped. Below is all of it, stated plainly, and you can turn off or delete your part.
What the bot stores
- Per-server settings: server ID, DJ role ID, default volume, and the switches for fair queue, track title on the voice channel, and 24/7 mode (with the voice channel the bot should stay in).
- Saved queues: track names or track identifiers, plus the voice and text channel IDs, so playback can be restored after the bot restarts.
- Listening history: which track played, when, which user (Discord ID) requested it, and which users (Discord IDs) were listening in the channel at the time.
- Each user's π π ratings and favorites list.
- Playlists (
/playlist): personal playlists tied to the owner's Discord ID, and server playlists tied to the server. Each playlist stores its name and the tracks in it. - Each user's quiz scores and badges, per server.
- Contribution records (if the feature is on): the sender's Discord ID, file name, size, SHA-256 hash, the file's tags, review status and rejection reason.
- Audio files awaiting review, kept temporarily until approved or rejected (deleted on rejection, or after 14 days if nobody reviews them).
- Track suggestions (
/request) and the list of people who voted. The bot only records the text and never opens or downloads the link you give it. - Auto-generated tags and audio features (tempo, energy, brightness) for each track in the music library, if the bot owner enables them. This is data about the music files and is not tied to any user.
- Everything above is tied to Discord user IDs and server IDs.
- Operational logs: when an error occurs, the logs on the machine running the bot may record server IDs, channel IDs and track names.
What the bot does not do
- It does not read message content. The bot only uses slash commands, buttons, the quiz answer dialog and voice channel state.
- It does not record voice channels. The bot only plays music into the channel and never captures anyone's audio.
- It does not sell or share data with advertisers or third parties.
What the data is used for
To make the bot work: remembering server settings, restoring queues after a restart, and tracking down the cause of errors. To power the stats features: /mystats, /leaderboard, /wrapped, badges, quiz leaderboards, favorites lists, playlists, the shuffle weighting in /nhaajt (tracks with a π turn up more often) and the ordering of /radio rounds (based on the server's π/π, skipped tracks and usual listening hours).
Track title on the voice channel
The bot writes a "Now playing: track title" line into the voice channel's status, so anyone who can see that channel can see the track title. Admins can turn it off with /settings vc-status.
Direct messages from the bot
The bot sends direct messages (DMs) to report the result of a contributed-file review, to tell you when a file matches a track you suggested or voted for, and to send the bot owner a review request that includes the file name.
External services (only if the bot owner enables them)
The auto-tagging feature (AUTOTAG=on) sends an audio fingerprint (a condensed string of numbers, not the music file) along with the duration of an untagged track to AcoustID, and the file name to MusicBrainz, then downloads cover art from the Cover Art Archive. No Discord user information is sent. Tempo analysis runs entirely on the machine running the bot.
The /display status page (if the bot owner enables it) shows what is playing on the bot owner's own machine or home network; the page does not show IDs or requester names and hides itself during a music quiz.
Your rights: turn off and delete
/privacy stats: turn recording of stats about you on or off. When it is off, the bot stops recording your listening history./privacy delete: delete the data the bot holds about you, including listening history, ratings, favorites, personal playlists, quiz scores and badges, and anonymize your suggestions and contributions. Files that were already approved stay in the library but are no longer tied to your name.
Server playlists belong to the server, so they are not deleted with your data; whoever may change server playlists (the DJ role, if one is set) removes them with /playlist delete. You run the two /privacy commands yourself, with no need to ask anyone.
Third parties
Discord processes messages, commands and voice under Discord's own policies. When you ask for a track to be played, the machine running the bot sends the request to the music source (YouTube, SoundCloud, Spotify), so that source sees the request coming from the bot's server, not from your device.
Online lyrics lookup is optional: when it is on, the bot sends the track title, artist name and duration of the current track to the public LRCLIB service to fetch the lyrics. The host can turn this off. Lyrics taken from a .lrc file or from the music file's tags are not sent anywhere.
How long it is kept, and how to delete it
Data stays on the machine running the bot until it is deleted. You can delete your own data with /privacy delete. A server admin can ask for all of their server's data to be deleted at any time by contacting the bot maintainer (nhaajt) at the address in the last section.
If you self-host
The data lives on your own machine, in the data folder next to docker-compose.yml. In that case you manage it and are responsible for it, including whether LRCLIB lookup is on or off; this page only describes how the bot stores things.
Contact
If you have questions or want your data deleted, message the bot maintainer:
Instagram: @nhaajt_hehee • GitHub: nhaajtt (you can also open an issue on the musiDISCORD repo)