Privacy Policy
What personal data Sentinel handles, why, who receives it, how long it is kept and how to use your rights.
1.The short version
- Sentinel is a Discord bot run by an individual in France. It processes Discord data (IDs, usernames, roles, messages the bot needs to act on) to provide the features that Server Administrators turn on.
- The website has no advertising, no analytics and no tracking. It stores your language choice in your browser. If you log in or verify, it sets short-lived cookies.
- Logging in with Discord shows you your servers; verifying on a server’s page lets that server give you a role. Discord’s access token is revoked immediately and never stored.
- Most bot data is kept until it is deleted by Administrators or on request. You can ask for access, correction or deletion at any time at [email protected]; requests are answered within one month.
- Your data is not sold. It is shared only with the services needed to run Sentinel, listed below.
2.Who is responsible
The Sentinel bot, the website and the login and verification service are operated by zxdac_, an individual acting in a non-professional capacity, based in France (see the legal notice). Contact: [email protected]. There is no data protection officer.
Roles differ by situation. For the website, the login and verification service, support requests, security and the operation of the Bot itself, the Operator decides why and how data is used and is the controller. For data about a community’s members that exists because a Server’s Administrators enabled a Module (for example warnings, tickets, levels or verification settings), the Administrators decide the purposes and means for their community and are controllers of that community data; the Operator provides the tool and processes the data on their behalf and under their configuration.
3.What this policy covers
This policy covers the Sentinel Discord bot, the website at sentineldashboard.site, the optional Discord login, the server verification page and communication with the Operator (e-mail and support server). It does not cover Discord, GitHub, Cloudflare or other services, which have their own policies, nor Servers’ own rules and notices.
4.Data we process
This list was established by reading the bot’s source code. What is actually created depends on the Modules each Server enables. Data comes from Discord (events the Bot receives and information about accounts, roles, channels and servers), from what you type into commands and panels, and from what Administrators configure.
| Category | What it can include | Where it lives |
|---|---|---|
| Server configuration | Server, channel, role and message IDs; module settings; welcome texts; panel messages; verification settings | JSON files and SQLite databases in the bot’s data folder |
| Moderation records | Warnings per member (reason, moderator, date); AutoMod incidents and statistics (capped at 2,000 incidents per server); AntiNuke and security settings and logs | storage and AutoMod data files |
| Member activity | Leveling XP, message and voice activity counters, economy balances and transactions, missions, user statistics, polls, reminders | JSON files and SQLite databases |
| Tickets | Ticket metadata and events, participants, staff notes, ratings, and generated transcripts (which can contain the messages exchanged in the ticket) | Ticket SQLite database |
| Verification and giveaways | Verification configuration and logs; giveaway entries and winners | Module data files |
| Content members provide | Social profile links, saved profile pictures, movie watchlists and history, subscriptions to social accounts, text submitted to commands | Module data files |
| Server backups | Structure of a server (roles, channels, settings) when an Administrator creates a backup or snapshot | Backup files created on demand |
| Direct messages | Optional welcome and verification DMs sent by the Bot; support requests started with the support command (issue type, subject, description) | Sent through Discord, or to the support server |
| Technical logs | Events and errors written by the Bot (for example IDs of servers and users involved in an error) | Host-dependent log output |
Typical Discord data used across Modules: user IDs, usernames, display names, avatars, roles, permissions, join dates, voice-channel state, reactions, message IDs and, where a Module needs it, message content and presence status (see next section).
5.Message content, presence and intents
The Bot asks Discord for the Server Members, Message Content, Presence, Voice States, Messages and Reactions intents. The Bot reads message content in real time so that AutoMod, leveling, counting, the honeypot trap and Flow triggers can work. Presence data is used for features such as roles based on a member’s status. In most cases content is evaluated in memory and not stored; where a Module stores content or an excerpt (for example ticket transcripts), it is described in the table above. The Bot does not read messages in order to build advertising profiles, and it does not sell or share them.
6.Website, cookies and local storage
The website is a static site hosted on GitHub Pages. It has no advertising, no analytics, no tracking pixels and no third-party cookies. Fonts are hosted on the site itself. As with any website, the hosting provider and the network necessarily process technical data such as your IP address, browser type and the pages requested when you load a page; these are handled by GitHub and, for the login and verification service, by Cloudflare.
A few images are loaded from Discord’s servers (for example the team avatars and server icons), so Discord receives your IP address when your browser fetches them.
| Name | Purpose | Duration | Set by |
|---|---|---|---|
sentinel_session (cookie) | Keeps you logged in on the dashboard page after “Login with Discord” | 24 hours or until you log out | api.sentineldashboard.site |
sentinel_state (cookie) | Protects the login and verification redirect against forgery | 10 minutes | api.sentineldashboard.site |
sentinel_verify (cookie) | Holds your verification step on the verification page | 15 minutes or until verification completes | api.sentineldashboard.site |
sentinel.lang (local storage) | Remembers your language choice (English or French) | Until you clear your browser data | sentineldashboard.site |
The cookies above are strictly necessary for the feature you request (staying logged in, completing a verification) and are not used to track you across sites, so they do not require a consent banner. They are HttpOnly, Secure and SameSite=Lax. You can delete cookies and local storage in your browser at any time.
If a captcha is enabled on the verification page, it is provided by Cloudflare Turnstile, which processes technical information from your browser (such as IP address and browser characteristics) to tell humans from bots.
Support form. If you use the contact form on the Support page, the e-mail address, Discord username, subject and message you type are sent by e-mail to the Operator using Resend’s email API so that we can answer you. To limit abuse, a keyed hash of your IP address (not the address itself) is kept for 60 seconds to allow one message per minute. The e-mail is kept in the Operator’s mailbox as long as needed to handle your request, and is deleted on request.
7.Login with Discord
The dashboard page can log you in with Discord (OAuth2) so it can show you the servers you manage. It requests the identify and guilds scopes only. It reads your Discord ID, username, display name, avatar and the list of servers you are in, and keeps only the servers you own or where you hold Manage Server or Administrator permission, with whether Sentinel is present there.
This information is stored for up to 24 hours under a random session identifier held in the sentinel_session cookie, so the page can show it. Discord’s access token is revoked right after your identity is read and is never stored. The login cannot read your messages or e-mail address, cannot join servers for you and cannot change your account or your servers. Log out on the dashboard page to delete the session immediately, and you can remove the authorisation in Discord under User Settings → Authorized Apps.
8.Server verification page
When a Server uses Sentinel’s verification gate, its members are sent to a verification page on this website. To verify, you log in with Discord using only the identify scope. The service then reads your Discord ID, name and avatar, checks with the Bot whether you are a member of that Server and whether you already hold the role, applies the thresholds the Server set (minimum account age, which is derived from your Discord ID, and minimum time in the Server), and, if everything passes, gives you the verified role and removes the unverified role if one is set. If the Server enabled it, the Bot also posts a short message in the Server’s log channel saying that you verified.
The verification session lasts at most 15 minutes. The Discord token is revoked immediately and never stored. The service stores, per Server, the settings the Bot registered (see retention). A verification is not an identity check: it does not collect your real name, your age or any document.
9.Why we use data and on what legal basis
Data is used only for the purposes below and not for advertising, profiling for sale, or training of AI models by the Operator.
| Purpose | Main data | Legal basis (GDPR) |
|---|---|---|
| Run the features a Server enables (moderation, tickets, leveling, giveaways, welcome, music…) | Discord IDs, configuration, module data, message content as needed by the module | Legitimate interests of the Operator and of the Server in providing and using the tools (Art. 6(1)(f)); for the person who requests a feature, performance of the service they asked for (Art. 6(1)(b)) |
| Security, abuse and fraud prevention, including AutoMod, AntiNuke and verification | IDs, account age, join date, event counts, incident records | Legitimate interests in protecting servers, members and the Service (Art. 6(1)(f)) |
| Website login and server verification | Discord ID, display name, avatar, server list or membership check | Your request to log in or verify (Art. 6(1)(b)), and legitimate interests in securing the Service (Art. 6(1)(f)) |
| Support and communication | E-mail address, Discord ID, content of your request | Legitimate interests in answering you (Art. 6(1)(f)); steps at your request (Art. 6(1)(b)) |
| Maintaining, debugging and improving the Service | Technical logs, errors | Legitimate interests (Art. 6(1)(f)) |
| Complying with the law and defending legal claims | Any data needed for the request | Legal obligation (Art. 6(1)(c)); legitimate interests (Art. 6(1)(f)) |
10.Who receives data
- Discord Inc.: everything you do on Discord, including the Bot’s API calls, is processed by Discord under its own policy.
- DisHost (dishost.fr, France): hosts the Bot and its data on a Pterodactyl panel.
- Cloudflare, Inc.: runs the login and verification service (Workers and KV storage) and, if enabled, the Turnstile captcha. It acts as a processor.
- GitHub, Inc.: hosts the static website (GitHub Pages) and receives technical data when you load it.
- Server Administrators and staff: can see data about their own community that the Bot records (warnings, tickets, transcripts, levels, verification logs).
- Authorities: when the law requires it, for example on a valid legal request.
Your data is not sold, rented or used for advertising.
11.Third-party services used by commands
Some commands send what you type, or identifiers derived from it, to the services below. Only the commands you run trigger these requests, and their own policies apply.
- Lavalink music node: search queries and track identifiers for music playback. By default this is a public third-party node set in the code.
- OpenRouter and the underlying model provider: prompts sent to AI chat, and prompts used by AI server generation.
- Pollinations: prompts for AI image generation.
- Lookup and content services: depending on the command, TMDB, MusicBrainz, OpenStreetMap/Nominatim, ArcGIS, GitHub, IP, RDAP and DNS lookup services, public SearXNG instances and image APIs, YouTube, TikTok and similar platforms.
Do not type secrets or sensitive personal data into commands that call external services.
12.Transfers outside the EEA
The Bot is hosted in France. Several recipients are established in or use infrastructure in the United States or elsewhere (Discord, Cloudflare, GitHub and several third-party services). Where personal data is transferred outside the European Economic Area, it relies on the safeguards those providers use, such as the EU-US Data Privacy Framework or standard contractual clauses, as described in their own documentation. You can ask the Operator for more information at the contact address.
13.How long we keep data
The Operator does not erase stored bot data on a schedule, so most of it remains until it is deleted by Administrators or on request. Short-lived website records expire on their own.
| Data | How long |
|---|---|
| Login session record (Discord ID, name, avatar, list of servers you manage) | Up to 24 hours, then it expires automatically; deleted when you log out |
| Verification session (Discord ID, name, avatar, server ID) | Up to 15 minutes, or until verification completes |
| Short anti-abuse delay on verification attempts | 60 seconds |
| Discord access token used during login or verification | Revoked immediately after your identity is read; never stored |
| Server verification settings (server ID, role IDs, log channel ID, age thresholds, server name and icon) | Until the Server’s Administrators change them or ask for deletion |
| Bot data (configuration, moderation records, activity, tickets, backups, content) | The Operator does not delete this data on a schedule. It stays until it is removed by the Server’s Administrators with the Bot’s own commands, or until you or an Administrator ask for deletion. Some Modules apply their own limits (for example AutoMod incidents are capped at 2,000 per server; notification subscriptions are removed when the Bot leaves a server) |
| Technical logs | Kept by the hosting environment for as long as its log settings keep them |
| E-mails and support requests | For as long as needed to deal with the request and the follow-up it requires, then deleted on request |
14.Security
The Operator takes reasonable steps to protect data, and describes here only measures that exist:
- The website and the login and verification service are served over HTTPS.
- The Discord client secret and the bot credentials are kept as encrypted secrets in the Worker’s environment and are never sent to the browser or published on the website.
- Session cookies are
HttpOnly,SecureandSameSite=Lax. The login redirect is protected with a signed state value, and actions that change state check the request origin. - Discord access tokens are revoked immediately after use and are not stored. Sessions expire automatically.
- Verification re-checks every condition on the server side; the browser cannot grant itself a role.
The Bot itself does not encrypt its data files at rest; they are protected by the hosting environment’s access controls. No system is perfectly secure, and the Operator cannot guarantee absolute security.
15.Your rights
Under the GDPR and the French Data Protection Act, and subject to the conditions the law sets, you have the right to:
- access your personal data and get a copy;
- rectify inaccurate or incomplete data;
- erase your data (“right to be forgotten”);
- restrict the processing of your data;
- object to processing based on legitimate interests;
- data portability for data you provided, where the processing is based on consent or a contract and is automated;
- withdraw consent at any time where processing relies on it;
- give instructions about your data after your death (France).
If you live elsewhere, you may have similar rights under the law of your country.
16.How to exercise your rights
Write to [email protected], or contact the Operator on the support server. To protect your data from being handed to someone else, the Operator may ask you to prove that you control the Discord account concerned, for example by sending the request from that account. Please give your Discord user ID and, if you can, the Servers concerned.
Requests are answered within one month. Where the law allows, this period can be extended for complex requests, and you will be told. Requests are free unless they are manifestly unfounded or excessive. Because most community data is controlled by Server Administrators, the Operator may need to involve them, or may direct you to them.
If you are not satisfied, you can complain to the French data protection authority, the CNIL (cnil.fr), or to the authority of your country of residence.
17.Server administrators
If you manage a Server, you decide which Modules run there and what they record about your members. You are responsible for having a legal basis, for informing your members (for example about moderation logs, ticket transcripts, verification and levels), for answering their requests about data you control, and for not enabling features that you cannot justify. You can disable Modules, delete records with the Bot’s commands, remove the Bot, or ask the Operator to delete your Server’s data.
18.Automated tools
AutoMod, AntiNuke, verification and some other Modules take actions automatically when rules configured by a Server’s Administrators are met (for example deleting a message, timing out a member or withholding a role). They do not produce legal effects beyond what the Server’s own rules provide. The Operator does not make decisions about individuals. If you think an automated action was wrong, contact the Server’s staff, who can review and reverse it.
19.Children
Sentinel is meant for Discord users aged 13 or older, in line with Discord’s own minimum age, and the Operator does not knowingly collect data from younger children. Where the law of your country requires parental consent for a young person’s data to be processed (in France, under 15 for processing based on consent), a parent or guardian should agree on their behalf. If you believe a child under 13 has used the Service, write to the Operator and the data will be deleted.
20.Removing the bot and deleting data
Removing the Bot from a Server does not automatically erase everything it stored about that Server: configuration and records generally remain, except that notification subscriptions are removed. To have a Server’s data deleted, an Administrator can use the Bot’s commands to clear module data where they exist, or write to the Operator. To have your own personal data deleted, follow the “How to exercise your rights” section. Deletion applies to the Bot’s own files and to the login and verification service; copies held by Discord or by other third parties are governed by their policies.
21.Data breaches
If a personal data breach occurs that is likely to create a risk for people, the Operator will notify the competent authority and, where the law requires it, the people affected, within the deadlines the law sets.
22.Changes to this policy
This policy may change as the Service evolves. The date of the latest version is shown at the top of this page, and significant changes may also be announced on the support server.
23.Contact
For anything about your data: [email protected], or the support server linked in the footer of every page. Operator: zxdac_, France. Requests are answered within one month.