Security at Descall

How Descall protects chats and calls, encryption in transit, account security, and honest limits.

Transport encryption (not default E2E)

Web and API traffic use HTTPS/TLS. Real-time media uses WebRTC with DTLS/SRTP between peers when a call is established. Descall does not claim default end-to-end encryption for all message history stored on the server, messages are encrypted in transit and stored to deliver chat history to your devices.

Voice & video

Call media is transmitted with WebRTC security (DTLS/SRTP). Descall never records or stores call audio, video, or screen shares. If a participant records locally, that is outside Descall's control.

Accounts

Passwords are hashed with bcrypt. Optional email 2FA and Google sign-in are available. Session management lets you revoke devices.

Report an issue

Email [email protected] or open an issue on GitHub. Include enough detail for a safe investigation.