Privacy Policy

This document describes what data NyrxBot processes, for what purpose and for how long. We have tried to write it in plain language, without needless jargon.

1. What we collect

Server configuration. The server ID, the chosen language, the command prefix, the log channel ID, automod settings, and the lists of banned words and allowed domains. Plus any radio stations you add.

Moderation history. For every moderation action we store the case number, the type of penalty, the ID and name of the punished user, the ID and name of the moderator, the reason, the duration and the date.

Play history. For every track we store the title, artist, address and artwork, plus the server ID and the time it played. We do not store who started it. This feeds the "recently played" and "popular today" lists in the dashboard. Radio streams are not recorded.

Dashboard session data. After you sign in through Discord we receive your ID, name, avatar and server list. We keep them only in a signed session cookie; they are not written to the database.

Support tickets. For each ticket we record its number, category, the id and name of the person who opened it, the id of whoever handled it, the status and the times it was opened and closed. We do not keep the conversation itself. If the server owner picks a transcript channel, the record of the conversation is posted there as a file — that is, on Discord, under their control — and we store only a link to it. With no channel picked, no transcript is made at all.

Persistent roles. If the server owner turns this on, we record the server id, the person's id, their list of roles and their server nickname when they leave — so we can give them back when they return. The record is written only at the moment they leave, disappears as soon as the roles are restored, and deletes itself after 90 days if they never come back. With the feature off we store nothing.

Server history. When the bot joins a server, we record the server's ID and name, its member count, the date it was added and — if the bot has permission to read the server's audit log — the ID and name of the person who added it. When the bot is removed, we add the removal date, which modules were turned on, and how many commands were used and tracks played. The person who added the bot is deleted at that same moment. This is only for us — to understand why servers stop using the bot.

Top.gg votes. If you vote for the bot on top.gg, the site passes us your Discord ID. We store it together with your vote count and the date of your last vote — to grant the XP bonus and show it in the /vote command. We receive nothing else from top.gg.

Temporary counters. For anti-spam and warning thresholds we keep counters tied to a user ID in a cache. They expire automatically, within minutes at most.

Answering questions. If the server owner turns this on, the bot reads messages to recognise questions about itself and answer them with content from the documentation. It is off by default. Messages are checked in memory and are neither stored nor sent outside the server the bot runs on.

Bot log in the panel. We record what the bot did on your server: the command used together with the options given, the ID and name of the person who ran it, the channel, ticket events, punishments issued by automod and settings changes made from the panel. None of your conversations are in it. This is on by default and can be turned off in the panel.

Server log in the panel. OFF by default. If the server owner turns it on, we store the content of deleted and edited messages (up to 500 characters), attachment names, the author's ID and name, the channel, and joins and leaves. Turning this on is a deliberate decision by the server owner, who is responsible for telling their members about it. With it off we store nothing — the content of a deleted message then goes only to your log channel, that is, to Discord.

Both logs share one retention period, set in the panel: from 1 to 90 days, 30 by default. After that entries delete themselves, whether or not anyone remembers.

Levels. If the server owner turns this on, we record, per message, the server ID, the member's ID and name, the total points earned, the level, how many messages earned points and when points were last awarded. With voice XP enabled we also count the minutes spent in voice channels and the points they earned — a counter only, with no record of which channel or with whom. We store neither message content nor audio — both only serve to add the points. With the feature off, which is the default, nothing is recorded.

Starboard. We store IDs: the server, the highlighted message, its channel and the board entry, plus the reaction count. We do not keep the highlighted message's content — the board entry is rebuilt each time from the live message on Discord. When the original is deleted, we drop the link too.

Public leaderboard. If the server owner turns it on, members' names and levels become visible on our website with no login. It is off by default. Turning it off hides the page immediately; the data itself stays in the database on the same terms as everything else.

Greetings and 24/7 mode. No personal data here: the server configuration holds channel IDs, the greeting text written by the owner and the address of the last radio station played.

2. What we do not collect

• we do not archive message content — the one exception is the server log described above, off by default and turned on deliberately by the server owner; apart from it, the content of a deleted or edited message goes only to your log channel, on your own Discord server
• we do not store email addresses or passwords
• we do not store IP addresses in the bot's database, build device fingerprints, or use them to detect alternate accounts
• we run no advertising trackers and no third-party analytics
• we do not sell or share data with third parties

3. Why we need it

Solely so the bot works: so it remembers your server settings, can show the moderation history and can enforce automod thresholds. The basis for processing is performing the service you asked for by adding the bot.

4. How long we keep it

Configuration and moderation history are kept for as long as the bot remains on your server.

When the bot is removed from a server, that server's data is deleted automatically — configuration, automod settings, radio stations, play history, the entire moderation history, both logs, level points and starboard entries.

The only thing that remains is the server history entry described above: the server's ID and name, member count, dates, enabled modules and usage counts — with no data about any person.

Top.gg votes are not tied to any server, so they do not disappear with the bot. If you want them deleted, contact us through the support server.

Entries in both logs delete themselves after the period set in the panel (1 to 90 days, 30 by default), and disappear immediately when the bot is removed from the server.

Anti-spam counters expire on their own and are not archived anywhere.

5. Who has access

The moderation history and configuration are visible to people with the Manage Server permission, through the bot's commands or the web dashboard. Beyond that, access is limited to the service administrator, to the extent needed to keep it running.

6. Where it is stored

The data sits on a server in the European Union. The database is not exposed externally; it can only be reached from inside the service infrastructure. The connection to the dashboard is encrypted.

7. Your rights

Under the GDPR you have the right to access your data, to have it corrected or erased, to restrict processing and to object. You also have the right to lodge a complaint with the President of the Personal Data Protection Office in Poland.

To delete the data, remove the bot from the server. If you want to remove only your own entries from a particular server's moderation history, write to us through the support server. We handle requests within 30 days.

8. Third-party services

The bot talks to the Discord API and to music services when you ask it to play a track. Those services have their own privacy policies.

9. Changes

We may update this policy. The date of the most recent change is shown at the top of this page. We will announce significant changes on the support server.

10. Contact

For matters concerning personal data, contact us through the support server linked in the footer.