1. About this policy
This policy explains how Commandly handles information when you use its ER:LC community and server-management tools. “Commandly,” “we,” and “us” refer to the operator of commandly.space. Privacy questions and requests can be submitted through the official Commandly Discord support ticket channel.
Commandly is independent and is not affiliated with or endorsed by Roblox Corporation, Police Roleplay Community, or the creators of ER:LC.
2. Information we handle
Roblox account information
When you sign in with Roblox, Commandly requests the OpenID profile scopes and receives your Roblox account ID, username, display name, profile URL, and avatar URL. Commandly does not receive your Roblox password.
Server and membership information
When a server is connected or joined, Commandly handles its name, invite code, owner/member roles, Roblox IDs, and usernames. The connecting owner’s ER:LC server API key is stored server-side so the app can request authorized server data. Do not share that key with people who should not manage the server.
ER:LC information
When a connected server is viewed, Commandly requests live information from the ER:LC API. Depending on the feature and API response, this may include player names and Roblox IDs, teams, callsigns, permissions, locations or postal codes, wanted-star counts, and emergency-call caller, description, team, time, number, and position. Live player and call responses are used to render the dashboard. When a user joins an emergency call on the dashboard, Commandly stores that responder’s Roblox ID, username, callsign, team, and join time in the server’s roster.
Settings and content
Commandly stores server-specific jurisdiction names, team names, and map boundary points. It also stores Premium entitlement status associated with a Roblox ID. Preview servers contain sample information and are marked as templates.
Technical and support information
The hosting environment and infrastructure providers may process IP address, request, browser, and diagnostic information to deliver and protect the website. If you contact support through Discord, Discord processes your ticket and the information you choose to include under its own policies. Commandly does not use Discord for sign-in.
3. How information is used
- To authenticate your Roblox account and maintain your signed-in session.
- To connect authorized ER:LC servers and provide live player, map, jurisdiction, and emergency-call features.
- To maintain server membership, invite access, responder rosters, and Premium entitlements.
- To protect the service, diagnose errors, prevent abuse, and respond to support requests.
- To meet applicable legal obligations and enforce the Commandly Terms of Service.
Where privacy law requires a legal basis, the basis may include providing a feature you request, our legitimate interests in operating and securing Commandly, compliance with law, or your consent for optional storage or technologies.
4. Storage and service providers
Commandly’s backend is designed to store server, membership, jurisdiction, responder-roster, and Premium records in Supabase. The database is accessed from the server using a secret key; it must never be exposed in browser code. Supabase and the hosting provider may process data in the regions where their infrastructure operates.
Roblox provides authentication, and ER:LC’s API provides connected game-server information. These providers process information under their own terms and privacy policies. We do not currently use advertising networks, analytics providers, Discord OAuth, voice recording, or Stripe payments.
Commandly currently does not accept real-money payments. A future Robux game-pass and manual Premium-grant process is planned; if introduced, the relevant Roblox transaction and support information will be handled as described before that feature is offered.
6. Retention
The session cookie expires after its stated lifetime or when the session is destroyed. Server configuration, memberships, jurisdiction boundaries, Premium records, and responder rosters remain stored until they are changed or removed. The current version does not apply an automatic deletion schedule to these records. Live ER:LC player and emergency-call data is fetched for display and is not intended to be retained as a historical game-data archive; responder roster entries are retained until the responder leaves or the record is otherwise removed.
Some diagnostic or infrastructure logs may be retained by the hosting provider for its operational and security purposes. Retention periods depend on the provider and deployment configuration.
7. Disclosure and transfers
We do not sell personal information or use it for cross-context behavioral advertising. Information may be processed by Roblox, ER:LC API infrastructure, Supabase, website hosting providers, or Discord when you contact support. We may also disclose information when required by law, to protect users or the service, or to establish or defend legal claims.
These providers may operate in different countries. Where applicable law requires safeguards for international transfers, the service operator should configure and document those safeguards with the relevant providers.
8. Your choices and requests
You can change optional-cookie consent using Cookie settings. You can stop using a connected ER:LC feature by disconnecting the server where that option is available. To ask about access, correction, or deletion of information, submit a privacy request through the official Commandly Discord support ticket channel and identify the Roblox account involved. We may need to verify your identity before acting and may retain information where required for security, legal obligations, disputes, or abuse prevention.
Your rights depend on where you live and may include access, correction, deletion, restriction, objection, portability, or withdrawal of consent. You may also have the right to complain to your local data-protection authority.
9. Children and account eligibility
Use Commandly only if you meet the minimum age and consent requirements that apply to you and follow Roblox’s age requirements. If you believe a child has provided information contrary to applicable requirements, contact Commandly through the support channel so the request can be reviewed.
10. Security and updates
We use server-side access controls and reasonable safeguards appropriate to the service, but no internet transmission or storage system can be guaranteed completely secure. Do not send passwords or server API keys in a support ticket.
We may update this policy as features or providers change. The date at the top will be revised when material changes are made. Check this page periodically.