Privacy policy
What data Jackson County Roleplay collects through our website and Discord bots, why we collect it, where it goes, and how to get it deleted.
1. Who we are
Jackson County Roleplay ("JCRP", "we", "us") is a community-run Emergency Response: Liberty County roleplay community on Roblox. We are a hobbyist community, not a registered company.
This policy covers:
- jacksoncountyroleplay.com — our public website.
- JCRPBot — our main community Discord bot.
- JCRP Staff Management — our internal, staff-only Discord bot.
Together these are referred to as "the Services". You agree to this policy by doing any of these:
- joining our Discord server;
- using our bots;
- playing on our ER:LC private server.
2. What we collect
We only collect what our features actually need. We do not buy data, sell data, or run advertising.
Discord account data
- Your Discord user ID, username, display name and server nickname.
- Your avatar (fetched from Discord for display).
- Your roles in our server, and changes to them over time.
- Whether you are a member of our server, and when you joined or left.
- Moderation history relating to you in our server (warnings, mutes, kicks, bans, and the staff member and reason attached to each).
Roblox and in-game data
- Your Roblox username and user ID, if you have linked your Roblox account to Discord through Bloxlink. We read this link; we do not create it and cannot see your Roblox password or account details.
- Whether you are currently connected to our ER:LC private server, read from the ER:LC private server API.
Staff and roleplay records
- Staff rank, promotions, demotions, transfers and blacklists.
- Shift and quota data (via Melonly).
- Support ticket records and ticket transcripts.
- Applications, suggestions, bug reports and internal staff requests you submit.
Website data
- Our public website does not provide staff login or staff administration pages.
- Our host, Cloudflare, processes standard request information (such as IP address) to serve and protect the site. We use Cloudflare Web Analytics on the public site for aggregated visit counts. It does not use advertising cookies and is not used to build a profile of you for ads.
3. Message content
Our bots use Discord's Message Content privileged intent. We want to be specific about what that means in practice, because "the bot can read messages" sounds broader than what we actually do.
Message content is read in these situations:
- Text-to-speech relay. When TTS is enabled in a voice channel, messages typed in the linked text channel are converted to speech and played in that voice channel. The text is used to generate audio and then discarded. It is not saved.
- Prefix commands. Messages that start with our command prefix are parsed so the command can run.
- Ticket transcripts. When a support ticket is closed, the messages inside that ticket are compiled into a transcript file, posted to a private staff channel inside Discord and sent to you by direct message. The transcript is not uploaded to our database or any server outside Discord.
- Bug reports and suggestions. Content posted in our internal bug-report and suggestion channels is read so it can be tracked and triaged.
- Utility lookups. Certain staff commands read a referenced message to pull out a case number or a timestamp.
What we do not do: we do not log, archive, or store the content of ordinary messages sent in our server. No message content is stored outside Discord. Nothing in our database contains the text of your messages — it holds only structured records such as user IDs, case numbers, staff-written reasons and timestamps.
You can opt out. Run /privacy in our Discord server to:
- stop the bot reading your messages for text-to-speech;
- have your messages left out of saved ticket transcripts;
- turn off the automated triage described in section 7.
See section 9 for the full list.
4. Why we use it
We use this data only to run the community.
We do not use your data for advertising, profiling, or anything unrelated to running this community.
5. Where it is stored
Data that needs to persist is stored in a hosted Turso (libSQL) database that our bots and website share. The website itself is hosted on Cloudflare.
Everything we store is encrypted at rest, and data moving between our systems is protected in transit.
- Turso encrypts database storage at rest as part of its SOC 2 controls.
- Cloudflare encrypts the storage backing our website.
- Data in transit between Discord, our bots, our database and the website is sent over TLS.
- Requests between the website and our bots are cryptographically signed.
Access to the database and staff tooling is limited to Jackson County Roleplay leadership and developers who need it to do their role.
Our services may store and process data on servers located outside your country, including in the United States.
6. Third parties
We share data with the following services only to the extent needed to make a feature work. We do not sell your data to anyone.
Each of these providers handles data under its own privacy policy. We may also disclose data in either of these cases:
- We are legally required to.
- It is necessary to protect the safety of our community.
7. Automated processing
Our internal staff bot sends the text of bug reports posted in our staff bug-report channels to Google's Gemini API, which generates an automated first-pass reply to help the development team triage the issue.
This applies to staff bug reports only. Ordinary member messages, tickets and TTS text are not sent to any AI service.
This data is used for live inference — generating a single reply — and is not used by us to train or fine-tune any machine learning model.
8. How long we keep it
Different records are kept for different lengths of time.
- Moderation and staff records are kept for as long as they are useful for community safety, appeals and audit — in practice, indefinitely unless you ask us to remove them and we are able to.
- Ticket transcripts stay in a private Discord channel for record-keeping and dispute resolution. We keep an index of which transcripts you appear in purely so that we can find and delete them if you ask us to.
- Role and rank history is kept while you are a member and for a period afterwards for audit purposes.
- TTS text is not stored at all.
- Login sessions expire on their own and are cleared when you log out.
Leaving the Discord server does not automatically erase records already created about you. If you want them removed, see the next section.
9. Your choices and deletion
You can limit what the bot records about you, and you can ask us to see, correct, or delete your data.
Opting out yourself
Run /privacy in our Discord server at any time to see and change what the bot records about you. You control these individually:
Opting out takes effect immediately and applies going forward. It does not erase anything already saved — for that, make a deletion request below.
What you cannot opt out of:
- moderation cases;
- blacklists;
- ban-appeal outcomes;
- staff rank and shift records.
These exist so that punishments cannot be evaded and so appeals can be reviewed fairly, and switching them off would make the community unsafe to run. They are still covered by the deletion request process below.
Access, correction and deletion
You can ask us to:
- tell you what data we hold about you;
- correct data that is wrong;
- delete data we hold about you.
To make a request, open a Management Support ticket in our Discord server at discord.gg/jcrp, or use the request form in section 14 if you cannot reach us there. Either way we confirm your identity through your Discord account first, and respond within a reasonable time, normally 30 days.
Deletion works like this:
- A built-in tool that only the Ownership Team and bot developers can run carries it out.
- It scans every table in our database for records about you and removes them.
- It deletes any ticket transcript you appear in — the whole transcript message, its attachment and any related DM copy — from Discord.
- Before anything is removed, the person actioning it is shown exactly what will be deleted and what will be kept, and has to confirm.
What we keep even after a deletion request:
- moderation cases;
- warnings;
- strikes;
- bans;
- blacklists;
- ban-appeal outcomes.
Removing these would let someone erase a punishment and rejoin, so they are permanent and the deletion tool cannot touch them. We also keep records where you were the staff member who took an action against someone else, because those are records about that other person, not about you.
Every deletion is written to an audit log recording who ran it, for whom, when, and how much was removed. If you ask, we will tell you your deletion reference and what was kept.
You can also limit what we see at any time by:
- leaving our Discord server;
- unlinking your Roblox account in Bloxlink;
- adjusting your Discord privacy and status settings.
10. Age requirements
Our Services are used through Discord and Roblox, and you must meet Discord's minimum age requirement for your country — at least 13 years old, or older where local law requires it.
We do not knowingly collect data from anyone under that age. If we learn that we hold data about someone below the minimum age, we will remove their data and their access to our Services. If you believe a child's data is held by us, contact us using the method in section 13.
11. Security
These are the steps we take to protect stored data and limit who can reach it.
- All stored data is encrypted at rest and all traffic between our systems uses TLS, as described in section 5.
- Access to our database, hosting and bot credentials is limited to a small number of trusted developers and leadership.
- Staff panel actions require Discord login and are restricted by role.
- Requests between the website and our bots are signed.
No system is perfectly secure. We cannot guarantee absolute security, but if a breach affects your data we will notify the community promptly through our Discord server.
12. Changes to this policy
We may update this policy as our features change.
- The "Last updated" date at the top of this page will always reflect the current version.
- Material changes will be announced in our Discord server.
- Continuing to use the Services after a change means you accept the updated policy.
13. Contact
For any question about this policy, or to make a data request, open a Management Support ticket in the Jackson County Roleplay Discord server: discord.gg/jcrp.
This is the fastest and most reliable way to reach the people who can actually action your request.
Use the form below instead if:
- you have been banned;
- you have left the server;
- you cannot open a ticket for any other reason.
It requires signing in with Discord to prove the request is yours, but it does not require you to be a member of our server.
14. Request form (no server membership needed)
Use this if you cannot reach us on Discord. Requests go straight to our leadership team, and we reply within 30 days. You do not need to be a member of our server.
Signing in with Discord is required to use this form. Without it we have no way to tell whether a request is genuinely yours, and we are not willing to delete somebody's records — or hand over a list of what we hold about them — on the word of an anonymous form. Requiring sign-in protects you from someone else erasing or requesting your data.
Signing in works even if you are banned from our server or have left it — you are logging in to Discord, not joining anything. We receive only your user ID and username. We get no access to:
- your account;
- your messages;
- your servers;
- your email.
The sign-in is valid for 15 minutes for this request alone.
If you genuinely cannot sign in — for example your Discord account has been deleted — open a Management Support ticket, or have someone contact us on your behalf, and we will arrange another way to confirm your identity.
Submitting this does not delete anything on its own — it opens a request that a member of our leadership team reviews and actions. Moderation records described in section 9 are kept regardless of how the request reaches us.
We record the request itself so we can act on it and prove afterwards that we did:
- your Discord ID;
- what you asked for;
- any contact details you add;
- the reference number.
That record is kept as part of our deletion audit trail described in section 9.
Questions about your data?
Open a Management Support ticket in our Discord and a member of leadership will handle it. We would rather answer a question than have you guess.