CBSE.CLUB

Security

How we keep your boards safe

No security claim is worth much without specifics, so here are ours.

Accounts and sign-in

  • Optional two-factor authentication with any authenticator app (TOTP), plus ten single-use recovery codes.
  • Account owners can require two-factor sign-in for everyone in the account.
  • Passwords are stored with a modern, slow password-hashing algorithm, never in plain text.
  • Repeated failed sign-ins trigger rate limits and temporary lockouts.
  • You can see your active sessions and sign out other devices. You get an email when your password or email address changes.

Access to data

  • Boards can be open to the whole account or limited to chosen people. Cards on boards you cannot access never appear in search, filters, notifications or the API.
  • Personal API tokens can be read-only or read-write and can be revoked at any time. They are stored only as hashes.
  • Our staff tools show account-level information such as account size. They do not show card contents.

Application security

  • HTTPS everywhere, with HSTS.
  • A strict Content-Security-Policy, plus protections against clickjacking, MIME sniffing and cross-site request forgery.
  • All rich text is cleaned on the server with an allowlist before it is stored.
  • The platform accepts no file uploads, so there are no stored attachments or profile photos to leak.
  • Outgoing webhooks are signed with HMAC-SHA256 and cannot be pointed at private network addresses.
  • Secrets such as webhook keys and two-factor seeds are encrypted at rest.

Your data

  • Export your whole account at any time.
  • Cancelled accounts become read-only, can be restored for 30 days, and are then permanently deleted.
  • We do not sell your board contents, and we do not use them to train AI.

Reporting a problem

If you believe you have found a security issue, please report it privately rather than posting it publicly, and give us a reasonable time to fix it before disclosure.