Skip to content
Public Notice

Privacy Policy

Last updated: 25 October 2026

Authentication with Discord

You sign in with Discord OAuth2. You do not create a separate account, and the dashboard never sees your Discord password.

The dashboard asks Discord for the identify scope only. From it, Discord gives us your user ID, username, display name and avatar. We do not receive your email address or your list of servers from Discord when you sign in. The access token is used once to read that profile and is not kept.

Discord login No Discord password

What we collect and store

The dashboard and the bot keep only what they need to work:

  • Command access records: your Discord user ID, whether bot command access is active, and when it was granted, last used to sign in, or revoked.
  • Restrictions: blacklist entries and cooldowns, with the Discord ID they apply to, who applied them, the reason the bot owner entered, and the times involved.
  • Audit records: a log of owner and access actions with the Discord IDs of the actor and the target, the action, and a timestamp.
  • Invite requests: the requesting Discord ID, the server and channel IDs, the status and the times.
  • Prefixless settings: the server slots, aliases, members and embeds that a server owner configures, plus the notices the bot sent about them. Notice history is kept without the embed text.
  • Music settings: per-server options such as volume, DJ role, text channel and a 24/7 voice channel. The music cog does not store what you listen to.
  • Recent command activity: the bot owner can see a live feed of recent commands. Arguments are masked before they are stored, and the feed stays in memory only. It is not written to disk and is cleared when the bot restarts.
  • Webhook URLs: a webhook you paste into Embed Studio is used once to deliver that message to Discord. It is not stored and not logged on the server.
  • Operational logs: sign-in events, errors and delivery outcomes, which include Discord IDs. Embed delivery logs record the account and the result, never the webhook URL or the message.

How we use it

  • To sign you in and show the dashboard features your Discord account is allowed to use.
  • To decide whether bot commands run for your account, and to apply cooldowns and blacklists set by the bot owner.
  • To keep an audit trail of owner actions, so changes can be explained and reviewed.
  • To deliver the messages and embeds you ask us to send.
  • To protect the service. Rate limits are kept in memory and are tied to your account, the webhook ID and your IP address for a short time only.

We do not sell your information, use it for advertising, or build tracking profiles.

Cookies and browser storage

The dashboard sets a signed session cookie for your sign-in. It also holds your language choice and the CSRF token that protects forms. It is not kept after you close your browser or sign out.

If you change the theme, the dashboard remembers it in preference cookies for one year. Some pages also keep small settings in your browser, such as motion preference, Embed Studio drafts and templates, the server you last picked on the games, card preview and profile pages, and the owner's live-feed filters.

There are no analytics, advertising or tracking cookies. The Cookies page lists each item. Read the Cookies page

Third parties

Discord handles sign-in and delivers the bot's messages and any webhook message you send. Discord's own terms and privacy policy apply to that data. Avatars are loaded from the Discord CDN.

Your browser also loads fonts, icons and scripts straight from Google Fonts, Bootstrap CDN, cdnjs, jsDelivr, unpkg and pagination.js.org. Those services can see your IP address and browser details when they serve the files, under their own policies. We load nothing else from third parties and run no analytics or ad services.

The dashboard is built from open-source components, each under its own license. The Credits page lists them.

Data retention

Access, restriction, audit and invite records have no automatic expiry. They are kept until the bot owner removes them. Prefixless notice history is capped, keeping the most recent 50 broadcasts and 200 notices. Settings stay until the server owner or the bot owner changes them.

Sessions end when you close your browser or sign out. Anything saved in your browser stays there until you clear it.

Public pages, leaderboards, awards and web games

Nothing about you is shown on a public page unless you choose it. Every choice is its own tick box on the My settings page (or the angelweb command in Discord), every box starts unticked, no box is ticked for you because you use a feature or are in a server, and unticking takes effect as soon as you save it (or at once with the angelweb command).

  • Leaderboards: if you tick a board, your name and avatar appear with your rank and score on that public board. A box for all servers combined never reveals which servers you are in. A box for one server shows your server nickname on that server's board only, and anyone who opens it can see that you are in that server. The numbers are read live from the bot and are not copied anywhere.
  • Server pages: a server page exists only after a server admin switches it on. It shows only items (starred messages, closed polls, welcome tiles) whose authors ticked the matching box for that server. Private and age-restricted channels are never shown, links and mentions are removed, and an author or a server admin can take an item down at any time. A picture in a starred message keeps its Discord link, and that link contains the number of the public channel it was posted in (avatars and server icons are never linked, because their links contain member and server numbers).
  • Awards: your achievements are private to you. Two optional boxes let other people see your showcase badges on profile cards (they appear on your profile card in Discord, which other members can see), or count your achievements, without your name, in the percentages on the public achievements page (shown only when enough people take part).
  • Web games: results you play on the website count in the same Angel stats as in Discord and are never shown publicly unless you tick a box. Game state is kept only as long as the game needs it.
  • What is stored: for each box you tick, your Discord user ID, the name of the box, the server ID where it applies and the time. Untick a box and that row is deleted. Your server boxes are deleted when you leave or are banned from the server or the bot leaves it. Nothing is stored for people who never ticked a box.
  • Server admins can hide their server from the website with one switch: it then behaves as if it did not exist there and members' choices for it stop applying until the switch is lifted. Server admins and the bot owner see only how many members ticked a box (a number below 5 is shown as fewer than 5), never who.
  • Your rights: untick everything in one click, download your data, or delete it, all from My settings, or with angelweb off, angelweb mydata and angelweb forget in Discord. Red's data request commands work too. We never sell or share this data, and it is never used for anything except showing what you chose.

Open My settings · Questions or a takedown request? Ask in the support server: https://discord.gg/8Kt9uAMBqe

Your choices

  • Sign out of the dashboard at any time. This ends your session and revokes bot command access for your Discord account. It does not remove a blacklist.
  • Remove the app under Authorized Apps in your Discord settings to withdraw its authorization.
  • Clear your browser's site data to remove cookies and the settings saved in your browser.
  • Ask in the support server to have the records tied to your Discord ID reviewed or deleted. Records needed to enforce a restriction or to explain an owner action may be kept.

Contact

The Discord support server is the only way to reach the bot owner, for privacy questions or anything else: https://discord.gg/8Kt9uAMBqe