Swell · Invite-only messenger

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

The building blocks

PrimitiveWhat Swell uses it for
X25519Classical key agreement between two phones.
ML-KEM-768Post-quantum key agreement, combined with X25519.
HKDF-SHA-256Turns the shared secrets into separate message and header keys.
AES-256-GCMEncrypts and authenticates messages and files.
Ed25519Signatures.
TLS 1.3 with a pinned keyThe 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

It cannot see

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

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.