Privacy Policy

Last updated: 22 October 2026

This policy explains what Sentry ("the Bot") stores, why, and for how long. It applies to the Sentry Discord application operated by Progames_exe ("the developer", "we").

Contact for anything in this policy: the Sentry Support server, or support@sentrybot.net.

Who is responsible for what

Two different people have a hand in your data, and it is worth being clear about which is which.

• Your server's owner and moderators decide what Sentry records. They choose to add it, which features to switch on, who may use which commands, and whether to warn, ban or log anything at all. If you are a member of a server and want something removed, they are the first people to ask.
• The developer runs the machine it is stored on. We keep the database, take the backups, and carry out deletion requests.

Where the law uses the words, the server is the controller of what it chooses to record, and the developer is the processor that stores it — with the developer also acting as controller for the small amount of operational data below, such as which servers Sentry is in.

What is stored

Server settings

When a server configures Sentry, the choices are stored against that server's Discord ID:

• Logging — which channel receives logs, and which categories are on
• Verification — the panel channel, the verified role, the optional unverified role, and a count of how many members have verified
• Autorole and self-role panels — which roles are given on join, and the roles offered on a panel with their labels
• Automod — which filters are on, the blocked-word list the server set, the mention limit, and which roles and channels are exempt
• Anti-raid and anti-nuke — the thresholds, the alert channel and role, and which roles or users are exempt. If anti-nuke quarantines someone, the roles it took are stored so they can be given back
• Tickets — the panels and their categories, which staff role answers them, who is blocked from opening one, and the ratings members leave for the staff who handled theirs
• Autoresponders — the trigger phrases and the replies the server wrote
• Appeals — which channel receives ban appeals
• The date Sentry joined the server

Moderation records ("cases")

When a moderator uses Sentry to warn, timeout, kick, ban, softban or unban someone — or when automod or a spam trap acts automatically — Sentry stores:

• The Discord user ID of the member the action was taken against
• The Discord user ID of the moderator who took it, or Sentry's own ID for automatic actions
• The type of action, the reason text that was entered, any duration, and the time

This is the history shown by /history, /warnings and /case.

Ban appeals

If a server switches appeals on, a banned member can send one appeal through a button in the DM their ban produced. Sentry stores the text they wrote, their user ID and username, when they sent it, and — once staff decide — which outcome and which moderator decided it.

An appeal is written by the person themselves and can contain anything they choose to put in it. Only staff of the server they were banned from can read it.

Invite records

If a server grants the Manage Server permission, Sentry works out which invite each new member used. For each join it stores: the member's user ID, the user ID of whoever created the invite, the invite code, whether the account was less than seven days old at the time, when they joined, and when they left.

This is how /invites and /inviteleaderboard work. It is a record about every member who joins, including members who never use the Bot, so it is called out separately here rather than buried in the list above. A server that does not want it can simply not grant Manage Server, and nothing is recorded.

Scheduled actions

Temporary bans, timed channel locks and ticket auto-closes are stored with the user or channel they apply to and the time they expire, so they still take effect after the Bot restarts.

What is not stored

• Message content is never written to disk. /snipe keeps recently deleted messages in memory only and loses them when the Bot restarts. Automod inspects a message as it arrives and keeps a rolling ten-minute window in memory to detect spam; nothing is saved.
• Ticket transcripts are not kept by us. When a ticket closes, the transcript is built, sent to the server's log channel and to the member who opened it, and then discarded. The copies live in Discord, in your server and in that member's DMs — not in our database.
• Direct messages. Sentry sends DMs to tell members about actions taken against them, and does not read or store any reply.
• Member lists, voice activity, presence, or any analytics about individual people.
• Email addresses, IP addresses, or payment information. Sentry asks for none of these and has no payments.

Why it is stored

Server settings exist so the Bot behaves the way a server configured it. Moderation records exist so moderators can see a member's history before acting, which is the core purpose of a moderation bot. Appeals exist so a ban is not necessarily the end of the conversation. Invite records exist so a server can see who is bringing people in. Scheduled actions exist so a temporary ban actually ends.

There is no other purpose. Your data is not sold, rented, shared with third parties, used for advertising, or used to train anything. It is not used to profile anyone, to judge anyone's character, or for any decision about employment, housing, credit or insurance.

Who can see it

• Inside your server: whoever your server permits to use the relevant commands. Case history needs Moderate Members by default; deleting a case needs Administrator.
• The developer: has access to the database in order to run and fix the Bot, and to the backups. It is not read for any other reason.
• Discord, as the platform all of this runs on, under their own privacy policy.

Nobody else. There are no third-party analytics, no advertising networks, and no data processors other than the hosting provider that runs the Bot.

How long it is kept

The 14-day window exists because servers remove bots by accident, or while fixing permissions. If Sentry is added back within that time, everything is still there. After 14 days it is deleted and cannot be recovered.

Because backups are kept for about a week, data you delete may still exist in a backup for up to seven days after deletion before it ages out. It is not restored into the live database unless the host loses the database entirely.

Your rights

Whatever country you are in, you can ask us to do all of these. We do not distinguish between jurisdictions, because it costs nothing to offer them to everyone.

• See what is stored. /config shows every setting for a server; /history shows a member's full record; /invites shows the invite counts held for someone. For anything beyond that, ask.
• Correct something. /case reason edits the reason on a case.
• Delete something. /case delete <number> removes a single case (Administrator). /clearwarns removes a member's warnings.
• Delete everything for a server. Remove Sentry from it. Everything goes 14 days later, or immediately if you ask.
• Ask a human. Email or the support server, either is fine.

We will respond within 30 days. For a deletion request we verify that you own or administer the server in question, or that the data is your own, before acting — otherwise anyone could erase somebody else's moderation history.

If you believe your data has been mishandled, you may complain to your local data protection authority. In India this is the Data Protection Board; in the EU or UK it is your national supervisory authority.

Children

Discord requires users to be 13 or older, or the minimum age of digital consent in their country, whichever is higher. Sentry is not directed at children and is not intended for anyone below that age. If we learn that data about someone under Discord's minimum age has been stored, it is deleted.

Security

Being specific is more useful than being impressive, so:

• The database is a single file on the Bot's host, reachable only by the Bot and the developer.
• Backups are uploaded to a private Discord channel that only the developer can read.
• The Bot's token and all credentials are held in environment variables, never in the source code, and the source repository is private.
• Access to the host is protected by the hosting provider's own account security.

No system is perfect, and no promise of absolute security is made. If a breach affects stored data, it will be announced in the support server and, where the law requires it, reported to the relevant authority.

The law

Sentry is operated from India by a single developer, and is free.

• India's Digital Personal Data Protection Act applies to the developer, and this policy is written to serve as the notice it requires.
• The GDPR and UK GDPR apply to members in the EU, EEA and UK regardless of the size of the operator. The rights above are offered accordingly.
• The CCPA and CPRA are not claimed. Sentry meets none of the thresholds that would make it a covered business — it has no revenue, sells nothing, and is nowhere near 100,000 California consumers. Saying otherwise would be untrue. The rights above are offered to Californians anyway.

Sentry has no EU representative under GDPR Article 27. If it grows to a size where that is warranted, this policy will be updated to name one.

Changes

This policy changes when Sentry changes. The date at the top is updated whenever it does.

Material changes are announced in the support server at least 30 days before they take effect, so you have time to remove the Bot if you disagree. Smaller corrections — fixing a wrong number, clarifying wording — take effect when the date changes.

Continuing to use the Bot after a change means accepting the updated policy.