Learn about end-to-end encrypted remote video, device identity checks and access controls.
End-to-end encrypted remote video (E2EE)
Remote video is encrypted on the host PC and decrypted on the connecting device. The two devices derive video encryption keys through X25519 key exchange and protect video with AES-128-GCM or ChaCha20-Poly1305. The service backend does not relay or store video, and connection authorization information alone cannot derive the video encryption keys. Account, permission and connection diagnostic metadata is processed separately to operate the service.
How device identity is verified
On the first connection, the app trusts and stores the host's public-key fingerprint received from the server or local network. Later connections to the same computer are blocked if the fingerprint changes. Initial device verification relies on that source. A legitimate change, such as reinstalling the host, also requires resetting the stored trust information.
Account protection
Accounts use email verification and optional OTP. With OTP enabled, sign-in checks your password before accepting an OTP code through a single-use verification step.
Computer access
The server checks the computer's owner, sharing permissions and organization roles. Organization features require a valid Teams or Enterprise license.
Direct connectivity
Screen, audio and input travel directly between devices. A network that blocks direct communication may prevent a connection. Test on the network you will use before a business rollout.
Business security and support requirements
SSO and SCIM integrations, SOC 2 certification and SLAs are not part of the standard offering. Discuss any support, data retention or security requirements before signing a contract.
Report a vulnerability
Contact support with the affected version and steps to reproduce the issue. Do not include other users' data or secret keys. Quote your inquiry reference when following up.