Privacy Policy
On this page
This Policy comes in two versions, Portuguese and English, with the same content. Each version applies to the people who read it in that language. If they differ, the Portuguese version applies.
In short
- We keep the minimum the bots and the panel need to work: your Discord ID, your preferences, your favorites and server settings.
- We do not sell, rent or disclose your data. We do not use your data for advertising.
- The bots do not record or listen to call audio.
- Data is stored in Brazil.
- You can delete your data at any time, with a bot command or a button in the panel.
- Questions and requests: legal@empirecommunity.org.
This summary helps you read, but it does not replace the full text below.
1. Who we are
The party responsible for your data (the "controller" under the LGPD and the GDPR) is Leone S Martins, founder of EmpireCommunity, on behalf of the community. EmpireCommunity is a community based in Brazil.
We have no named data protection officer (DPO). We are a small-scale data processing agent, which Brazil's data protection authority (ANPD) exempts from naming one. The channel for anything about your data is the e-mail legal@empirecommunity.org.
This Policy applies to the EmpireMuse bots run by EmpireCommunity and to the EmpireCommunity panel. EmpireMuse is free software: whoever runs their own copy decides about, and is responsible for, that copy's data.
2. Data we process
| Category | Examples | Where it comes from | What it is for |
|---|---|---|---|
| Discord identity | ID, username, display name, avatar | Discord, when you use a bot or sign in to the panel | Knowing who asked for each action and showing your profile in the panel |
| Your server list | For servers you can configure: ID, name, icon and your permissions. For other servers you are on where one of the bots is too: only the ID | Discord, at panel sign-in | Showing the servers you can configure and those where you can pick your favorite radios. Kept only in the session, never saved |
| Your preferences | Personal prefix, favorite songs, favorite radios (your account's and your own on each server), radio filters, saved queue, the last 6 songs you played, the status app (Rich Presence) token | You, through commands and the panel | Keeping your choices and showing your recent history |
| Last.fm (optional) | Your Last.fm username, the access key, whether scrobbling is on, the songs you listen to in the call | You, when you link the account | Sending what you listen to to Last.fm, if you turn the integration on |
| Server settings | Language, DJ roles, channels, appearance, server playlists, Jukebox, radios, the server's favorite radios and the ID of whoever changed a radio | Server administrators | Making the bot work the way the server chose |
| Playback | Song queue, who requested each song, session history | Using the bot in a call | Playing the songs and resuming the player if the bot restarts |
| Supporter mark | The marked server and the ID of the team member who granted the mark | The team, when granting the mark | Enforcing the server's access to the features Limited to Supporters |
| Usage statistics | Time, bot, server and channel (ID and name), command used, whether it worked, song played and for how long | Using the bot | Understanding usage and fixing problems. Does not record who used it |
| Technical and security logs | IP address, page visited, date and time of access, error codes with user, server and channel IDs, panel actions (the name of the field changed, never the value) | Using the bot and the panel | Protecting the service from abuse and investigating errors |
| Join and leave notices | A notice that the bot joined or left a server, with the name and ID of the server owner | Discord, when the bot joins or leaves | Keeping track of which servers the bot is on |
| Ban record | Your Discord ID, date, reason and who applied it | The team, when applying the sanction | Enforcing the ban |
| Cookies | Two essential panel cookies | Your browser | Keeping you signed in (section 4) |
What we do not process:
- Audio: the bots join a call only to play music. They do not record, listen to or process what people say.
- Messages: the bot reads only messages that start with its prefix or mention it, to run the command. The text of those messages is not saved: the library the bot is built on keeps the most recent messages (up to 1,000, including direct messages to the bot) in memory only, and they disappear when the bot restarts.
- Discord password and e-mail: we never receive them. The access Discord grants the panel at sign-in is used once and revoked right after.
Site access log. On every visit to the panel and the EmpireMuse pages, the EmpireCommunity server that receives the visits (the proxy) logs the IP address, the page requested and the time. This proxy also serves the other EmpireCommunity sites. The log starts a new file every day and keeps the last 80, about 81 days; after that, the oldest files are deleted. Cloudflare, which protects the site, also processes and logs IP addresses.
3. How we use data and on what legal basis
The law requires a "legal basis" for each use of data. Ours are:
| Purpose | Data | Legal basis |
|---|---|---|
| Providing the service you asked for: playing music, keeping preferences, favorites and settings, keeping you signed in to the panel | Identity, servers, preferences, settings, playback, cookies | Performance of the service (LGPD art. 7, V; GDPR art. 6(1)(b)) |
| Last.fm integration | Last.fm data | Your consent, given when you link the account (LGPD art. 7, I; GDPR art. 6(1)(a)). You can withdraw it at any time by unlinking |
| Protecting the service, investigating errors and understanding usage | Security logs, usage statistics, IP in the sign-in rate limiter, join and leave notices | Legitimate interest (LGPD art. 7, IX; GDPR art. 6(1)(f)) |
| Keeping access and security logs for a limited period (section 6), to protect the service | Access and security logs (IP, page, date and time) | Legitimate interest (LGPD art. 7, IX; GDPR art. 6(1)(f)) |
| Enforcing a ban | Ban record | Legitimate interest (LGPD art. 7, IX; GDPR art. 6(1)(f)) |
| Enforcing a server's Supporter mark | Supporter mark | Legitimate interest (LGPD art. 7, IX; GDPR art. 6(1)(f)) |
We do not use your data for advertising, we do not build behavior profiles and we make no automated decisions that affect your rights.
4. Cookies
The panel uses only two cookies, both essential:
- Session cookie: keeps you signed in. It is removed when you close the browser, sign out or the session expires (12 hours, or 60 minutes without activity).
- Sign-in cookie: protects the Discord sign-in. It lasts 10 minutes.
We use no analytics, advertising or third-party cookies. Because the cookies are essential, the panel shows no cookie consent banner.
5. Who data passes through
We do not sell, rent or disclose your data. It only passes through the services below, which EmpireMuse needs to work or which you turn on yourself:
- Discord: everything that happens in the bot and in panel sign-in goes through Discord, which handles that data under the Discord Privacy Policy. When you open the panel, your browser loads avatar and server icon images from Discord, so Discord sees your IP address.
- Music platforms (such as YouTube and SoundCloud) and music catalog services (such as Spotify and Deezer): receive search text, links and song titles and artists, to find and play the audio. They do not receive your ID or name.
- Google: receives the text you type in the search field of the play command, to suggest songs. It does not receive your ID.
- Last.fm: only if you link your account. It receives what you are listening to and your scrobbles (song, artist, album and time). See the Last.fm Privacy Policy.
- Infrastructure providers, which store or carry data on our behalf and may not use it for anything else: MongoDB Atlas (database), Hostinger (server) and Cloudflare (protection and delivery of the panel, which sees your IP).
- Donations: EmpireMuse does not receive or keep any payment data. How to donate and what happens to donations are on the EmpireCommunity Support page.
- Authorities: only when the law or a court order requires it.
6. Where and how long we keep data
Data is stored in Brazil: the database on MongoDB Atlas, on AWS servers in São Paulo, and the bot server at Hostinger, in Campinas.
| Data | How long |
|---|---|
| Your preferences, favorites, saved queue and 6-song history | While you use the service, or until you delete them |
| Last.fm data | Until you unlink or delete your data. When you unlink, we delete the access key and the username |
| Server settings | While the bot is on the server. They may remain stored after the bot leaves the server |
| Player queue and session | Until the player stops |
| Panel session | Up to 12 hours, or 60 minutes without activity. Kept only in memory and lost if the panel or the bot restarts |
| Usage statistics | 30 days, then deleted automatically |
| Bot and panel access and security logs | Up to 6 months, then deleted automatically |
| Site access log (proxy) | About 81 days: one file per day, up to 80 files. After that, the oldest are deleted |
| Server join and leave notices | 6 months (183 days). After that, the notice channel is cleared |
| Ban record: your Discord ID, date, reason and who applied it | While the ban is in effect. Deleted when the ban is lifted. We review the ban list once a year |
| IP in the panel sign-in rate limiter | 60 seconds, in memory only |
| Server Supporter mark | While the mark is in effect |
When you ask us to delete your data, we delete everything tied to you, except the access and security logs, the join and leave notices for servers you own and, if there is one, the ban record. The logs and notices stay only until the end of their period in the table above, to protect the service, and are then deleted.
The ban record stays because, without it, the ban would stop working. The basis is our legitimate interest in protecting the service and the people who use it (LGPD art. 7, IX; GDPR art. 6(1)(f)), and it stays only while the ban is in effect. Applying or lifting a ban also creates a line in the security logs, which follows the 6-month period.
Our hosting provider's backup copies may keep deleted data for up to 2 weeks. After that, the data is gone from those copies too.
7. Security
We protect data with encrypted connections (HTTPS), access limited to the responsible team and as little stored data as possible. The panel does not keep the access Discord grants at sign-in, and logs never store passwords, keys or message text. Automatic error alerts sent to the team carry only the error type and code.
No system is completely secure. If a security incident could create a significant risk or harm to you, we notify you and Brazil's data protection authority (ANPD) and, where the law requires, the competent data protection authority in the European Union.
8. Your rights and how to delete your data
You have the right to:
- know whether we process your data and access it;
- correct incomplete or wrong data;
- receive a copy of your data in a machine-readable format (portability);
- delete your data;
- withdraw your Last.fm consent at any time;
- object to a use based on legitimate interest;
- know who your data passes through (section 5);
- complain to the ANPD or, if you are in the European Union, to your country's data protection authority.
How to delete your data:
- In the bot: use the
/delete_my_datacommand. - In the panel: sign in and click the Apagar meus dados (Delete my data) button. If your sign-in is not recent, the panel asks you to sign in again to confirm it is you.
- By e-mail: write to legal@empirecommunity.org.
Deletion removes your preferences, favorites, your favorite radios (your account's and your own on each server), saved queue, history, Last.fm link (key and username) and scrobble queue, and takes your ID out of the records of who changed a server's radios. The server's favorite radio list stays, because it belongs to the server. What was already sent to Last.fm stays there. Deletion does not reach a server's settings: a server administrator can change or remove them in the panel and with commands, or ask for full deletion by e-mail. To stop using a bot on a server, an administrator can remove it from the server in Discord.
If you are banned: you can still delete your data with the bot command or by e-mail; the panel stays closed. Deleting your data does not lift the ban, and the ban record stays while the ban is in effect (section 6). To dispute the ban, write to the e-mail above (Terms of Service, section 10). At that e-mail you can also ask for the date and reason kept in your record; we reply within 15 days, without saying who applied the ban. The bot's automatic notice does not include the reason.
For the other rights, write to the e-mail above. We may ask you to confirm that you own the account, for example by sending a message from that Discord account. We reply within 15 days.
9. Children and teenagers
EmpireMuse is for people 13 or older. If the law of your country sets a higher age, your country's age applies. We do not knowingly collect data from children under 13. If we learn that we hold data from someone below that age, we delete it. A parent or guardian can ask for this through the contact e-mail.
For teenagers, we process only what the service needs to work, never for advertising or profiles. If the law of your country requires a parent or guardian's permission to link Last.fm, ask them before linking.
10. International transfers
We store data in Brazil. Some services EmpireMuse uses are in other countries, and data passes through them:
- Discord (United States): every use of the bot already goes through Discord, under its policy.
- Last.fm (United Kingdom and United States): only if you link your account.
- Cloudflare: a global network that delivers the panel and sees your IP.
- Music and catalog platforms: receive searches, links, titles and artists, without your ID.
These transfers happen because they are needed to provide the service you asked for or the integration you turned on (LGPD art. 33, IX; for people in the European Union, GDPR art. 49(1)(b)).
11. Changes to this Policy
- This Policy takes effect on the publication date shown at the top of the page.
- For material changes, we give 15 days' notice in the EmpireCommunity support server on Discord and in the panel.
- Minor fixes (typos, clearer wording, links) take effect immediately and are recorded in the version history at the end of this page.
12. Contact
Requests about your data, questions and security reports: legal@empirecommunity.org. We reply within 15 days.
Version history
| Date | Change |
|---|---|
| November 17, 2026 | First published version. |
Back to top