Rook Dashboard Add to Discord

Privacy

Discord is a chat app where people meet in servers, which are communities with their own chat channels. Each server is run by its owner and the moderators they choose. Rook is a bot, an automated account that a server can add. When you join a server that uses Rook, you're asked to verify, which means opening a page from Rook so it can check whether your account is a second account (an alt) of someone already there, or of someone the server has banned.

Rook is made and run by Sirius, a small business in the UK (sirius.menu). Sirius is the controller of the data described here, which means it decides how the data is used and is responsible for it. Contact Sirius at privacy@rook.bot.

What Rook keeps

When you verify in a Discord server that uses Rook, Rook records, for that server:

  • your Discord user ID and the server's ID;
  • a keyed one-way fingerprint of your IP address and of its network;
  • a keyed one-way fingerprint of a random ID stored in a cookie on this site;
  • a keyed one-way fingerprint of some of your device's settings (see below);
  • your network type (home, VPN and so on), your score, the reasons for it, and the IDs of members of that server whose fingerprints match yours.

Rook never stores your IP address, your email address, your messages, your browser's user agent or the device settings it reads. The data comes from your visit to this site, from Discord, and from other members' verifications in the same server.

If you're banned

When a server bans you, which removes you and stops you rejoining, Rook also keeps a simplified form of your username and display name, your avatar's ID and a small fingerprint of the picture, until you are unbanned. If a new account in that server looks like yours, its moderators are told. Your names and picture are public on Discord; the picture itself isn't kept.

The owner of several servers can link them to share bans. Then, if the same Discord account is banned in one, moderators of the others see that it's banned there, when, and the ban's reason, which Rook reads from Discord at the time and doesn't keep. Only servers with the same owner are linked, and their verify pages name them.

Ban Beacon

Servers can turn on Ban Beacon, which warns them when someone banned in other servers that use it joins. Their verify page says so before the check.

In those servers, Rook keeps a locked fingerprint of your connection and browser with your verification record. Only Rook's bot can unlock it, and it does so only if that server bans you. The fingerprint then goes on a list the other Ban Beacon servers check when someone verifies. Until then it can't be compared with anything, so it doesn't link you to any other server.

Moderators see how many servers banned an account linked to a newcomer. They don't see which servers, why or when. A server can choose to keep those accounts out.

A listing ends when the ban is lifted, when the server leaves Ban Beacon or removes Rook, or after 1 year. Sirius can take a server's listings down, and will look at any listing you ask about.

Scam protection

Servers can turn on scam protection, which removes the image scams posted from hacked accounts. In those servers, when a message has several images, Rook keeps a fingerprint of the images with the message, channel and author IDs for 48 hours, to spot the same scam posted again. It keeps no images and no message text.

Raids

In servers with raid alerts on, Rook reads messages from people who joined in the last 15 minutes, or during a raid, to spot coordinated spam: the same message from many of them, or one message mentioning a crowd. It keeps a scrambled fingerprint of each message in memory for a few minutes and never stores the text. While a raid is being judged, it also keeps newcomers' account age, name, picture ID and Discord's spammer flag in memory for up to 3 hours, and stores none of them. Apart from this and Rook Assistant, Rook ignores messages.

Support tickets

In Rook's support server, opening a ticket makes a private channel with the Rook team. Rook keeps who opened it, who handled it and when, for 1 year after it closes. When it closes, Rook reads the channel, sends the transcript to the team's private log channel and to you by DM, and deletes the channel. Rook doesn't store what was said.

Why Rook uses it

Servers use Rook to keep out people they have banned and accounts made for raids. The lawful basis is legitimate interests: keeping these communities safe. Sirius has weighed this against your privacy, and you can ask for that assessment. If you don't verify, you won't get the server's verified role.

The verify page sets one cookie, __Host-rook_d. It holds a random ID and lasts 400 days from your latest visit. It lets Rook notice when several accounts verify from the same browser, and it is used for nothing else.

Signing in to the dashboard sets __Host-rook_s, which keeps you signed in for up to 7 days, and __Host-rook_oauth, which lasts 10 minutes while you sign in. Each dashboard session notes its browser and system, such as "Chrome on macOS", so you can tell your sessions apart; it ends with the session.

These cookies are needed for the service you asked for, so Rook doesn't ask for consent.

When you reach rook.bot from another site or a tagged link, the site sets rook_src, which holds that site's name or the tag and the day, such as topgg.20261014. If you add Rook later, the install counts for that source. It holds no ID and lasts 30 days. Rook only uses it to count which sites bring servers. Delete it or block cookies for rook.bot and nothing is counted.

The device check

The verify page also reads some of your device's and browser's settings, such as your screen and time zone. Rook turns them into one keyed fingerprint for that server and keeps nothing else. It helps Rook notice when the same device verifies another account in the same server.

Different people's devices can look alike, so this fingerprint is weighed with care.

Reading these settings is needed to keep the server secure and to prevent ban evasion, so it needs no consent under UK law. It is kept as long as the verification record.

Automatic decisions

By default, an account that matches other members is let in and the server's moderators are told. Rook keeps an account out without a person checking first when it matches someone banned from that server, or breaks a rule the server set, such as a VPN block, a minimum account age, keeping matched accounts out, or keeping out accounts banned in a linked server with the same owner, or keeping out accounts that match Ban Beacon bans.

Servers with Raid Autopilot let Rook handle a raid without a person. While a raid is on, Rook holds new accounts that look made together with other raid accounts, which keeps them out of the server until it ends. It bans accounts that post the same spam as other new members or mention a crowd, and deletes their messages from the last hour. An hour after the raid ends, Rook removes the accounts it still holds, without banning them, so a real person can join again and verify. Accounts that boost the server are let in. Moderators see each of these decisions and its reasons in their log, and can let a held account in or undo a ban.

To have a person review a decision, ask the server's moderators or contact Sirius, and say why you think it's wrong.

Who sees it

Moderators of the server you verified in see your result and any matched accounts there. Fingerprints are compared within one server. If its owner links it with other servers they own, Rook also compares you with members of those while you verify, using fingerprints worked out for each server at that moment and never stored that way. Moderators are told which linked server a match is in, and who it is only if that account is banned there. They also see whether your account is banned in a linked server. Railway hosts Rook in the EU. Cloudflare runs the network in front of this site and the human check, may process your IP address in the US under the UK Extension to the EU-US Data Privacy Framework, and uses check data to improve its bot detection. Discord delivers Rook's messages, and serves the server icons and avatars your browser loads. Sirius staff see counts for each server, such as verifications per day, to run Rook and stop abuse. Those counts don't say who verified, and staff access is logged. Fastmail handles email sent to Rook's contact address and stores it in the US.

The people who run a server can use Rook Assistant, a chat helper in Rook's dashboard (the website where they set Rook up) and in Discord, where staff ask it by mentioning Rook. What they type, and their server's structure (its name, roles, channels, permissions and Rook's settings), go to the AI provider that answers them, in the US. In Discord, when staff ask about something said in a channel they can see, its recent messages go too, with each member shown as a code such as M2 in place of their name. The provider also learns whether a member in the conversation is in the server, verified, timed out or a moderator, when staff ask about a member, when they joined, how old their account is and their roles, and the names of members staff look up by name. Verification records are never sent: staff see them on their own screen. Rook doesn't keep the messages it read. In Discord, it keeps what staff asked and its answer for 14 days, so Sirius can check the answers are right, with members shown as codes and no record of who asked or in which server. A name a moderator typed stays as they typed it. The provider may keep the chat for a short time to check for abuse, and doesn't use it for training.

How long Rook keeps it

  • Verification records: while you're a member of that server or banned from it, then 90 days.
  • Moderators' decisions about you: 1 year.
  • Bans, with the simplified name, avatar ID and a fingerprint of the picture: until you are unbanned.
  • Raid Autopilot's holds, with their reasons: 7 days.
  • What staff asked Rook Assistant in Discord, and its answers: 14 days.
  • Ban Beacon listings: until the ban is lifted, the server leaves Ban Beacon or removes Rook, or 1 year.
  • Dashboard actions moderators ask for: 30 days.
  • Records of privacy requests, including emails: 2 years.
  • Scam protection fingerprints: 48 hours.
  • Support tickets: 1 year after they close.
  • When you use the dashboard: Rook notes when you first and last opened it, on how many days, and the server you last opened, so Sirius can see whether people come back. Kept 13 months after your last visit.
  • Dashboard sign-ins: 7 days. Signing in keeps your Discord ID, name, picture and an encrypted Discord token Rook uses to list the servers you manage. Delete them any time from the dashboard's Account page.

Your records are what link a new account to you, so they last as long as your membership or ban. When a server removes Rook, its data is kept for 30 days in case that was a mistake, then deleted.

Your rights

You can ask for a copy of your data, and ask Sirius to correct, delete or restrict it, or object to its use. Run /rook privacy in any server with Rook to download your records or delete them. Records from servers you're still in, or banned from, are kept until that ends, because deleting them would let anyone hide a second account; they're deleted within 2 hours after. For anything else, email privacy@rook.bot. If you're unhappy with how Sirius handles your data, complain to Sirius first. You can also complain to the Information Commission at ico.org.uk.