Skip to content
Last updated November 6, 2026

Privacy Policy

EvaluBot is built to read your Discord server so it can describe it back to you. This policy explains what it stores, what it never touches, and how you stay in control.

Who this covers

EvaluBot is a Discord server audit bot and a product of Digital Den. This policy applies to the EvaluBot application and the website at evalu.dev. Digital Den is the controller of the personal data described here.

Read-only audits and alerts

EvaluBot's audits and permission alerts have no code path that bans, kicks, edits, deletes, or otherwise changes a server. EvaluBot asks for Administrator so it can see every channel, but audits and alerts use it only to read channels, the ban list, webhooks, invites, integrations, AutoMod rules, server templates, and the audit log. EvaluBot changes a server in one case only: on a Premium server, the channel permissions an admin reviews and applies with /auditchannels. Separately, an admin on a Premium server can change how EvaluBot itself looks in that server with /auditstyle bot: its nickname, avatar, banner, and bio.

Messages EvaluBot sends

Every reply to a command is private to the person who ran it, unless they choose to share a score card. The only messages other people can see in a server are:

  • The permission alerts an admin turns on with /auditmonitor, its test alerts, the notice in the old alert channel when alerts are turned off or moved, and the one-time notice when alerts became critical-only. On Premium, an alert shows who acknowledged it.
  • In the alert channel, when alerts are on, a notice each time someone applies or undoes a channel permission template, naming them and the channels, and each time someone changes alert routing or the permission baseline, accepts a risk or takes one back, or changes EvaluBot's profile, naming them.
  • The permission baseline alert and the weekly digest, on a Premium server that turned them on.
  • A score card when someone shares it, and the public score message an admin posts with /auditcard badge. Nothing about a score is public unless someone chooses to post it.
  • The recurring audit reports an admin sets up with /auditschedule recurring, their skip, hold, pause, and failure notices, and a notice if one stops because the person who set it up deleted their data.
  • One welcome message in the system channel, only when the person who added EvaluBot cannot be reached by direct message.

Direct messages go only to people involved: the copy of a report someone ran; scheduled audit confirmations, results, failures, and cancellations; the welcome to whoever added EvaluBot, or the server owner; permission alerts and notices about alert settings, routing, and baselines to the server owner, and to the previous owner on an ownership transfer; alerts about EvaluBot losing a permission or its place, which reach the owner even with owner DMs off unless the owner turned them off themselves; recurring audit pause and stop notices to the owner; reminders before a higher limit ends; Premium thank-you and plan-ended notices; a note to whoever bought extra audits saying which server they went to; a notice to the owner when EvaluBot is removed from a server with alerts on; and a one-time notice to owners of servers that added EvaluBot before 7 November 2026 without Administrator, saying that private channels drop out of audits and alerts from 16 November 2026.

This website and cookies

evalu.dev uses Google Analytics to understand how visitors find and use the site. Analytics cookies are only set after you accept them in the cookie banner. Until then, and if you reject them, the Analytics script sets no cookies and stores nothing on your device, and Google receives only cookieless signals, such as that a page was viewed, with no identifier that links your visits together. The site uses no advertising or other tracking scripts, and its fonts are served from this domain rather than a third party.

If you accept, Google Analytics sets the _ga and _ga_* cookies, which last up to two years, and Google receives details such as the pages you view, your approximate location, and your device and browser type. Google acts as our service provider, advertising features are turned off, and we keep Analytics data for no longer than 14 months.

Your choice is saved in your browser's local storage so the banner does not reappear on every page. You can change it at any time with Cookie settings in the footer. Rejecting after accepting deletes the Analytics cookies and returns Analytics to cookieless signals only.

The site is hosted on Cloudflare, which processes your IP address and standard request details to deliver pages and protect the site from abuse. Cloudflare may set a strictly necessary security cookie when it screens traffic for bots. Strictly necessary cookies do not require consent.

Information we store

To run audits, deliver alerts, enforce fair usage, and let you review your history, EvaluBot keeps these records in a database, each for as long as stated:

  • Audit records: the requesting user ID, the server ID, the sections requested, the report format, the score, the number of issues found and of critical findings, whether it used an extra audit, and the time. Used for the monthly and daily limits, audit history, and bot statistics. Kept; your user ID is removed by /auditdata delete, or 60 days after EvaluBot is removed from the server unless it is added back. The record stays so the server's monthly count and the bot's totals are kept.
  • First audits: one row per person who has run an audit, holding only the date of their first audit and no user ID, to count how many people use EvaluBot. Kept.
  • Server installs: the server ID, which account added EvaluBot, and when it was added and removed. Used for the welcome message and install tracking. Kept, also after EvaluBot is removed; who added it is cleared by /auditdata delete, or 60 days after EvaluBot is removed unless it is added back.
  • Scheduled audits: the requester, server, sections, format, time zone, run time, status, and last error. Pending ones are deleted when cancelled, by /auditdata delete, or when EvaluBot is removed. Ones that ran or failed are kept, also after removal; the requester's ID is removed by /auditdata delete, or 60 days after EvaluBot is removed unless it is added back.
  • Recurring audits (Premium): the server, report channel, who set it up, frequency, time zone, day and time, format, sections, next and last run, failure count, last error, and next retry. Kept until stopped with /auditschedule cancel, /auditdata delete by the person who set it up (the report channel and the server owner are told), or EvaluBot being removed.
  • Saved time zones: your user ID and the time zone you last picked in /auditschedule, so you are not asked again. Replaced when you pick another and deleted by /auditdata delete.
  • Channel template runs: the server, who applied the template, its name, and each channel's permission overrides before and after, which are role and member IDs with their permissions, for the Undo button on /auditchannels. Deleted after an hour, when used, by /auditdata delete by the person who applied it, or when EvaluBot is removed. The change itself, with the name and user ID of whoever applied it, is also written to the server's own audit log.
  • Accepted risks (Premium): the server, which risk, the reason typed, and who accepted it and when, to keep a risk the server lives with out of its score. Removed with /auditfix unaccept or when EvaluBot is removed. /auditdata delete removes who accepted it.
  • Fix plans (Premium): the server, the steps on its plan and their channel IDs, its score at the start, and who started it and when, to show what got done. Deleted when nothing is left on the plan or EvaluBot is removed. /auditdata delete removes who started it.
  • Permission baselines (Premium): for each server that pins one, role IDs, names, and permissions, channel IDs, names, and the @everyone override in each, and who pinned it and when, to notice drift. No other member or user IDs. Replaced by pinning again, and removed by clearing it or when EvaluBot is removed. /auditdata delete removes who pinned it.
  • Weekly digests (Premium): the server, channel, the next and last send, and who last changed it. Removed by turning it off or when EvaluBot is removed. /auditdata delete removes who last changed it.
  • Alert log (Premium): the server, each alert's title, severity, and topic, whether it was muted, and who acknowledged it and when, for /auditmonitor log and the Acknowledge button. It does not hold the alert's contents, though a title can name a role, bot, or account. Deleted after 30 days or when EvaluBot is removed. /auditdata delete removes who acknowledged it.
  • Alert routing (Premium): the server, the channel for each severity, muted topics, quiet hours and time zone, and who last changed them. Removed by resetting it or when EvaluBot is removed. /auditdata delete removes who last changed them.
  • Extra audits: each server's number of extra audits and, for each purchase, its Discord ID, the server, who bought it, how many audits, and when, so one purchase is never added twice. Kept, also after EvaluBot is removed, since they were paid for. /auditdata delete removes who bought it.
  • Milestones: the server, which milestone, and when it was earned, with no user IDs, to show its progress. Kept, also after EvaluBot is removed.
  • Public score messages: the server, channel, message, and who posted it, to keep the message up to date. Removed by /auditcard badge_off, when the message is deleted, or when EvaluBot is removed. /auditdata delete removes who posted it.
  • Report styles (Premium): the server, theme, accent color, the icon image an admin uploads with /auditstyle, whether EvaluBot's profile was changed, and who last changed them. Resetting clears the theme, color, and icon. Removed when EvaluBot is removed. /auditdata delete removes who last changed them. EvaluBot's nickname, avatar, banner, and bio go to Discord and are not stored here.
  • Section presets saved before November 2026, when EvaluBot stopped offering them: your user ID, the preset name, and its sections. Kept until /auditdata delete.
  • Permission alert settings: the server, whether alerts are on, the alert channel, ping role and owner-DM choice, who last changed the settings, the last alert time, the last delivery problem, and when the server was told about critical-only alerts. Kept until EvaluBot is removed; turning alerts off keeps them. /auditdata delete removes who last changed them.
  • Audit snapshots: for each server, the security-relevant settings from its latest audit of each section, so the next audit can say what changed. This means role and channel IDs and names with their risky permissions, @everyone channel permissions, webhook and integration names, and counts of invites and bans. Snapshots contain no member or user IDs. Replaced at each audit and deleted when EvaluBot is removed.
  • EvaluBot's own footing: for each server with alerts on, EvaluBot's own permissions, its highest role ID, the IDs of roles above it, and whether its place passed the check, so it can alert when it loses a permission or its place, also across a restart. No member or user IDs. Updated at each check and deleted when EvaluBot is removed.
  • Approved Administrator lists: the server, the role and bot IDs the server owner approved, and who approved them and when, to point out new Administrator holders. Replaced when the owner approves again and deleted when EvaluBot is removed. /auditdata delete removes who approved it.
  • Limit grants: the user or server, the higher limit, notes, the expiry, and who granted it. Kept after they expire; /auditdata delete deletes a user's grants.
  • Complimentary Premium: the server ID, who granted it, a note, and the end date. Kept after it ends, until the operator removes it.

What reports contain

Reports are files, not database records. Besides the server's configuration, including the server owner's user ID, a report can name people where a finding is about them: banned users with the recorded reason, invite creators, who created each webhook, who added each bot and integration, who last changed each privileged role, members with their own channel overrides (including people who have left), people with their own access to a private channel, and server template creators (JSON reports only). A report leaves out what Discord does not show the person it is for: channels they cannot see, and the ban list, webhooks, audit log, invites, integrations, AutoMod rules, and templates without the permission each needs. On a Premium server, a report also lists the server's accepted risks with the reason typed, and can carry the colors and icon its admins chose.

In the Recent Activity section, free reports show only how many risky actions of each kind happened in the server's audit log over the last 45 days. Premium reports also name who took each one and who or what it affected, such as the member given a role or the bot added. This exists only in the report file, which is deleted after 24 hours, and never in the database. Report file names include the server's name.

Information we never store

  • Message content. EvaluBot does not use the Message Content intent and does not read your messages.
  • Report contents in the database. Reports are generated as files on the bot host, attached to Discord, and deleted automatically after 24 hours.
  • Audit log dumps. The audit log is read to name who made specific changes (who last changed a privileged role, who made a change in a permission alert, and who added the bot) and, in the Recent Activity section of a report, to list risky actions from the last 45 days. None of it is stored in the database.
  • The contents of permission alerts. On Premium, a 30-day log keeps each alert's title and severity, as described above.
  • What /auditwho shows. It reads a member's roles and channel overrides when an admin asks, and replies only to that admin.
  • Payment details. Discord handles every payment.

Premium and payments

EvaluBot Premium is a Discord server subscription. Discord handles the purchase, billing, and cancellation, and EvaluBot never sees card or billing details. From Discord, EvaluBot learns only which servers subscribe and which account bought each subscription, so it can apply the benefits and send a thank-you message. It keeps that in memory while running and does not store it. Complimentary Premium grants are stored as described above.

Where they are offered, extra audits are a one-time purchase through Discord too. EvaluBot never sees card or billing details for them either. It stores who bought each purchase, as described above, so the audits reach the right server exactly once.

Operational logs

The bot host keeps an operational log that includes server and user IDs, for example a note that an audit could not be delivered to a user by direct message. The log rotates at 10 MB and keeps one previous file, so it holds between 10 and 20 MB of recent activity. Unexpected errors are sent to a private Discord channel or direct message for the operator, with the server or user ID when one is involved.

How we use what we store

  • To generate the audit reports you request, and show what changed since the last audit.
  • To apply the monthly allowance and daily limit fairly across users and servers.
  • To run scheduled and recurring audits at the times set up for them.
  • To deliver the permission alerts a server's admins turn on, naming who made each change, and to alert when EvaluBot loses a permission or its place in the role list.
  • To point out Administrator holders that are not on the list a server owner approved.
  • To welcome the person who added EvaluBot to a server.
  • To show you your audit history and remaining usage, and apply Premium benefits.
  • To keep what a server's admins set up on Premium working: accepted risks, fix plans, alert routing, the alert log, permission baselines, weekly digests, and report styles.
  • To offer Undo for an hour after a channel permission template is applied.
  • To show a server's milestones, keep its public score message up to date, and add extra audits bought through Discord exactly once.
  • To remember the time zone you last picked, so you are not asked again.
  • To operate, protect, and improve the service.

Why we are allowed to use it

Where the GDPR or UK GDPR applies, we rely on these legal bases:

  • Performance of a contract, to run the audits you request, deliver scheduled and recurring audits and the permission alerts a server turns on, and provide Premium and extra audits.
  • Legitimate interests, to enforce usage limits fairly, prevent abuse, keep the service and website secure, keep operational logs, record which account added the bot, keep audit snapshots, and tell a server's admins who made a risky change to that server, took a risky action in it, or changed what its alerts and score show, such as by accepting a risk or changing alert routing. We also rely on it to count website visits from cookieless Analytics signals.
  • Consent, for Google Analytics cookies on the website. You can withdraw it at any time from Cookie settings in the footer.

EvaluBot does not make automated decisions that have legal or similarly significant effects on you.

Retention

  • Report files are deleted from the bot host after 24 hours. The report you downloaded is yours to keep.
  • Audit records are kept so a server's monthly allowance stays accurate. Deleting your data removes your user ID from them, and so does EvaluBot being removed from the server for 60 days. The server's count is kept.
  • Operational logs are overwritten as they rotate, keeping between 10 and 20 MB of recent activity.
  • Each database record is kept for as long as stated under Information we store. Channel template runs last an hour, and the alert log 30 days.
  • Expired limit grants and complimentary Premium grants stop applying but stay on record.

When EvaluBot is removed from a server

Its permission alert settings, audit snapshot, pending scheduled audits, recurring audits, recorded footing, approved Administrator list, channel template runs, accepted risks, fix plan, alert routing, alert log, permission baseline, weekly digest, report style, and public score message record for that server are deleted. Audit records, limit grants, the install record, scheduled audits that already ran, and complimentary Premium are kept so that removing and re-adding the bot cannot reset the monthly limit. 60 days after the removal, unless EvaluBot was added back, people's IDs are removed from them: who ran each audit, who scheduled it, and who added EvaluBot. Extra audits and their purchase records, which were paid for, and milestones are also kept. Servers that remove EvaluBot while it is offline are cleaned up the same way when it next starts.

Your controls

EvaluBot gives you self-service commands to see and remove your data directly inside Discord:

  • /auditdata view shows counts of what is stored about you.
  • /auditdata delete asks first, with Delete and Cancel buttons. It then deletes your saved time zone, presets, limit grants, pending scheduled audits, the channel template runs you applied, and the recurring audits you set up, and clears you as the account that added any server. When it stops a recurring audit, the report channel and the server owner are told.
  • Your past audit records, past scheduled audits, and your name on alert settings, alert routing, acknowledged alerts, permission baselines, weekly digests, accepted risks, fix plans, public score messages, report styles, extra audit purchases, and approved Administrator lists are anonymized, with your ID removed, rather than deleted. A server's monthly count belongs to the server, so erasing your data cannot reset it, and what its admins set up stays in force. An audit of yours that is already running when you delete is counted for the server the same way, without your ID.

Anyone can use these commands, with no permissions needed, in any server with EvaluBot or in a direct message with it. For any request they do not cover, open a ticket in the support server and we will help.

Your rights

Depending on where you live, you may have the right to access, correct, delete, or export your personal data, to restrict or object to how we process it, and to withdraw consent. The commands above cover most requests instantly. For anything else, ask in the support server.

If you are in the EEA or the UK, you also have the right to complain to your local data protection authority, such as the UK Information Commissioner's Office. We would appreciate the chance to resolve your concern first.

Permissions and access

EvaluBot's install link asks for Administrator, so it can see every channel: from 16 November 2026 Discord only shows a bot the channels it can view. You can install it with fewer permissions instead, from the links on our permissions page. If you do, only the matching report section or feature is limited, and EvaluBot says so. It uses no privileged intent: not Server Members, Message Content, or Presence. Per-role member counts come from Discord's role member counts. You can review or change these permissions in your Discord server settings at any time.

Third parties

EvaluBot runs on the Discord platform and reads server data through Discord's official API, so your use is also subject to Discord's own terms and privacy policy. Discord also processes Premium payments. Data is processed on the infrastructure that hosts the bot and its database. To make a PDF report, EvaluBot sends the finished report to Cloudflare Browser Run, which prints it and returns the file; Cloudflare handles it as a processor under its data processing terms. EvaluBot keeps only the finished PDF, deleted after 24 hours like every report file. A score card goes the same way, with only the server's name, icon, score, date, and milestones, and is not kept. EvaluBot posts its server count to top.gg every 30 minutes, with no personal data. The website is served by Cloudflare and measured by Google Analytics. We do not sell your data or share it for advertising.

Reports carry no ads, partner offers, or affiliate links. Links to Digital Den's free tools carry a tag (utm_source=evalubot) so dgden.com's analytics can count visits from EvaluBot.

Discord, Google, Cloudflare, and our infrastructure providers may process data outside your country, including in the United States. Where data leaves the EEA or the UK, it is protected by the safeguards those providers offer, such as the EU-U.S. Data Privacy Framework or Standard Contractual Clauses.

Age

EvaluBot is intended for Discord users who meet Discord's minimum age requirement. Do not use the bot if you do not meet that requirement.

Changes to this policy

We may update this policy as EvaluBot evolves. When we do, we will revise the date at the top of this page.

Contact

Questions about privacy or your data are welcome. The Digital Den support server on Discord is the only support channel, so please raise privacy and data requests there. You can also read our Terms of Service.