Encryption protects the content of your conversations between authorized devices. Understanding your devices and the information the service still needs is just as important.
01
Messages encrypted between devices
Synapse uses the Signal Protocol through libsignal: PQXDH key agreement, which adds Kyber1024 post-quantum key encapsulation, and the Double Ratchet. Each device has its own messaging sessions and prekeys.
Messages are encrypted before they leave your device. Attachments are encrypted separately, with their decryption keys shared inside encrypted messages. History backups are encrypted on your device with a backup key before upload. The service stores only the encrypted data; it does not receive message content, attachment keys or the backup key in readable form.
02
A phone approves your browser
The browser displays a short-lived QR code. Scan it with Synapse on your signed-in Android phone, check the request and approve it. Only the browser that created the request can complete the sign-in.
Account encryption identity is transferred in a sealed exchange; the server relays ciphertext rather than plaintext private keys. Only approve browsers you recognize, and remove devices you no longer use.
03
Check who you are talking to
Compare a contact’s safety number through another trusted channel. It helps you confirm the encryption identity behind a conversation. The apps only encrypt for a contact’s device whose identity key matches that contact’s account key, so a device added to the account without the account key receives nothing.
An encryption identity reset changes the safety number. If you lose every authorized device, a reset can restore account use, but it does not recover the old encrypted history.
04
Encrypted calls, checked by your devices
Voice and video use WebRTC with DTLS-SRTP encryption. Devices connect directly when possible; a TURN relay can carry encrypted media when network restrictions prevent a direct connection. Relaying encrypted media does not give the relay the keys to the call.
Call setup, including each device’s DTLS fingerprint, passes through the service. After each setup exchange, the devices send each other these fingerprints over the end-to-end encrypted Signal session and compare them. A mismatch ends that connection. A connection that is not confirmed within 10 seconds is marked as unverified and continues, unless the service is set to end such calls.
05
Content privacy is not zero metadata
The service still handles account and device identifiers, message addressing, timestamps and delivery status, as well as group membership, reaction emoji, call records and connection information. IP addresses in call records are removed after 30 days.
End-to-end encryption protects message content. It does not hide every relationship or activity detail from the service.
06
Your device is part of the protection
Android keeps its data in a SQLCipher-encrypted local database and protects the database key with Android Keystore. The browser keeps its encryption state and history in IndexedDB, encrypted with an AES-256-GCM key that the browser creates as non-extractable. Signing out of the browser deletes this local data.
Use a trusted, updated browser and a protected device. Scripts running in the app’s browser origin, and anyone using your unlocked browser profile, can still have that data decrypted. Clearing browser storage may remove local keys and history.
Know the device you approve.
Open Synapse Web on a trusted computer, then confirm the QR request on your phone.