The short version: Monolith stores what a community's staff need in order to run that community — who is linked to whom, who was punished and why, who was on duty. It does not read your DMs, it does not sell anything to anyone, and a server owner can have their entire community's data deleted by asking.
Monolith ("we", "the Service") is operated by the Monolith project and is provided to Discord servers running Emergency Response: Liberty County on Roblox. This policy explains what the Service collects, why, how long it is kept, and what you can do about it.
Who controls your data
This matters more than it sounds. When a community installs Monolith, the server owner and their staff decide what is collected and what it is used for. We operate the software and the storage on their behalf.
In practice that means: if you are a member of a community using Monolith and you want your moderation history changed or removed, the people who can decide that are that community's staff, not us. We will act on a verified request from a server owner. We will also act directly on a request about your own linked account — see Your rights.
What we collect
Only what an enabled module needs. Monolith is modular: a community that turns on nothing but moderation never causes dispatch or economy data to be collected at all. Nothing in the table below is gathered "just in case".
| Data | Where it comes from | Why |
|---|---|---|
| Discord user ID, username, avatar | Discord, when you sign in or a staff member acts on you | Identifying you across the product and showing you in staff views |
| Discord server ID, roles, channels | Discord, when the bot is invited | Deciding who may do what, and where the bot posts |
| Roblox user ID and username | You, when you verify; and the game server | Linking your Discord account to your in-game character |
| In-game presence: join and leave times, team, playtime, position | The community's ER:LC server, polled through api.erlc.gg |
Live server views, duty tracking, playtime rewards |
| Moderation records: warnings, kicks, bans, and their reasons | Staff actions in Discord and in game | The punishment history staff rely on, and appeals |
| Staff records: shifts, applications, leave, discipline | Staff use of the Service | Running the staff team |
| Roleplay records: characters, vehicles, citations, arrests, balances | You and staff, through the CAD modules | The in-character systems, where a community enables them |
| Message content | Only in channels a community has explicitly pointed a module at | Tickets, suggestions, and word filtering, where enabled |
What we do not collect
- Your direct messages, and messages in channels no module has been pointed at.
- Voice audio. Voice modules read who is connected and where, never what is said.
- Payment details. There is no payment processing in the Service today; if that changes, this policy changes with it before it launches.
- Anything from Discord servers that have not invited the bot.
- Your Discord password or your Roblox password. Sign-in is OAuth — you authenticate with Discord or Roblox directly and we never see the credential.
Discord permissions and why
The bot asks for the permissions its enabled modules need and no more. Message content is a privileged intent: where a community enables a module that requires it, the bot reads messages in the channels that module is configured for. Turning that module off stops the reading.
Why we are allowed to hold it
Where UK or EU data protection law applies, we rely on legitimate interests: a community cannot be moderated without a record of moderation, and members benefit from consistent, reviewable enforcement. Where you choose to link a Roblox account or create an in-character profile, we rely on your consent, which you can withdraw by asking us, or your community's owner, to remove the link, or by deleting that profile.
Who we share it with
We do not sell data, and we do not use it for advertising. It is shared only with:
- Your community's staff, through the dashboard and in-Discord surfaces — that is the product working as intended.
- Discord and Roblox, as far as is necessary to talk to their platforms on your behalf.
- Police Roleplay Community, through
api.erlc.gg, in order to read your community's game server. - Cloudflare, which carries the traffic to our servers.
- Law enforcement, if we are legally required to.
Your verification is the one thing shared between communities. We keep a single record of your Discord and Roblox link, so joining another server running Monolith links you there and gives you its verified role without verifying again, and that server's staff can see the link. Apart from that, two servers running Monolith cannot see each other's moderation records, staff, or members.
Where it is stored
On our own hardware in the United Kingdom, reached only through Cloudflare — the database is not exposed to the internet. Backups are encrypted and held in object storage. If you are outside the UK, using the Service means your data is transferred there.
How long we keep it
| Data | Kept for |
|---|---|
| Command and event logs | Around 3 days, then summarised into counts and discarded |
| Presence and playtime | While your community is active on the Service |
| Moderation and staff records | Until deleted by staff, or until the community leaves the Service |
| Financial and in-character records | Kept as history; not automatically expired |
| Account links | Until you ask us, or that server's owner, to remove it, and we remove that server's copy. The shared record stays until you ask us to remove it too |
| Everything, after a community removes the bot | Deleted within 90 days unless the owner asks sooner |
Your rights
You can ask us to:
- Show you what we hold about your account.
- Correct it if it is wrong.
- Delete it. Ask us, or your community's owner, to remove your account link from a server, and we remove it; it is not added back if you rejoin. To remove it from every server, ask us. For records held by a community, we will pass a verified request to that community's owner, and will delete directly where we are the ones deciding.
- Object to a particular use, or ask us to restrict it.
One honest limit: a community's moderation history is that community's record of its own enforcement, and a server owner may have a legitimate reason to keep it even after you leave. Where we cannot delete something, we will tell you why rather than quietly not doing it.
Children
The Service follows Discord's own minimum age for your country — 13 in most places, higher in some. It is not directed at children below that age. If we learn that we hold data for someone under it, we delete it.
Security
Access is restricted to the project's operators. Traffic is encrypted in transit, the origin server accepts no direct inbound connections, and credentials are held outside the codebase. No system is perfectly secure, and we will not pretend otherwise: if a breach affects you, we will say so.
Changes
We will update this page when the Service changes and move the date at the top. Material changes — new categories of data, a new recipient — will be announced to server owners before they take effect, not after.
Contact
Reach us through the support channel in the Monolith Discord, or by opening a ticket from the configuration dashboard. We aim to answer requests about your data within 30 days.