End-to-end encryption, key recovery and signed updates, built in.
Security that is part of the design from the first day, not a feature added before launch.
Encrypted before it leaves the device.
Your data is encrypted on the device, with keys that are made there and stay there. Servers can store and pass on what they cannot read, so a breach of a server is not a breach of your data.
- End-to-end encryption. Data is encrypted before it is stored or sent. Servers hold only sealed envelopes.
- An encrypted local database. The copy on each device is encrypted at rest.
- Key recovery. A recovery kit, kept by you, brings your keys back when a device is lost. Losing a laptop does not mean losing your data.
- Signed updates. Every installer and update is signed, and the app checks the signature before it installs anything.
- Separated customers. On the server, each customer's records are fenced off at the database level.
Plain words, standard tools.
- Threat model. In plain words: what you protect, from whom, and what happens if a device is lost.
- Key design. A key hierarchy built from established, reviewed building blocks, such as the
ageencryption format. No home-made cryptography. - Recovery, tested. We test recovery from a lost device before launch, not after the first incident.
- Signed releases. Installers and updates are signed, and the signature is checked on every device.
Trust is part of the product.
- Your software handles personal, financial or confidential data.
- You want to be able to say, truthfully, that you cannot read your customers' data.
- Your users need to keep working, and keep their data, when a device is lost or stolen.
--- Questions
Can you read our data?
Not with end-to-end encryption. Our servers hold only encrypted envelopes, and the keys stay on your devices.
What if someone loses their device?
The recovery kit brings the keys back on a new device, and the data comes back from the other devices or from the encrypted copy.
Do you write your own cryptography?
No. We use established formats and libraries, and we spend our effort on how keys are made, stored and recovered.
Can you review the security of an existing app?
Yes, as part of an audit: keys, encryption, updates and where data is exposed, with a written plan to fix what we find.