Privacy Policy — BetterYAG

Last updated: 12 September 2026

This policy explains what data the BetterYAG Discord bot (“the bot”) and its control panel at gpbot.groundpower.dev collect, why, how long it is kept, and how you can have it removed.

Who operates the bot

What we collect and why

Server settings

Server, channel and role IDs, and the settings administrators choose in the control panel: auto-moderation rules, custom commands, role menus, welcome messages, log channels, feeds, streaming role settings, soundboard sounds and similar.

Why: the bot needs them to work the way each server set it up.
Kept: while the bot is in the server. Settings are not deleted automatically when the bot is removed, so they come back if it is added again. A server owner can ask us to delete them at any time.

Control panel

When you log in to the control panel with Discord, we receive your Discord user ID, username, avatar and the list of servers you are in, so we can show the servers you can manage. When an administrator changes a setting, the change is logged with their user ID and username so the server's staff can see who changed what.

Kept: the login session until you log out or it expires; the change log until the server owner asks us to delete it.

Member data

Discord sends the bot information about the members of servers it is in: user IDs, usernames, nicknames, roles and join dates. Most of it is only held in memory while the bot runs. It is used for auto-roles, welcome and farewell messages, re-applying an active mute to someone who leaves and rejoins, role menus, and permission checks before moderation commands.

What is stored:

• Username and nickname history, on servers that keep these logs on. Kept until you clear it yourself by mentioning the bot with resetpastnames (for example @BetterYAG resetpastnames) or ask us to delete it.
• Moderation records (warnings, mutes and bans, with the moderator's ID and the reason). Kept until a server administrator removes them or you ask us to delete them.
• Data you create yourself with features such as reminders, reputation points or timezone settings. Kept until you or a server administrator remove it.
• Custom command data. Server administrators can write custom commands that save values tied to a user ID, such as points or counters. This data is part of that server's setup and is kept until the server's commands or administrators delete it, or you ask us to. Custom commands can also fetch information from external websites; the server's administrators decide what those requests contain.

Other features store only what they need to work, for example open support tickets or verification status, and the deletion options below cover them too.

Message content

The bot reads the text of messages in channels it can see in order to:

• run auto-moderation (spam and flood detection, invite links, banned words, mass mentions and other rules the server sets up),
• match the custom command triggers that server administrators define.

The bot's built-in commands are run through Discord's slash commands or by mentioning the bot, so they do not depend on message content.

Messages are processed in memory and not stored, with three exceptions:

• Message logs that a moderator creates with the logs command, a snapshot of recent messages in one channel. Kept until a server administrator deletes them in the control panel or you ask us to.
• The auto-moderation log, which keeps the message that triggered a rule. Only the latest 200 entries per server are kept.
• The command log, which keeps the text of commands run through the bot. Kept until you ask us to delete it.

Direct messages to the bot are handled the same way: they are used to run the command you sent and are not stored, except in the command log. The bot does not see messages in servers it is not in.

Presence data (online status and activity)

Discord sends the bot members' online status and current activity, for example the game someone is playing. The bot uses it in memory for:

• the streaming role and stream announcements, on servers that switch them on,
• the topgames command, which shows what is being played in the server right now,
• the status line of the whois command.

Presence updates also tell the bot when a username changes, which goes into the username history above. Apart from a short-lived list of who is streaming right now, used to add and remove the streaming role, presence data is not stored, and we do not build profiles of what people play.

Opt-out: run the presence command with optout (for example /presence action:optout) and the bot stops using your presence in every server. optin turns it back on and status shows your current setting.

Server statistics

Message counts per channel and member join and leave counts, shown on each server's stats page. They do not identify individual users. Kept until the server owner asks us to delete them.

What we do not do

• We do not sell your data or share it with anyone for advertising or any other purpose.
• We do not send your data to AI services or use it to train machine learning models.
• We do not collect more than the features above need.

Where the data is kept

The bot, its database and its cache run on a server rented from Hetzner Online GmbH in Nuremberg, Germany. The database and cache are not reachable from the internet; only the bot and the operator can access them. Bot credentials are kept in environment variables on that server, not in source code.

Your rights

• Opt out of presence processing: the presence command with optout.
• Clear your username and nickname history: mention the bot with resetpastnames.
• See or delete anything else we hold about you: email ykimp@protonmail.com with your Discord user ID. We answer within 30 days.
• Server owners can ask us by email to delete everything stored for their server.

Children

The bot is not directed at children under 13, or under the minimum age for digital consent in your country, in line with Discord's Terms of Service.

Changes

If this policy changes in a meaningful way, the date at the top of this page will be updated.