Everhold is built so that we cannot read your data – not even if we wanted or were forced to. See live how it works.
Real AES-256-GCM encryption with a random key that exists only in this browser tab. This is exactly how your files and passwords are encrypted before upload.
……
…— never sent —On your device, your passphrase becomes a key that opens your master key. Every file has its own key. None of it leaves your device unencrypted.
Recovery kit: 24 words also open the master key – in case you forget your passphrase.
Browsers do not send the part after “#” to the server. Only someone with the full link can decrypt.
| Area | Method |
|---|---|
| Files, passwords, notes | AES-256-GCM, one key per file |
| Key from passphrase | Argon2id (64 MiB, t = 3) + HKDF-SHA-256 |
| Recovery | BIP-39 recovery kit (24 words, 256 bit) |
| Sharing in teams | ECDH P-256 + HKDF + AES-GCM per person and generation |
| Passkeys | WebAuthn; unlocking optional via PRF extension |
| Transport | TLS 1.2+ with HSTS |
| Breach check | k-anonymity: only 5 characters of a SHA-1 hash |
We welcome reports and treat every one confidentially. Please give us time to fix before publishing details. We will not take legal action against people testing in good faith without harming others.
In scope: everhold.io, the web app, the API and the storage API. Out of scope: social engineering, denial of service, third-party providers.
An independent security audit is planned; the report will be published here.