Privacy PolicyDraft

You sign in with Discord, which is needed to use the dashboard. We request only the "identify" and "guilds" scopes, so we do not receive your email address and have no password for you.

• Your Discord profile (user ID, username, display name, avatar, banner, accent colour and language), and the servers you are in with your permissions there, cached for a few minutes.
• The access and refresh tokens Discord issues at sign-in, stored encrypted. Signing out asks Discord to revoke them; the encrypted copy stays until your account is deleted.
• Sessions: the IP address, browser (user agent) and times of each session and of your last sign-in. You can see and end your sessions on your account page.
• If you turn on two-factor authentication: the authenticator secret, stored encrypted, and your recovery codes, stored only as hashes.
• Records of the changes you make in the dashboard (old and new values), and security records of sign-ins, refused requests and administrative actions: the IP address the request came from, the browser, the page and a request identifier. No IP address is recorded for events not sent by your browser, such as Discord events or scheduled jobs.
• What you write in support tickets. A short notice of each new ticket (its subject, category, your Discord name and ID, and the start of your message) goes to a private Discord channel that only our staff can see.

A server’s administrators can give a member Administrator or Manager access to its dashboard before the member signs in. Until then we store the member’s Discord user ID, username, display name and avatar and who granted the access, and remove them when the member signs in, the access is removed or the member leaves. Managers named in the bot’s owner panel are stored as a user or role ID with who added them.

In each server that adds it, the bot receives the member list and message content from Discord, but not members’ online status, and uses them only for the features that server turns on.

• Messages (content, attachments, author and channel), checked as they arrive for automatic moderation and anti-spam.
• A temporary copy of each message (its text and the names and sizes of its files, not the files themselves), kept for up to 48 hours so that an edit or deletion can be logged. No copy is kept for a server that has turned on message-content redaction.
• When a deleted message is logged, the log’s details (which can include its text) are kept only until the log is posted; the remaining record (IDs, file sizes and results) is deleted 7 days later.
• Log entries the server chooses to record, such as edited and deleted messages, joins and leaves, role, nickname and voice changes, moderation actions and server changes, with the user IDs, names and avatars of the people involved; they are also posted to the server’s own log channels. Only authorised 27Guard staff can export a server’s logs as a file; each export is recorded.
• Message-content redaction: when a server turns it on, message content is removed from the log entries we store and from log search, and the bot’s new log posts leave it out. It cannot remove copies already posted to Discord, or database backups made before then, which keep that content until each backup is deleted. Turning redaction off later does not bring the content back, and ticket transcripts are not affected.
• Member records: join dates, the invite used, message counts, levels and experience points, time in voice channels, warnings, daily activity totals, Protection Bypass exemptions, and members’ part in giveaways, polls, suggestions and verification (verification answers are stored only as hashes).
• The roles each member was last seen with (role IDs only), for leave, kick, ban and timeout logs; deleted 30 days after the bot last saw the member, or 10 minutes after they leave.
• Moderation cases, appeals and the server’s own tickets. A ticket’s messages are stored as a transcript only when the server’s ticket settings turn transcripts on, and are kept until the ticket data is deleted with the server’s data.
• Backups of the server’s structure (channels, roles, permissions and settings) when the server uses backups.
• Anti-Scam, if the server turns it on: images are checked on our own servers and are never sent to a third party. We compute fingerprints (hashes) and, where configured, read the text in the image. For a known scam we keep a detection record for 30 days (the fingerprints, a small preview image of at most 160 pixels, at most 500 characters of the text, any domains it named, and what was done); an alert can quote up to 400 characters of that text, with links disabled. With message-content redaction on, that text and those domains and links are left out.
• When our staff confirm an image as a known scam campaign, only its fingerprints are used to recognise copies in other servers; the preview and text stay with the server that reported it.
• Direct messages sent to the bot are not answered; they are forwarded, with the sender’s name, avatar, user ID and any attachment links, to a private channel that only our staff can see, for support and abuse reports.

The Media Archive keeps private copies of the images and videos members post, so that a deletion log can still show them after Discord removes the original. It does not keep message text, and files posted by bots are not copied. It is off unless we switch it on; once on, it works automatically in every server that has not turned on message-content redaction, within the limits of the server’s plan. With each copy it keeps the message, channel and author IDs, the author’s name, and the file’s name, size, type and checksum.

• Storage: the copies are stored in Cloudflare R2, a private storage service in which Cloudflare encrypts stored files. They are never public and are not kept on our servers’ disks.
• Access: only signed-in people who can read that server’s logs, through our website, with a single-use link that works for 5 minutes; every link and download is recorded in an audit log. Our staff cannot open the copies; our platform owner can only during an audited, time-limited support session for that server, after a fresh two-factor check.
• Deletion: a deletion log posts the message’s details, then its files; a file not posted is listed as “(not attached)”. Each private copy is deleted once Discord confirms that very file was posted, and also when its channel or thread is deleted, the bot is removed, the server’s owner deletes it, we reset the server’s archive, the server turns on message-content redaction (at once), or a member’s archived media is deleted on request. A copy that is not posted (for example, too large for the log channel’s server, no log channel, or a message removed by automatic moderation) is kept until then, never deleted for its age. Failed deletions are retried until they succeed.
• Deleting our private copy does not remove a copy already posted in a Discord channel; that copy is managed in Discord.
• Message text archived by earlier versions is no longer added or shown to anyone. It is deleted at most 365 days after each message was posted, or earlier if we delete it all, if the server turns on message-content redaction, or with the server’s data after the bot is removed.

We do not rely on consent. Automatic moderation, anti-spam and Anti-Scam act on messages automatically, under each server’s own settings (for example by deleting a message or timing out its author); server staff can review these actions, and Anti-Scam detections can be marked as false positives so that the action is corrected.

We do not sell personal data, show advertising, or use analytics or tracking services. Data received from Discord is used only to provide the features described here and to keep the service secure; it is not shared with data brokers or advertising services, and message content is not used to train machine-learning or AI models.

• To run the features a server has turned on, your website account and support requests, and to keep a record of each server’s plan: needed to provide the service that was asked for, and in the server’s legitimate interest in moderating and protecting its community.
• To keep the service secure (sign-in protection, rate limits, abuse prevention and investigating incidents): our legitimate interest in a safe service.
• To meet legal obligations, such as lawful requests from authorities.

Some of this data is stored or processed outside Saudi Arabia: Cloudflare R2 has no storage location there, and Discord and Cloudflare operate internationally.

• A server’s administrators, and people they give access, can see that server’s logs, moderation records, Anti-Scam detections and member records, including entries about you. They see archived media only from the deletion logs.
• Our staff, for support, security and abuse handling. Security alerts (who acted, what was done or refused, settings changes with old and new values, and any recorded IP address), support notices and forwarded direct messages reach them in private Discord channels. Staff allowed to view security records can export them; each export is recorded.
• Service providers: Discord, which provides the platform; Cloudflare, which carries traffic to the website (and therefore sees IP addresses) and stores the Media Archive’s copies in Cloudflare R2; and the provider that hosts our servers, which stores the data on our behalf.
• Authorities, when the law requires it.

• Server logs: the period of the server’s plan, 180 days on the Free plan and 180 days on Premium (also when we give a server Premium limits at no cost). Older entries are deleted daily. Server backups are kept for the same period as that server’s logs.
• Temporary message copies: up to 48 hours. Anti-Scam detection records: 30 days. Deletion-log records, last-seen roles, Media Archive copies and older archived text: as described above.
• Sessions: deleted 7 days after they expire or are signed out. Records of dashboard changes: 365 days by default. Security records, and the alerts that carried them: 180 days.
• When the bot is removed from a server, that server’s logs, member records, moderation records, tickets, archive and backups are deleted about 7 days later (archived media at once), together with the data of features we have retired. We keep a note of when the bot was removed, and records that are not the server’s own data: security records, plan and licence records, and the managers named in the owner’s panel.
• Otherwise, member records, moderation cases and tickets are kept while the bot remains in the server, because its administrators rely on that history. Your website account and your support tickets are kept until you ask us to delete them.
• Database backups (copies of our whole database, including the data above but not the Media Archive’s files), made daily and before each update, on our servers and possibly also in separate backup storage. Each is deleted at the first daily clean-up after it is 30 days old; the most recent usable backup is kept until a newer one exists.

The website uses only the cookies it needs to work. There are no analytics or advertising cookies.

• 27_access and 27_refresh keep you signed in; page scripts cannot read them. 27_csrf protects against cross-site request forgery.
• 27_oauth links a sign-in in progress to your browser, for ten minutes.
• 27_locale remembers your language, and 27_ann_dismissed the site announcement you closed.
• Your browser’s local and session storage remember announcements and reminders you dismissed, and how often a sign-in refresh was retried.

Discord tokens and two-factor secrets are encrypted at rest; session tokens and recovery codes are stored only as hashes. Two-factor authentication is available for every account, and sign-ins are rate limited. No system is perfectly secure. If we learn that data may have been accessed without permission, we will tell the people affected and inform Discord.

• You can end any session from your account page, and remove 27Guard’s access to your Discord account at any time in Discord under Settings, Authorized Apps.
• Server administrators can choose which events are logged, turn on message-content redaction, turn Anti-Scam off, or remove the bot, which starts the deletion described above.
• To have your archived media deleted, ask that server’s owner, or open a support ticket: our staff can delete it from every server. Each deletion is recorded in an audit log.
• To ask for a copy of your data, a correction, deletion of your website account, or to object to how we use your data, open a support ticket while signed in with that Discord account.
• Depending on where you live, data-protection law (such as Saudi Arabia’s Personal Data Protection Law or the GDPR) may give you further rights, such as receiving your data in a portable form, and the right to complain to a data-protection authority, such as the Saudi Data and AI Authority (SDAIA).

You must meet Discord’s minimum age to use Discord and therefore 27Guard. The service is not directed at children under 13.

When this policy changes, the date at the top changes too. Significant changes will also be announced on the website.

27Guard is contacted through the support tickets on the website: sign in with Discord and open a ticket. This covers questions, privacy requests and reports of misuse.

Open a support ticket