Privacy Policy
What is stored, why, who can see it, and how to have it removed.
The short version
Verifying shares your Roblox username and user ID, and nothing else. Your password is typed on Roblox’s own site and never reaches this service. Nothing is sold, and nothing goes to advertisers.
What is received when you verify
Pressing Verify sends you to Roblox’s own sign-in page. Roblox returns only your user ID and username, using the openid and profile scopes. Not your email address, date of birth, friends, inventory, or account balance.
With Legacy Verification you never sign in at all: you place a one-time code in your Roblox profile description, and the bot reads your public profile to confirm it.
What is stored
- Account link
- Your Discord user ID, your Roblox user ID and username, how you verified, and when.
- Support tickets
- What you write in a ticket, and a transcript kept after it closes.
- Staff records — staff only
- Shift times, leave of absence requests and reasons, promotions and disciplinary records.
- Server activity
- Suggestions and votes, giveaway entries, purchase claims you submit including any screenshot attached, and a count of removed messages in a counting channel.
Why
To confirm you own the Roblox account you claim, to assign roles and set nicknames, to run in-game sessions and staff shifts, and to keep a record of moderation decisions. That is the whole purpose. No advertising profiles are built and no data is sold.
Who else sees it
- Discord
- The bot runs on Discord, so messages and roles necessarily pass through it.
- Roblox
- Only during sign-in, to confirm your account.
- Anthropic — only if that server has enabled it
- Support tickets can have an AI assistant. Where a server has switched it on and supplied its own API key, the text you write in a ticket is sent to Anthropic to generate a reply. Most servers instead use the built-in answer matching, which sends nothing anywhere. Either way, do not put passwords or personal details in a ticket — and if you would rather a human handled it, say so and staff will take over.
- That server’s staff
- Staff can read tickets and staff records for the server they run, as part of moderating it. Staff of one server cannot see another server’s data.
Keeping servers separate
Each Discord server’s configuration and records are stored against that server alone. Any API keys a server provides — for its Roblox game server, or for the AI assistant — are encrypted before being stored, so a copy of the database is not a copy of anyone’s credentials.
Where it is kept
On a private server rented from Hetzner in Germany. Access is limited to the bot’s operator. Traffic to this site is encrypted with HTTPS.
How long
Account links are kept while the link is in use. Ticket transcripts and staff records are kept as a moderation history unless removal is requested. Verification codes and in-progress sign-in states expire within minutes and are deleted once used.
Removing your data
Open a ticket in the Discord server that sent you here and ask. Your account link can be deleted on request. Leaving a server does not delete records by itself.
The CAD, and your ER:LC server
Servers on Sample Plus+ can connect a Computer Aided Dispatch system to their Emergency Response: Liberty County private server. Doing so means the bot reads that server through Police Roleplay Community’s API, using a key the server owner supplies.
What is read from the game
Who is in the server and their Roblox username and user ID, the team and callsign they
are playing on, where they are standing, the street and postal they are in, vehicles that
have been spawned and their plates, join and leave logs, kill logs, moderator calls, and
emergency calls players dial in game.
What is recorded
Calls raised in game, traffic stops, plate checks, staff logs (warnings, kicks, bans and
ban requests) with the reason given and who issued them, on-duty periods and unit
statuses, and a short activity feed. Characters, vehicles, licences and records a
community creates in the CAD are stored against that community.
Bodycams and traffic cameras — pictures of your own screen
A member may start a bodycam. If they do, their browser asks them to share a window or
screen, and a still image is taken from it roughly every two seconds and stored so other
members of that community can watch it. This is ordinary browser screen sharing: nothing
is captured from Roblox itself, nothing is installed, and it only happens after the person
chooses what to share and presses start. It stops when they stop it or close the tab, and
the frames are deleted automatically — about two minutes are kept at any time, and
nothing is retained beyond an hour. Do not share a screen with anything on it you would
not want that community’s staff to see.
Messages sent into the game
The CAD sends private messages in game — being assigned to a call, a warning, a panic
alert. These pass through Roblox and its chat filter like any other in-game message.
Who sees it
Only members of the community it belongs to, and only the parts their rank allows. A fire
crew cannot look up criminal records; a civilian sees their own characters and a list of
open incidents without names attached. One community can never see another’s data.
ER:LC server keys are encrypted before being stored. Police Roleplay Community receive the requests the bot makes against their API, as the operator of that game and its API.