Sentinel Privacy Policy
This policy explains what data the Sentinel Discord bot ("Sentinel", "the Bot") collects, why, how long it is kept, and how you can ask for it to be deleted.
In short
Sentinel reads the text of messages from exactly one bot, the counting bot configured by the server, and only to detect the phrase "guild save!". It does not read, store or log what people write.
It stores moderation records (user IDs, reasons, case numbers) so servers can run moderation.
Your data is never sold, shared for advertising, or used to train machine-learning or AI models.
Sentinel is used in one public server and a few private test servers, and this policy applies to all of them.
1. Who operates Sentinel
Sentinel is a Discord moderation bot operated by Param Chandarana ("we", "us"). We are the data controller for the data described below. Contact: support@sentinelbot.tech.
Sentinel is currently used in one public Discord server, (We are engineers), and in a small number of private test servers that we operate. This policy applies to every server where we operate Sentinel. If we add it to more servers, this policy will cover them too, and we will update the date at the top of this page.
Sentinel's source code is public at github.com/param-chandarana/sentinel. This policy covers only the instance we operate. If someone else runs their own copy of the code, that person is responsible for their own instance and for publishing their own privacy policy.
2. Data we collect
A. Data stored in our database (PostgreSQL)
- Server configuration: server (guild) IDs; IDs of the channels set for the counting game and for moderation and ban logs; IDs of the mute and counting-blacklist roles; the counting time window; roles allowed to use each command; appeal-link templates.
- Moderation records (infractions): the Discord user ID of the person actioned; the user ID of the moderator; action type (warn, mute, kick, ban, timeout, counting blacklist); case number; the reason written by the moderator or generated automatically; timestamps; duration and expiry for temporary actions.
- Direct-message retry queue: if a notification DM to an actioned user cannot be delivered, a copy of that notice (written by Sentinel or a moderator, not copied from anyone's messages), the recipient's user ID and delivery status are kept so delivery can be retried a few times. Successfully delivered DMs are not kept in the queue as message text beyond their delivery status.
- Counting save tracking: timestamps of detected guild saves are held only in the Bot's memory, not in the database, and are discarded after the configured time window or when the Bot restarts. If the threshold is reached, an infraction record is created as described above.
B. Data processed but not stored
-
Message content (Message Content Intent): Sentinel
receives message events from Discord's gateway. It checks the author
of each message first and reads the text only when the author is the
single counting bot whose ID the operator has configured
(
COUNTING_BOT_ID). The only thing it looks for is the phrase "guild save!" (case-insensitive). Sentinel acts on a match only if the message is in the server's configured counting channel. Message content from every other author, including all human members, is not read, stored, logged, or transmitted anywhere. The counting bot's message text is also not stored. - Usernames and avatars: used briefly to display profiles in log embeds and command replies, and not saved to the database.
- Member join events: when a member joins, Sentinel checks its database for an active mute or counting blacklist on that user ID and, if there is one, re-applies the role. Nothing from the join event is stored.
C. Data we do not collect
- We do not read or store the content of messages written by human users.
- We do not collect email addresses, real names, IP addresses, payment details, or location data.
- We do not use Discord data for advertising, profiling, or training any machine-learning or AI model.
3. How we use the data
- Moderation: to record warnings, mutes, kicks and bans, and to re-apply roles when a sanctioned user leaves and rejoins.
- Counting rule enforcement: to detect repeated "guild save" abuse, assign the blacklist role, record an infraction, and notify the user and the server's moderators.
- Logging: to post moderation and ban logs to channels chosen by server administrators.
- Notifications: to send the affected user a DM stating the reason, duration, and appeal link if one is configured.
We process this data on the basis of our legitimate interest in keeping the communities that install Sentinel safe and orderly.
4. Storage, security and retention
- Where: data is stored in a PostgreSQL database that runs in a Docker container on a virtual private server rented from Hostinger. It is not stored with any other service.
- Security: credentials are kept in environment files outside the code repository, and access to the server is restricted to the operator. No system is perfectly secure, so we cannot guarantee absolute security.
- Retention of infractions: moderation records are kept for as long as the Bot remains in the server, so moderators have a history. When a moderator deletes an infraction it is hidden from normal views and can still be recovered by the operator. It is permanently erased on request (section 6).
- Server configuration: if Sentinel is removed from a server, that server's configuration and moderation records stay in our database until we delete them. We delete them on request, and email us if you'd like them removed.
- Technical logs: the Bot's application logs contain server names and IDs and error details. They never contain message content. They are rotated automatically and only the three most recent 10 MB files are kept.
5. Sharing
We do not sell, rent, or trade your data. It is shared only with:
- Discord Inc., because the Bot works through Discord's API. See Discord's Privacy Policy.
- Hostinger, as our hosting provider, which stores the server on which the database runs.
- Law enforcement or other authorities, only where we are legally required to.
6. Your rights and choices
-
Access: server staff can view infractions with
/infraction list. You can also email us to ask for a copy of the data we hold about your user ID. - Deletion: email us from, or tell us, your Discord user ID and we will permanently delete your infraction records and any other data tied to your ID within 30 days. A server may ask us to keep some records for moderation, and we will tell you if that applies.
- Opting out of message-content processing: Sentinel does not process message content written by human users, so there is nothing of yours to opt out of. Because it reads the counting bot's messages in the counting channel, members who do not want to appear in those detections can avoid playing in that channel or leave the server.
- Removing the Bot: a server administrator can remove Sentinel from the server at any time, which stops all further processing.
Depending on where you live, you may have additional rights under laws such as the GDPR or similar. Email us to exercise them.
7. Age
Sentinel is used inside Discord, which requires users to meet its minimum age. We do not knowingly collect data from children below that age. If you believe we have, contact us and we will delete it.
8. Changes to this policy
If we change this policy, we will update the date at the top of this page.
9. Contact
Questions, access requests and deletion requests: support@sentinelbot.tech