Security
This page summarises the security model of SLChat. It describes how the service is designed, not a guarantee of absolute security.
Encryption
Messages and attachments are end-to-end encrypted on users’ devices. The relay forwards ciphertext and stores encrypted attachments; it does not hold decryption keys. Keys are held on devices, rotated when membership changes, and can be verified through safety numbers.
Accounts and access
Access requires an authenticated account. Workspaces support single sign-on, role-based permissions, device management and administrative audit logs. Administrators manage membership, retention and policy, but do not receive decryption keys for room content.
Infrastructure
Traffic is protected with TLS; stored data is encrypted at rest; production access follows least privilege and is logged. We apply security updates and review dependency and configuration risks.
Reporting a vulnerability
If you believe you have found a security issue, contact info@k2a.pro with the subject “Security”. Please include enough detail to reproduce the issue and do not access, modify or disclose other users’ data.
Last updated: 5 November 2026.