Last updated: 24 September 2026
This policy explains what information Sentinel collects, why it is used, how long it is kept, and what you can do about it.
Sentinel is a Discord bot for Emergency Response: Liberty County (“ER:LC”) communities. It provides staff shifts, leave of absence (LOA) and reduced activity (RA) requests, moderation records, Roblox account verification, ER:LC server tools and observed playtime. In this policy, “Sentinel”, “we” and “us” mean the Sentinel service and the people who operate it. A “server” or “community” means a Discord server that has added Sentinel.
Summary
- Sentinel stores what the features a server turns on need. Records are tied to Discord and Roblox IDs.
- Each Discord server’s data is kept separate from every other server’s.
- Sentinel does not sell personal information or use it for advertising.
- Sentinel’s public website does not use cookies, analytics or tracking scripts. The separate Roblox verification flow uses short-lived security cookies as described below.
- ER:LC server keys are stored encrypted and are never shown again after they are entered.
- Server administrators can delete their server’s shifts, LOA and RA requests, moderation records and playtime data with /server manage. Members can remove their own Roblox link with /roblox unlink.
- Removing Sentinel from a server does not by itself delete that server’s records. See section 6.
1. Who this policy covers
- Server owners and administrators who add and configure Sentinel.
- Staff members who use Sentinel’s commands.
- Members who link a Roblox account through Sentinel.
- Roblox players that a community records or looks up through Sentinel, for example the subject of a moderation record or a player who appears in an ER:LC server’s data. These people may never have used Sentinel themselves.
- Visitors to the Sentinel website.
2. Information Sentinel collects
What Sentinel stores depends on which features a server enables. Most features are off until a server administrator turns them on.
Discord information
- Discord user IDs of people who use Sentinel, and of the members a record is about (for example who a shift belongs to, who requested an LOA and who reviewed it).
- Discord server, channel, role and message IDs needed to run features, such as configured log channels and the panels Sentinel has posted.
- A record of the roles Sentinel itself has given a member (such as an LOA or RA role), so it can remove them again later.
Sentinel reads a member’s current roles and permissions at the moment they use a command or button, to check they are allowed to. It does not keep a copy of anyone’s full role list.
Sentinel receives messages in channels it can see so it can recognise commands that start with the server’s command prefix. It does not store message content. Text you type into a Sentinel command, such as a reason, is stored as part of the record you are creating.
Sentinel does not store Discord usernames, display names, avatars or email addresses.
Server configuration
Settings chosen by a server’s administrators: enabled modules, the command prefix, the roles that count as Staff, Admin and Management, log channels, shift types, LOA and RA settings, punishment settings, playtime and reward-role settings, verification panel settings, and ER:LC logging and alert settings.
Shifts, LOA and RA
- Shifts: the member, shift type, start and end times, breaks, and any duration added by management for a past shift. If a shift is voided, who voided it, when and why.
- LOA and RA requests: the member, start and end dates, the reason given, the request’s status, who reviewed it and when, and who ended it early and when, if anyone did.
Moderation records
When staff create a punishment record, Sentinel stores:
- the player’s Roblox user ID, and their Roblox username at the time;
- the record type (Warning, Kick, Ban BOLO, Temporary Ban, Ban or Note);
- the reason staff enter, and an evidence link if they add one;
- the Discord user ID of the staff member who issued it;
- the expiry time of a temporary ban;
- for a Ban BOLO, the review decision, who reviewed it and any denial reason; and
- if the record is voided, who voided it, when and why.
While staff prepare a record, Sentinel fetches the player’s Roblox headshot from Roblox so staff can confirm they have the right account. The headshot is shown in Discord only. It is not stored with the record.
Roblox account links
When a member links their Roblox account with /roblox link or a server’s verification panel, Sentinel stores their Discord user ID, their Roblox user ID, their Roblox username at the time of linking, and when the link was made. The username is for display only and may go out of date if it changes on Roblox.
Links are per server. Linking your Roblox account in one server does not link it in any other server.
Linking uses Roblox’s own sign-in. Sentinel requests only Roblox’s basic identity permissions (“openid” and “profile”). Before sending you to Roblox, Sentinel asks you to sign in with Discord, requesting only Discord’s “identify” permission. That step proves the person completing verification owns the Discord account that started it.
Sentinel does not store your Roblox display name, email, age, avatar, friends, groups or inventory, and it keeps no Roblox or Discord sign-in tokens.
While verification is in progress, Sentinel keeps a short-lived record of the sign-in attempt. It holds only hashed security values and an encrypted one-time verifier, with no tokens or account details. Each step expires after ten minutes. The record is deleted when sign-in completes, and an abandoned attempt is removed the next time someone starts verifying in that server.
Verification cookies
The Roblox verification pages set two short-lived cookies, sentinel_discord_verify and sentinel_roblox_link. They last at most ten minutes and exist only to make sure verification is finished in the same browser that started it. They are not used for analytics or tracking, and they cannot be read by scripts on the page.
ER:LC information
Server key. When a server owner links an ER:LC private server with /erlc link, Sentinel stores that server’s ER:LC API key, encrypted, along with who linked it and when. Sentinel never displays the key again, in whole or in part.
Live server data. When staff use Sentinel’s ER:LC commands, Sentinel reads live data from ER:LC’s API, such as the players in the server, and shows it in Discord. This live data is not saved to Sentinel’s database.
Game logs and alerts (off by default). If a server turns them on, Sentinel reads the ER:LC server’s join and leave logs, kill logs and command logs. It uses them to post Join / Leave Logs, Kill Logs, Mass Command Alerts and Off-Duty Command Alerts to the Discord channels the server chooses. These posts show players’ Roblox usernames, with a link to the player’s Roblox profile when ER:LC provides their Roblox user ID. Command alerts also show the command used. Off-Duty Command Alerts match the player to a Discord member only through that server’s Roblox links. They then use the member’s Sentinel shift status, and any exempt roles the server has set, to flag in-game commands run while the member is not on shift. Sentinel does not store the log entries themselves. It keeps only short-lived hashed fingerprints of recent entries, to avoid posting duplicates, and deletes them within minutes. The Mass Command Alert cooldown is kept in memory only.
Remote commands. When a Management member runs an ER:LC command through Sentinel, Sentinel records who ran it, when, the command’s first word only (for example “ban” for “:ban PlayerName”) and the result. The full command text is posted to the server’s ER:LC command log channel and result message. It is not stored in Sentinel’s database.
Observed playtime (off by default)
If a server turns on playtime tracking, Sentinel checks the ER:LC server’s player list about once a minute. It credits time only to players who have linked their Roblox account in that server. Sentinel stores:
- each linked member’s total observed time per day; and
- while a linked player is in the server, their Roblox and Discord IDs and when they were last seen, so the next check can add the time in between.
Players who have not linked a Roblox account in that server are not stored. Observed playtime is an estimate based on Sentinel’s checks. It is not a complete record of time spent in the game.
Audit records
Sentinel keeps an audit trail of administrative and security-relevant actions. Examples include configuration changes, approvals, edits and voids, ER:LC link and unlink, remote command attempts, and data deletions. Each entry records who acted, what they did, when, the outcome, and a small amount of detail. Servers cannot turn the audit trail off. It never contains ER:LC keys or other secrets.
Diagnostic logs
Sentinel writes technical logs so its operators can find and fix problems. These are limited to fixed fields such as event names, error types and Discord server IDs. They are designed never to include ER:LC keys or other secrets, message content, player names, commands, IP addresses or browser details.
Blacklist checks
Sentinel is run alongside Sentinel Core, a separate internal service used by the people who operate Sentinel. Sentinel sends a Discord user ID or server ID to Sentinel Core to check whether that user or server is blacklisted. Sentinel remembers each answer in memory for at most 30 seconds and does not save it.
The Sentinel website
The Sentinel website does not set cookies, use browser storage, or load analytics or advertising scripts. Like any website, its hosting provider may process standard technical information, such as your IP address, to deliver pages and protect the service.
3. How Sentinel uses information
Sentinel uses information to:
- provide the features a server has enabled and show results to the people allowed to see them;
- check permissions before every action;
- link Discord members to their Roblox accounts, and match them to ER:LC players by Roblox user ID;
- read from, and when a Management member asks, send commands to, a linked ER:LC server;
- calculate observed playtime and give configured reward roles;
- post logs and alerts to the channels a server has chosen;
- keep an audit trail of administrative actions;
- refuse service to blacklisted users and servers;
- keep Sentinel secure and investigate abuse; and
- diagnose and fix technical problems.
Sentinel does not sell personal information, use it for advertising, or combine records from different servers into profiles.
Automatic actions
Sentinel performs some actions automatically once a server has set them up. It adds and removes the on-duty role during shifts, gives and removes LOA and RA roles for approved dates, gives Verified or Unverified roles after verification, gives playtime reward roles when a threshold is reached, and posts alerts.
Sentinel does not decide punishments. Moderation records are created by a community’s staff. Commands are sent to an ER:LC server only when an authorised staff member runs them.
Legal basis, where the law requires one
Some privacy laws, such as UK and EU data protection law, require a legal basis for using personal information. Where such a law applies, Sentinel relies on the following:
- Providing what you asked for. When you add Sentinel, use its commands or link your Roblox account, Sentinel uses your information to provide those features.
- Legitimate interests. Sentinel and the communities that use it have a legitimate interest in running staff management, moderation records, ER:LC server tools and playtime features. Sentinel also has a legitimate interest in keeping the service secure, preventing abuse and fixing problems. This is the basis for information about people who have not used Sentinel themselves, such as Roblox players named in moderation records or shown in game logs. Sentinel limits this to what the features described in this policy need.
- Legal obligations. Where Sentinel must keep or disclose information to comply with the law.
Sentinel does not rely on consent as its general basis for using information. If you object to Sentinel using your information on the basis of legitimate interests, you can email privacy@sentinelerlc.com.
4. Separation between communities
Each server’s records, settings, Roblox links and ER:LC connection are stored against that server and are only reachable through it. One server’s staff cannot view or change another server’s data through Sentinel. Each stored ER:LC key is also encrypted so that it can only be decrypted for the server it belongs to.
Within a server, access is controlled by the server owner, members with Discord’s Manage Server permission, and the roles the server has set as Staff, Admin and Management. Server administrators also decide who can see the channels Sentinel posts logs to.
5. Who information is shared with
Sentinel does not sell or rent personal information. It shares information only as needed to run the service:
- Discord: Everything Sentinel shows you is delivered through Discord.
- Roblox: Sentinel asks Roblox to look up accounts by username or ID, to fetch headshots, and to handle Roblox sign-in.
- ER:LC: Sentinel sends a server’s ER:LC key to ER:LC’s API to read that server’s data and to run commands that staff request.
- Hosting providers: Sentinel uses infrastructure providers to host its bot, database and website. The Sentinel bot, including its Roblox verification pages, currently runs on Railway.
- Sentinel Core: User and server IDs are checked against Sentinel’s own blacklist service, as described above.
- The community itself: Records are shown to that server’s members who have permission to see them, and logs are posted to the channels the server chooses.
We may also disclose information if we are legally required to, or where it is necessary to protect people’s safety or to investigate serious abuse of Sentinel.
6. How long information is kept
- Records (shifts, LOA and RA requests, moderation records, playtime totals, Roblox links and server settings) are kept until they are deleted. They do not expire automatically.
- Voided shifts and moderation records stay in the history, marked as void.
- Bulk deletion: A server owner or a member with Manage Server can permanently delete all of that server’s shifts, moderation records, LOA requests, RA requests or playtime data with /server manage. Each deletion is recorded in the audit trail. Bulk deletion does not remove audit records, Roblox links or server settings.
- Roblox links: A member can remove their own link at any time with /roblox unlink, and Management can remove a member’s link. A link is not removed automatically when a member leaves the server.
- ER:LC key: It is deleted when the server owner runs /erlc unlink, or when Sentinel is removed from the server.
- Removing Sentinel from a server does not delete that server’s records. When Sentinel is removed, it stops playtime tracking and game logging for that server. It deletes only the stored ER:LC key, current playtime observations, and game-log fingerprints and tracking state. It does not delete the server’s shifts, LOA and RA requests, moderation records, playtime totals, Roblox links, settings or audit trail. These stay stored, and are available again if Sentinel is added back (playtime tracking stays off until it is turned on again). To delete shifts, LOA and RA requests, moderation records or playtime data, use /server manage before removing Sentinel. For anything else, email privacy@sentinelerlc.com.
- Temporary verification data lasts at most ten minutes per step, as described above.
- Audit records are kept when the records they describe are deleted, including after a /server manage bulk deletion, so the history of administrative actions stays intact. They do not currently expire automatically.
- Diagnostic logs are kept for the log-retention period set by the hosting provider that runs the Sentinel bot. They are not part of any server’s records.
- Messages Sentinel posted to Discord channels, such as logs and alerts, stay in those channels until the server or its members delete them.
7. Security
Measures Sentinel actually uses include:
- ER:LC keys are encrypted with AES-256-GCM, bound to their server, and never shown again after they are entered.
- Only the actual Discord server owner can link, replace or unlink an ER:LC server.
- Roblox verification uses Roblox’s official sign-in with PKCE, state and nonce checks, plus a Discord sign-in step and browser binding to help prevent an account from being linked through a different browser.
- Permissions are checked by Sentinel on every command and button press, not only when a panel is first shown.
- Each server’s data is kept separate from every other server’s.
- Diagnostic logs are restricted to a fixed list of safe fields.
- Sentinel connects to Discord, Roblox, ER:LC and Sentinel Core over encrypted connections.
No online service can promise perfect security. If you find a security problem, please report it privately to security@sentinelerlc.com and do not share it publicly.
8. Your choices and requests
- Members can remove their Roblox link with /roblox unlink. For records a community keeps about you, such as moderation records or LOA history, you can also ask that community’s staff.
- Server administrators can turn modules off in /config, delete their server’s shifts, LOA and RA requests, moderation records and playtime data with /server manage, unlink ER:LC with /erlc unlink, and remove Sentinel from the server.
- Anyone can ask for a copy of, a correction to, or deletion of information Sentinel holds about them by emailing privacy@sentinelerlc.com.
When Sentinel receives a request:
- it may need to confirm that you control the account or server involved before acting on it;
- some records, such as moderation records and LOA history, are created and managed by a community’s staff, so Sentinel may need to involve that community or refer you to it; and
- some information may need to be kept where that is necessary for security, to keep the audit trail intact, to meet a legal obligation, or for another reason the law allows. If Sentinel cannot do everything you ask, it will explain why where it is able to.
Depending on where you live, you may have legal rights over your personal information. Sentinel handles valid requests according to the law that applies.
9. Children and young people
Discord and Roblox set their own minimum ages and their own rules for younger users. Sentinel is used inside those platforms. Sentinel does not ask for anyone’s age or date of birth, and it does not request age information from Discord or Roblox.
Communities that use Sentinel may include young people. A parent or guardian with a privacy concern about a young person’s information may email privacy@sentinelerlc.com. Sentinel may need to verify the request and will handle it according to applicable law.
10. Other services
Sentinel works with Discord, Roblox and ER:LC. Each is run independently and has its own terms and privacy policy, which apply to your use of that service. Sentinel is not affiliated with or endorsed by Discord, Roblox or ER:LC.
11. Changes to this policy
This policy is updated when Sentinel’s features or the way it handles information change. The “Last updated” date at the top shows when it last changed. Where appropriate, significant changes may also be announced on the Sentinel website.
12. Contact
For privacy questions, and requests to access, correct or delete your information, email privacy@sentinelerlc.com.
To report a security vulnerability, email security@sentinelerlc.com.
For general support, email support@sentinelerlc.com.
