01 Scope & Hosting
This policy describes information handled by Sentinel, the self-hosted Discord bot maintained by mob5824, when its features are used. It applies to data for an instance operated by or for the Maintainer. It does not replace Discord’s privacy policy or the policies of hosting, network, and other services.
For an independently self-hosted or community-hosted copy, the instance operator controls the machine, files, permissions, backups, and retention. Sentinel does not send its local database to the Maintainer by default, and the Maintainer cannot access or delete data on a server they do not operate. Ask that instance’s operator how it handles information.
02 Information Processed
Sentinel processes information needed for the features an administrator enables. Depending on configuration and use, a local instance may store:
| Category | Examples | Purpose |
|---|
| Discord identifiers and settings | Server, member, moderator, role, channel, and message IDs; configured staff roles, channels, and application form settings. | Apply server configuration, authorize staff actions, and refer to the correct Discord resources. |
| Moderation records | Warnings, punishment reasons, member and moderator IDs, role IDs, durations, timestamps, and current or completed status. | Apply timed role actions and show warning counts and moderation history. |
| Applications | Applicant ID, form name and questions, answers, submission time, review references, status, decision maker, and optional decision note. | Route submissions to the configured review channel and let authorized staff review and decide them. |
| Configuration and credentials | Bot token, dashboard key, server settings, form definitions, and optional DuckDNS settings. | Connect to Discord, run configured features, and secure access to the local dashboard. Credentials should be treated as secrets. |
| Operational and dashboard logs | Runtime diagnostics and, for dashboard authentication events, the client network address used for login throttling and security logs. | Operate, troubleshoot, and protect the instance. Details depend on version and operator settings. |
Application answers, reasons, and decision notes are text supplied by members or staff. Server operators should tell members what they ask for and restrict access to staff who need it. Sentinel is not designed as a general archive of ordinary Discord chat; Discord itself and server operators may retain messages sent through Discord.
03 How Information Is Used
An instance uses the information above to receive Discord commands and interactions; check staff permissions; apply or end configured role actions; record warnings, history, and applications; display authorized dashboard views; and send configured notifications or outcomes through Discord.
The Maintainer does not receive information stored by an independently hosted instance through Sentinel’s normal operation. If the Maintainer operates a particular instance, information for that deployment may be handled by its host and settings.
04 Storage & Retention
By default, Sentinel stores its SQLite database, configuration, and local log files on the machine running that instance. File locations depend on the operating system and configuration; the instance operator can inspect them with Sentinel’s path information or configuration. A cloud host, container volume, backup tool, or other provider selected by the operator may also store copies.
- Active punishment records are kept while their role timers are in progress. Completed punishments are kept in history until the operator deletes the relevant records or database.
- Warnings remain on record until an authorized moderator clears them or the operator removes the data.
- Application submissions remain available to staff after a form is changed or removed; no universal automatic deletion period is promised.
- Configuration and logs remain on the host according to that operator’s practices. Backups may persist after a live database entry is removed.
Removing the bot from Discord does not by itself erase its local database, configuration, logs, backups, or messages that were already sent to Discord.
05 Sharing & Third Parties
Sentinel communicates with Discord to receive commands and carry out requested server features. Depending on configuration, it may post moderation notices or application content in Discord channels, send direct messages, or grant configured roles. Discord then handles that information under its own policies and the server’s permissions.
- Instance operator and host: The operator and people with access to the host, database, configuration, dashboard, or backups may be able to view local records. A hosting provider may process data for the operator.
- Optional DuckDNS integration: If enabled, Sentinel sends the configured DuckDNS domain and account token to DuckDNS to update the record; the update can include the host’s public IP address. Keep the token private and consult DuckDNS’s own terms and privacy information.
- Website providers: This site is hosted by GitHub Pages and loads fonts from Google Fonts. Those providers may process connection information under their own policies.
The Maintainer does not sell information from self-hosted copies and does not receive their local records by default.
06 Access, Correction & Deletion
- Self-hosted or community-hosted Sentinel: Contact the instance operator. That operator controls the database and backups and is the person able to review, correct, export, or delete its records.
- An instance operated by the Maintainer: Email with “Sentinel privacy request” and enough detail to locate the relevant data. Do not send passwords, bot tokens, or other secrets.
- Discord-held information: Use Discord’s privacy and account tools for information Discord controls. Removing a bot or leaving a server does not automatically erase records kept by the instance operator.
Requests are handled only for information the recipient controls and subject to applicable law, security checks, and any copies retained in backups or Discord.
07 Security
Sentinel’s dashboard is local-only by default and uses an authentication key. These safeguards reduce risk but cannot guarantee security. The instance operator is responsible for access controls on the host and network, protecting the bot and dashboard credentials, securing the database and backups, and using HTTPS and a firewall when enabling remote dashboard access.
If you use an instance run by someone else, its operator and infrastructure providers may be able to access its records. Share only information you are comfortable giving to that community and its authorized staff.
08 Children’s Privacy
Sentinel is not intended for anyone below Discord’s minimum age requirement or a higher minimum age that applies in their location. Server operators must consider their members’ ages and must not collect information from children in violation of applicable law. If you believe information was collected improperly, contact the relevant instance operator or, for an instance operated by the Maintainer, email the address below.
09 This Website
The project and policy pages are static pages hosted by GitHub Pages. They do not contain a submission form or first-party analytics. The theme preference may be saved in your browser’s local storage; the site code does not send that preference to Sentinel. Google Fonts is requested from Google to render the selected typefaces. GitHub and Google may process connection data under their own policies.
10 Changes to This Policy
This policy may be updated when Sentinel’s features, deployments, or legal requirements change. A revised “Last updated” date will appear at the top of this page. For independently hosted instances, the operator may have different practices and should provide their own notice where required.
11 Contact
For questions about this policy or privacy requests concerning an instance operated by the Maintainer, contact . Include “Sentinel privacy” in the subject and do not include credentials.
Project: ·