Security
What Lokot is built to protect, what it cannot protect, and where it stands today.
Where it stands
Lokot is being built. The encryption core exists and has tests. The apps are not finished, and nothing has been checked by independent security experts yet. Until an audit report is published, the app will say so plainly.
What it is built to protect
Messages are encrypted from end to end. Lokot uses MLS, an open standard, with a lock made for quantum computers on top of the classic one, so an attacker has to break both.
The servers hold no accounts, no names and no phone numbers. A message for someone who is offline waits in a sealed envelope that we cannot open.
The private side opens only with your drive, your code and your own device together. Every session gets new encryption keys, and they are destroyed when the drive comes out.
What it cannot protect
A phone that is already infected. Whatever shows on its screen can be read.
What the other person does with what you sent, for example a photo of the screen.
An invite link that someone swapped on its way to you.
A changed version of the app, if we were broken into or forced and nobody noticed. Public code, and builds that anyone can compare, are the answer to that.
A mistake in our code. That is what the audit and the bug bounty are for.
Someone who has your phone, your drive and your code together.
A copied drive, in one case. A flash drive can be copied without you noticing. Someone who copies it, and then also gets your phone and your code before you next unlock, gets in. After your next unlock that copy is dead.
The network. It can see that your phone talks to our servers, and when.
How it is made
The code is written with an AI assistant, with a person directing and deciding. We say so because a privacy product that hid how it was built would be caught, and would deserve it. It is one more reason the code is public and the audit matters.
The code and the audit
The code of the apps, the core and the server will be published when the open beta starts, under a licence that keeps copies open as well. A bug bounty opens at the same time.
The audit starts as soon as it can be paid for. Its full report will be published, together with our answer to every finding.
Reporting a problem
If you find a weakness in this site, or later in the app, please write to security@lokot.io before you tell anyone else, and give us a fair amount of time to fix it. We will answer.
We will not take legal steps against anyone who reports in good faith, does only what is needed to show the problem, and does not look at or keep other people's data.