Security
The short version. The full model, including its gaps, is in the source repository.
Not independently audited. The message protocol is Signal's own libsignal. What skwod builds around it (the key directory, device linking, key backup, call keys, the peer-to-peer transport) is our own work, and nobody outside the project has reviewed it. If your safety depends on a messenger, use Signal.
What is encrypted
Direct messages, channels, files, the feed and stories, and voice and video calls are encrypted end to end, on your devices. skwod uses libsignal for this: post-quantum session setup (PQXDH), the Double Ratchet, Sender Keys for channels, sealed sender for direct traffic, and safety numbers to verify a contact. A call does not connect unless its keys could be set up.
What the server can see
The server is treated as untrusted, even though someone in your group owns it. It holds ciphertext and public keys. It does know the group's shape: who the members are, which channels exist, who posted in a channel and when, reactions, read states and presence, and the network addresses that connect to it. It never has message content or private keys.
What we can see
We run no chat servers, so there is nothing of yours for us to hold. Three things do leave your device toward services outside your group:
- Update checks. The Mac and Android apps check a public release feed on GitHub once a day. GitHub sees an IP address and that the device runs skwod. You can turn this off in the app. An update installs only if it carries our signature.
- Relays. When two devices cannot connect directly, traffic goes through an independent relay, which sees that two addresses are talking and nothing of what is said. A host can forbid relays.
- iPhone notifications. If a build has push turned on, a gateway is told only "wake this device". It learns no sender, no skwod and no content.
Invite links and this website
An invite is https://skwod.io/join#<server key>.<code>. Everything
after the # is a URL fragment, which browsers do not send to servers, so this site never
receives the key or the code. The join page reads it in your browser and hands it to the
app. The key in the link is also the server's identity: the connection fails unless the
other end holds the matching private key. See Privacy for what the
site itself does.
Why there is no web app
A website that serves the encryption code can serve different code to one person, once, and nobody would notice. So skwod exists only as installed apps with signed updates, and this site serves no code that touches your messages.
Read the details, report a problem
- The full model and "Remaining gaps versus Signal": docs/SECURITY.md
- The source code: https://github.com/FlayrLabs/skwod
- Found a vulnerability? Please report it privately to security@skwod.io, not in a public issue.
The source repository opens at launch. Until then these links may not work.