Privacy Policy
Eclipse is a Discord bot and web dashboard that helps run Emergency Response: Liberty County (ER:LC) communities. This policy explains what we collect, why, who we share it with, and the choices you have. We have tried to keep it plain and specific to what Eclipse actually does.
1. Who we are
"Eclipse", "we" and "us" mean the team behind the Eclipse bot and the website at eclipsecore.net. Eclipse is an independent project. It is not affiliated with, endorsed by, or sponsored by Roblox Corporation, Police Roleplay Community (the makers of ER:LC), or Discord.
2. What we collect
When you log in with Discord
The dashboard uses Discord OAuth with the identify and guilds scopes. From Discord we receive your user ID, display name and avatar, and the list of servers you are in. We do not receive your email address, your messages, or your password. We store your user ID; the ID, name and icon of the servers where you are the owner or have the Administrator or Manage Server permission, so you can choose which one to attach a plan to; and just the IDs of the other servers you are in, so the staff panel can find the ones that use Eclipse. That information is refreshed each time you log in. When you open the staff panel, Eclipse asks Discord which roles you have in that server to decide what you can do.
Your plan and settings
We store your plan (its owner, the modules on it, and the server it is bound to), the settings you choose in the dashboard (such as channel and role IDs, on/off switches, and any custom message wording), and any embed templates you save.
Your ER:LC server key
To read and run your in-game server, Eclipse needs your ER:LC server key. We encrypt it with AES-256-GCM before it is stored, and the dashboard never displays it again. We send it only to the ER:LC API, to carry out the features you turn on.
Data created by Eclipse features
When a server uses the Utilities module, Eclipse keeps the records those features need:
| Feature | What is stored |
|---|---|
| Sessions | Which Discord user started and ended a session, and when. |
| Votes | The vote topic and threshold, who started it, and the Discord IDs of members who voted. |
| Mod logs | The in-game player name, command text and timestamp from your ER:LC command logs. |
| Shifts | Discord user IDs, clock-in and clock-out times, and any time added, taken or deleted by a manager, with the reason and who did it. |
| Tickets | The ticket number, which ticket button was used, the opener's Discord ID, their answers to the form, who claimed it, its channel, status and timestamps. |
| Leave of absence | The member's Discord ID, the reason and length they gave, who approved or denied it, and the dates. Eclipse adds and removes the leave role you choose. |
| Moderation logs (panel) | For each warn, kick, ban, ban BOLO or note: the player's Roblox username, the reason, any evidence link, the length of a ban, and the Discord ID of the staff member who created it. |
| Staff requests | The Discord ID of the person asking, what they wrote, where, and who claimed or closed the request. |
| Ranks | The ranks you set up, the Discord roles they use, and the quota hours. Eclipse reads a member's roles when they press a button, to decide what they can do. |
Ticket transcripts. When a ticket is closed and a log channel is set, Eclipse reads up to the latest 1,000 messages in that ticket channel and posts them as a text file to your log channel. The transcript is delivered to your Discord server, and we do not keep a copy in our database.
What Eclipse does not read. Eclipse does not use any privileged Discord intents. It responds to slash commands, buttons and forms, and does not read or store the general chat in your server.
When you contact support
The support form collects your name, email address, topic, optional server name or ID, and your message. We also store a shortened one-way hash of your IP address, which we use only to limit repeated or abusive submissions. If email notifications are enabled, we send you a confirmation and your message passes through our email provider. Please do not put your server key, bot token or passwords in a message.
Technical data
Our hosting provider receives standard request information (such as IP address and browser type) when you visit the site, and may keep it in short-lived logs for security and reliability.
3. How we use it
- To run Eclipse: log you in, bind a plan to your server, post panels and messages, and run the features you enable.
- To keep the service secure, prevent abuse, and enforce one plan per server.
- To answer your support requests.
- To fix bugs and keep the service reliable.
We do not sell your data, we do not show ads, and we do not use your data to train AI models.
4. Who we share it with
We share data only with the services needed to run Eclipse, and with others only where the law requires.
- Discord: for login, and to send and manage the messages, channels and roles Eclipse uses in your server.
- ER:LC (Police Roleplay Community): your server key and the requests needed to read your server's data and run commands in it.
- Vercel: hosts the website and dashboard.
- MongoDB Atlas: hosts our database.
- Resend: sends support emails, when email is enabled.
- Google Fonts: our pages load fonts from Google, which means your browser contacts Google when you visit.
- Legal and safety: where we are required by law, or need to protect the rights, safety or security of Eclipse or others.
Inside your Discord server, features such as mod logs, shift leaderboards, vote results and ticket transcripts are shown to the members and staff you have allowed through your channel and role settings. Those people can see that information.
5. How long we keep it
- Login session: seven days, unless you log out sooner.
- Mod log records: 14 days, then they are deleted automatically.
- Plan, settings and feature records: while your plan is active.
- Support requests: as long as needed to resolve your request and handle follow-ups.
If you ask us to delete your data, or your plan ends, we will delete the associated records within 30 days, except where we must keep something for legal or security reasons. Ordinary backups roll off on the provider's normal schedule.
6. Cookies
We use only the cookies needed for login, and no advertising or analytics cookies.
eclipse_session: keeps you logged in for up to seven days. It is HttpOnly and signed so it cannot be altered.eclipse_state: a random value that protects the Discord login from forgery. It expires after ten minutes.
7. Security
Server keys are encrypted at rest. Logins use HttpOnly, signed cookies, and requests that change data are protected against cross-site request forgery. Every plan action checks that you own that plan. No system is perfectly secure, so we cannot guarantee absolute security. If you believe your account or key has been exposed, regenerate your ER:LC server key and contact us.
8. Your choices
You can ask us to give you a copy of your data, correct it, or delete it. You can also remove Eclipse from your server at any time, and revoke its access to your Discord account in Discord under Settings, Authorized Apps. Depending on where you live (for example, the EU, UK or California), you may have additional legal rights, and we will honor them. To make a request, email eclipsesupport@eclipsecore.net. We may need to confirm it is really you before acting.
Eclipse is operated from the United States, so your data may be processed there or wherever our providers operate.
9. For server owners
If you add Eclipse to a server, you decide what it records and who can see it. Please tell your members what Eclipse logs, such as shift times, vote participation, ER:LC command logs and ticket transcripts, and make sure you have the right to share that information with us. You are responsible for how your staff use the data Eclipse posts in your server.
10. Children
Eclipse is not directed at children. You must meet Discord's minimum age (13, or higher where your local law requires) to use it. If you believe a child has given us personal data, contact us and we will delete it.
11. Changes
We may update this policy as Eclipse changes, for example when paid modules launch. We will change the effective date above, and for significant changes we will post a notice on the dashboard or in our Discord. Continuing to use Eclipse after a change means you accept the updated policy.
12. Contact
Questions or requests about your data: eclipsesupport@eclipsecore.net, or use the support page.