Guides/Principle
Verifiable privacy: why you should be able to read the code
A privacy tool that asks for trust is asking for the wrong thing. A verifiable privacy tool lets you check what it does — either by reading the source or by watching the network. Elba is designed to be verified, not trusted.
Two things anyone can check
The source: open Elba.html in a text editor. Every function is there.
The network: open the browser's DevTools while you use it. The Network tab stays empty.
Why this matters more than a security certificate
Certificates say ‘someone checked this once’. Verifiability says ‘you can check it any time’. The second promise is the one that survives corporate turnover.
Questions people actually ask
- Do I need to be a developer to verify Elba?
- No. The network check takes ten seconds in any browser. Reading the source helps if you want to go further.
- What if the source is obfuscated?
- It isn't. Elba ships as readable JavaScript inside the HTML.
Take the island
Elba is one HTML file. It runs locally in a Chromium browser, seals a folder with AES-256-GCM, never phones home, and becomes open source on 1 January 2030.
- €49MMXXVI· now ·
- €39MMXXVII2027
- €29MMXXVIII2028
- €19MMXXIX2029
- FreeMMXXX2030
the price falls each year · free to all 1 jan 2030
pay once · no account · nothing leavesRelated guides
- How client-side encryption works, in one page
Client-side encryption means the key never leaves your device. Here's how it works, why it matters, and how Elba applies it.
- Zero-knowledge encryption, explained without jargon
Zero-knowledge means the service can't read your files even if it wanted to. Here's the idea, and how Elba goes one further.