Privacy policy

01The short version

The rest of this page is the detail behind that sentence.

02What we store

Configuration you set

Whatever you configure through commands or the dashboard: welcome messages, autoroles, antinuke settings, voice channel setups, vanity rewards, per-command permissions and so on. These are stored against your server's Discord ID.

Discord identifiers

Server IDs, channel IDs, role IDs and user IDs. These are how Discord features work at all. A role reward is meaningless without a role ID.

Feature data

Data a specific feature needs in order to function: jail records, economy balances, giveaway entries, AFK notes, activity counts used by the dashboard, and moderation case history. Turning a feature off stops it collecting.

Message content

Message content is processed in the moment, to run a command or a feature you enabled, and is not kept as an archive. Two narrow exceptions, both of which you control:

• Snipe keeps recently deleted or edited messages briefly so the command can show them.
• Logging, if you enable it, writes events into a channel in your own server.

Dashboard sign-in

Signing in uses Discord OAuth. We receive your user ID, username, avatar and the list of servers you can manage. Your session is a signed cookie. We never see your Discord password, and we don't ask for permission to read your DMs.

03What we don't store

• Your Discord password. Sign-in happens on Discord's side.
• Payment card details. Purchases run through Discord tickets and third-party processors.
• An archive of your server's conversations.
• Direct messages, unless you deliberately send one to the bot.

04Why we store it

• To run the features you turned on. That's almost all of it.
• To show your dashboard statistics. Counts of messages, reactions and voice time per channel and per member.
• To keep the service working. Diagnosing errors, preventing abuse, enforcing whitelists.

We don't build advertising profiles and we don't run analytics on your members for anyone else's benefit.

05Who else sees it

We don't sell your data, and we don't share it with advertisers. It's handled by:

• Discord, unavoidably, since the bot lives there.
• Our hosting and infrastructure providers, who store the data on our behalf.

We'll disclose data if the law genuinely requires it.

06How long we keep it

• Server settings stay while the bot is in your server.
• Activity statistics are kept as daily totals so the dashboard can show trends over time.
• Snipe data is short-lived and rotates out on its own.
• Dashboard sessions expire, and signing out ends them immediately.

Remove the bot from a server and that server's configuration stops being used. Ask us and we'll delete it outright.

07Your choices

You can ask us to:

• Tell you what we hold about you or your server.
• Delete your server's data, or your personal data.
• Correct something that's wrong.

Open a ticket in the Discord server or email support@bleeding.rest. Server-level requests need to come from someone who can manage that server, otherwise anyone could wipe your setup.

Depending on where you live, you may also have rights under laws such as the GDPR or the CCPA. We'll honour those requests regardless of where you're based.

08Keeping it safe

Dashboard access is restricted to people with Manage Server on the server in question. The token the website uses to talk to the bot stays server-side and never reaches your browser. Access to the underlying databases is limited to the people who run bleeding.

No system is perfect. If you find a security problem, please report it privately in Discord rather than publicly. We'd rather fix it before it's news.

09Younger users

bleeding isn't for anyone below Discord's minimum age for their country. If we learn that data belongs to someone under that age, we delete it.

10Changes to this policy

When what we collect changes, this page changes with it, and the date at the top updates. Significant changes are announced in the Discord server.