On your device
SWELL makes a new random key for this transfer and encrypts the file with AES-256-GCM. It locks that key to the recipient with ML-KEM-1024 and signs the transfer with your ML-DSA-87 key. The file name is sealed too.
Home / Security
Every transfer is locked on your device, travels locked, and is opened only on the device it was sent to. Here is exactly how, what our relay can and can't see, and what we don't claim.
Algorithms
SWELL uses the algorithms in the NSA's Commercial National Security Algorithm Suite 2.0, including the two post-quantum standards NIST published in 2024.
| Algorithm | Standard | What SWELL uses it for |
|---|---|---|
| ML-KEM-1024 | FIPS 203 | Delivering each transfer's key. Every transfer gets a fresh random key, locked to the recipient's post-quantum public key, so only their device can unlock it. |
| ML-DSA-87 | FIPS 204 | Signing. The sender signs each transfer's description (its manifest), so the recipient knows who sent it and that nothing was swapped. |
| AES-256-GCM | FIPS 197, SP 800-38D | Encrypting the file itself, piece by piece. Each piece is authenticated, so a changed byte is caught. |
| SHA-384 | FIPS 180-4 | Fingerprints of files and pieces, and the Swell Spatial Signature. Keys are derived with HKDF-SHA-384 and checked with HMAC-SHA-384. |
What this does and doesn't mean. SWELL uses the CNSA 2.0 algorithm suite. That describes the algorithms we chose. SWELL has not been certified, validated or approved under CNSA 2.0, FIPS 140 or any other program, and we don't claim compliance with them.
A transfer, step by step
SWELL makes a new random key for this transfer and encrypts the file with AES-256-GCM. It locks that key to the recipient with ML-KEM-1024 and signs the transfer with your ML-DSA-87 key. The file name is sealed too.
The locked pieces go straight to the other device when you're both reachable on the same network, or through the relay. Either way, only locked data travels.
The recipient's app checks your signature and every piece's fingerprint, unlocks the key, and rebuilds the file. Then it sends back proof (Landfall), and your app marks it delivered.
Saving a file locally, without sending it, works too: you lock it with a passphrase or a 64-character key of your own.
The relay
The relay is a drop box for locked pieces, run by WiredLogix on Cloudflare. It never has the keys. We'd rather tell you exactly what it does see than say "nothing".
Clears itself
Relay storage deletes a transfer's pieces one day after they were last written. Senders can delete a transfer sooner.
Receipts
Delivery proofs are opaque codes that only the sender's app can check. The relay keeps them for up to 30 days.
Direct
On the same network, devices connect to each other directly and the file doesn't need to touch the relay.
The browser app
Web apps usually trust whatever the server sends today. SWELL's browser app doesn't.
What we've tested
We state what was tested and how, not more.
Three implementations
The Apple apps, the Android core and the Windows core are written separately and checked against the same frozen test vectors, so a mistake in one shows up as a mismatch.
Windows
The Windows core passed 29 of 29 tests. Received files of 100 MiB matched the originals byte for byte, on a Mac test harness and on a Windows 11 test machine, against our live relay (November 2026).
Reviews
Every place the code uses cryptography is listed with its purpose and status, with every finding from our repeated internal review rounds and how it was resolved.
Limits
Found a security problem? Please tell us at support@wiredlogix.com with "SWELL security" in the subject. We read every report.