How the Swell Protocol works
Last updated 13 November 2026 · Swell by PT JIJI LABS DIGITAL
The short version: Swell is made on the Swell Protocol, our own end-to-end encryption with a post-quantum key exchange. Only the phones in a chat can read its messages. The protocol is open source under Apache-2.0.
What it does
- Your keys are your account. Your phone makes them when you open Swell. There is no phone number, no email and no account server. Twelve recovery words, shown only to you, bring the keys back on a new phone.
- Messages, files, groups and backups are encrypted on your phone before they leave it, and can be opened only on the phones of the people in the chat.
- The first key agreement is post-quantum. It combines a classical exchange (X25519) with a post-quantum one (ML-KEM-768), so a message recorded today stays protected even if quantum computers can later break the classical part alone.
- Each chat keeps renewing its keys. The protocol uses a Double Ratchet with encrypted headers, and a post-quantum ratchet renewed inside each chat, so a key taken at one moment does not open the rest of the chat.
- You can check who you are talking to. A safety number and a Contact Mark, a picture made from both keys, let two people compare what each phone holds. The Contact Mark is a quick look. For a full check, compare the safety number.
The building blocks
| Primitive | What Swell uses it for |
|---|---|
| X25519 | Classical key agreement between two phones. |
| ML-KEM-768 | Post-quantum key agreement, combined with X25519. |
| HKDF-SHA-256 | Turns the shared secrets into separate message and header keys. |
| AES-256-GCM | Encrypts and authenticates messages and files. |
| Ed25519 | Signatures. |
| TLS 1.3 with a pinned key | The connection between your phone and the Swell server. It is a second layer and does not replace the end-to-end encryption. |
On iPhone these come from Apple CryptoKit and the open-source Swell Protocol library. The other parts of the app are listed on Source code and licences.
What the server can and cannot see
It can see
- Your IP address while you are connected. It keeps it in memory only and writes no access log.
- A random mailbox address for each chat, with no name in it.
- How many sealed messages are waiting, their sealed size, and when each arrived.
It cannot see
- What any message, photo or file says.
- Your name, your photo or your contacts.
- The name of whoever sent a message.
A sealed message waits for up to 14 days and is then deleted. You can check this yourself in the app: tap the time under any message to open its Message Trail, or open your mark at top left, then What the server sees. The full policy is on the Privacy Policy.
Open source
The Swell Protocol library is open source under the Apache License 2.0. Licences and credits for the rest of the software are on Source code and licences.
Limits
- Nobody can stop the other person from photographing their screen or sharing what you sent.
- If you lose both your phone and your twelve words, your account cannot be restored. We do not have your keys.
Status
The protocol has had internal reviews and formal models, which we describe as our own work and not as outside proof.
Questions or a security finding: support@jijilabsdigital.com.