Security: how RoamTerm protects your terminal

Last updated:

RoamTerm gives a phone access to a shell on your computer, so security is the point of the product, not an add-on. These are the principles it is built on.

End-to-end encrypted by design

Your session is SSH between your phone and your computer. Both sides connect outward over port 443 to a relay that pairs them. The relay forwards encrypted bytes and cannot read your commands, output or files. When the network allows it, the two sides connect directly and the relay is not in the path.

Identity is pinned by the QR code

When you pair, the QR code carries your computer’s host key fingerprint. The phone checks it on every connection, so nobody can sit in the middle and pose as your computer.

Keys live in hardware

Your phone’s SSH key is created in the Secure Enclave on iPhone or StrongBox on Android where available, as an ECDSA P-256 key. It never leaves the device. Opening a session can require Face ID or a fingerprint.

An account is not access

Signing in to RoamTerm never grants access to a machine. Only a phone that you paired with a computer can connect to it.

You stay in control on the computer

The agent shows incoming connections, can ask for your approval and lets you revoke a device at any time. It runs in your own user session, not as a system service with extra privileges.

AI access is opt-in

If you connect an AI agent through MCP, access is switched on per device, a persistent banner shows while it is active and one tap cuts it. An action log records what the agent did.

ADB stays on localhost

Remote ADB is tunneled to localhost on your computer and is never exposed to the internet or your network. It has an auto-off timer and a visible notification.

Updates are signed

The desktop agent updates itself only with signed releases that it verifies before installing.

Review and reporting

An independent security review is planned before public launch. If you find a vulnerability, write to [email protected] with the subject “Security”; see the support page.