Documentation

Security & Encryption

Guides for setting up and getting the most out of TetherDroid.

Security & Encryption

TetherDroid is built so that your private conversations, calls, notifications, and screen stay yours — visible only on your own paired devices, and to no one in between, including us. This page explains, at a high level, how that works and why we designed it the way we did.

  1. The short version
  2. End-to-end encryption
  3. Why we can't see your content — even in flight
  4. Pairing: keys that never leave your devices
  5. Why we drive the phone through automation (RCS, not SMS)
  6. What stays on your devices

The short version

End-to-end encryption

TetherDroid uses end-to-end encryption (E2EE). That means content is encrypted on the device that sends it and can only be decrypted on the other device you paired — the two endpoints. Nothing readable exists anywhere in between.

Under the hood we use AES‑256 in GCM mode, an industry-standard authenticated-encryption algorithm. "Authenticated" means the encryption also protects against tampering: if data were altered in transit, the receiving device would detect it and reject it rather than trust it. Every message, notification, screen frame, audio packet, and control command is encrypted this way before it ever leaves the device.

Why we can't see your content — even in flight

Your two devices don't connect directly to each other; they connect through a lightweight TetherDroid relay so they can find and reach each other from anywhere. But the relay is deliberately built to be blind:

The same holds for anyone else in the network path between your devices: they'd see only unreadable ciphertext.

Pairing: keys that never leave your devices

When you pair your phone with your desktop, TetherDroid shows a one-time pairing code (as a code and QR) that you confirm on the phone. That out-of-band step is what lets both devices independently derive the same shared encryption key — combining that pairing secret with a per-account secret.

Crucially, the key itself is never transmitted through our servers. It is computed on each device, so the full key exists only on your phone and your desktop. Even during pairing, an observer watching the network never sees the key — only the two endpoints ever possess it.

Why we drive the phone through automation (RCS, not SMS)

TetherDroid interacts with your messages by securely automating Google Messages on your own phone — reading the conversation that's on screen and sending on your behalf — rather than intercepting or re-sending raw SMS the way many "text from your computer" tools do. This is a deliberate security choice:

The result is the best of both: the convenience of texting and calling from your computer, without trading away the security your phone's RCS messaging already gives you.

What stays on your devices

Have a security question or concern? Contact Us.