Don't trust us. Read it.

Where the code is

The repository opens to the public at launch. This page will link it the same day.

One repository holds the Rust encryption core, the iPhone app, and this website in site/, so you can check that the site tracks nothing too.

Review history

Every round of review the encryption core has been through is kept in the repository under docs/reviews/: what each reviewer found, the evidence, and how each finding was handled. It goes public with the code, and each release names the exact commit it was built from. No independent audit firm is booked yet; this page will name it when one is.

The license

GPL-3.0. You may read, run, change and share the code. If you ship a modified version, you share your changes under the same terms. Nobody, including us, can take it closed.

How to verify a build

Reading the source is half the job. The other half is knowing the app on your phone was built from it. Oorvel's builds are reproducible: the same source, built the same way, produces the same binary.

1. Check out the tag for the version you have installed. Every release in the changelog names its tag.
2. Build it with the pinned toolchain in the repository's build instructions.
3. Compare your build's hash with the hash published for that release.

App Store distribution adds Apple's signing and encryption on top of the binary, so the comparison is made on the unsigned build. The repository documents each step, and where Apple's tooling limits what can be checked, it says so.

This website

The site you are reading is static HTML. It sets no cookies and loads nothing from any other domain. Every build runs a check that fails if the output would make your browser contact any host but this one. The only time your browser leaves this site is when you choose to tap a link.