Privacy

What CLS OS is

CLS OS is the web dashboard used to configure and operate the CLS Discord bot and its platform services. Discord server permissions (server owner, Administrator, or Manage Server) can make you eligible to start installing CLS in a server, but a server is only activated after the CLS owner approves it, and dashboard access stays controlled by CLS. The first person to set up an approved server may receive administrator access for it; anyone whose access the CLS owner revokes cannot regain it by repeating setup.

This page describes how CLS works today. It is not legal advice.

Discord sign-in for the dashboard

Normal dashboard authentication uses Discord OAuth with the scopes identify and guilds.

• identify — Discord user ID, username, and avatar for session display and operator identity.
• guilds — the list of Discord servers you belong to, used for access checks (which servers you may open in the dashboard).

After sign-in, the backend creates a dashboard session tied to that Discord identity so API requests can be authorized. Sessions can be revoked.

Optional Recovery Authorization

Separately from normal dashboard sign-in, CLS may offer an optional Recovery Authorization flow that requests Discord OAuth scopes identify and guilds.join.

• It is optional and is not required to use the dashboard.
• It is separate from normal dashboard sign-in (`identify` + `guilds`).
• Its purpose is bounded member recovery into a replacement or recovery guild when that product path is used.
• Authorization can be revoked by the member (from the recovery status page, or under Discord Settings, Authorized Apps) and by operators according to product controls. When it is revoked in CLS, CLS asks Discord to revoke the authorization and deletes its stored copy once Discord confirms. If Discord cannot be reached, CLS stops using the authorization immediately and shows the revocation as pending until it is retried.
• Dashboard sign-in and Recovery Authorization use the same CLS Discord application, so removing CLS under Discord Authorized Apps revokes Discord's tokens for both.
• Recovery is not guaranteed. Discord, permissions, hierarchy, and operational gates can prevent a restore.
• Sensitive authorization material is protected by the Recovery Vault. This page does not describe or expose implementation secrets or cryptographic material.

Discord content the bot processes

The bot reads server activity only for features a server has turned on, and keeps only what that feature needs. It does not sell data, build profiles across servers, or send usage telemetry to third parties.

• Logging: when a server enables logging, CLS records server events (joins, leaves, role and channel changes, moderation actions). To show what an edited or deleted message said, it keeps recent message content for 30 days; event records are kept for 90 days.
• Automod and anti-phishing: messages are checked against the server's rules as they arrive. Only a short excerpt of a message that breaks a rule is kept, as evidence for the server's moderators.
• Tickets: messages in a ticket channel, the answers a member gives when opening a ticket, and any rating they choose to leave are stored so staff can handle the ticket and keep a transcript. Staff notes are visible to staff only.
• Security: server structure changes (for example role and channel deletions) and the audit log entry that caused them are recorded to detect and investigate attacks.
• Access requests: if you ask for dashboard access, CLS stores your Discord ID, display name, and the servers you suggested, so the CLS owner can review it.

Other information we process

• Configuration data: Settings you save (moderation, tickets, welcome, roles, logging, automod, and similar module configuration) for Discord servers you are authorized to manage.
• Operational records: Dashboard changes may be audited; security incidents, logging events, and platform backups may store operational metadata needed to run CLS.
• Backups: Platform backup (when configured) may include database and configured store contents. Structure snapshots capture Discord server structure for recovery workflows: roles, channels and their permissions, the ban list (user IDs), and which roles each member holds (user and role IDs). Config Transfer exports selected module configuration only — not vault secrets, OAuth grants, or live recovery state.

Retention and contact

Retention periods depend on server configuration and operational backups. For access or deletion questions, contact the CLS owner. Discord's own privacy policy applies to your Discord account.