Security

Security at Desklia

We built Desklia with security as a first principle — not an afterthought. Here's exactly how we protect your applications and your data.

End-to-End Encrypted Streams

All screen and input data is transmitted via WebRTC with DTLS-SRTP encryption. This means your stream is encrypted directly between your machine and the viewer's browser — our servers never see the content of your sessions.

WebRTC DTLS-SRTP Peer-to-peer

Secure Authentication

Desklia uses Google OAuth 2.0 for user login — we never store passwords. Agent tokens are hashed with bcrypt before being stored in the database, and Personal Access Tokens (PATs) are used for agent registration rather than raw credentials.

Google OAuth 2.0 Bcrypt hashing JWT tokens

Rate Limiting & Abuse Prevention

Every endpoint is protected by rate limiting. Authentication attempts are tracked and throttled to prevent brute-force attacks. Connection limits per user prevent resource abuse.

Per-IP rate limiting Auth attempt tracking Connection limits

Transport Security

All web traffic is served over HTTPS with strict TLS. HTTP Strict Transport Security (HSTS) headers are enforced. Content Security Policy headers prevent XSS attacks by restricting which resources browsers can load.

HTTPS / TLS HSTS CSP headers

Your Data Stays Yours

Desklia operates on a peer-to-peer model. The content of your sessions — your screen, your keystrokes, your files — is never routed through or stored on our servers. We only store what's necessary to run your account: your email, subscription status, and session metadata.

Responsible Disclosure

Found a security vulnerability? We take all reports seriously. Please disclose responsibly by emailing us directly — we'll respond within 48 hours.

Report a vulnerability