End-to-end encryption you can check
With RemoteBite, what happens in a session is only seen by the two computers. Not even our servers can decrypt it, and in every connection you can check that with an on-screen code.
How we protect every session
End-to-end encryption
Screen, keyboard, mouse, clipboard and files travel encrypted between both computers, also through the relay server.
Security code
Both computers show the same 6-digit code: if it matches, nobody is sitting in the middle.
Computer identity
Each computer has its own key. The app checks it's connecting to the right computer and not an impostor.
You decide
Whoever is at the computer accepts each connection and decides whether it can be controlled or just watched. They can end it at any time.
Protected accounts
Two-step verification, sign-in with an emailed code in the apps and per-person permissions on computers.
Logged sessions
The dashboard shows who connected, to which computer and when.
How the encryption works
Every computer has an X25519 identity key that never leaves it. When a session is requested, the app makes a temporary key and our API signs both that key and the target computer's key into the session permit, so nobody can swap them along the way.
With those keys, both computers agree on the session keys (a Noise-style exchange) and encrypt all traffic with ChaCha20-Poly1305. Because the keys are temporary, a past session stays protected even if a long-term key were leaked later (perfect forward secrecy).
The connection goes directly between both computers whenever the network allows it. If not, it goes through a relay server that only forwards encrypted data it can't read.
Short-lived permits
Every session is authorized with a signed token that expires in two minutes and that the target computer checks on its own. Connecting without acceptance is only allowed for your own account or for your organization's computers that have it turned on.
Privacy
RemoteBite is made in Europe. We don't see or store the contents of your sessions: we only log what's needed to run the service, such as which computers connect and when.
Frequently asked questions
Can RemoteBite see my sessions?
No. Sessions are end-to-end encrypted between both computers; our servers only see encrypted data.
What is the security code for?
Both computers derive it from the session keys. If it matches on both screens, you know nobody is sitting in the middle.
Can someone connect to my computer without permission?
No. Someone at the computer has to accept every connection, except for computers in your own account or in your organization with unattended access turned on.
Which encryption does RemoteBite use?
X25519 key exchange with temporary keys, HKDF-SHA256 key derivation and ChaCha20-Poly1305 encryption, with one key per direction.
Are the files I send encrypted too?
Yes. Files and the clipboard travel over the same end-to-end encrypted connection as the screen.
Can I turn on two-step verification?
Yes, in your account settings in the web dashboard.
Connect with peace of mind
Download RemoteBite and check the security code in your first session.