Security

Encryption you can try for yourself.

Everhold is built so that we cannot read your data – not even if we wanted or were forced to. See live how it works.

Try it live

Type something – your browser encrypts it instantly

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.

What you see
Key (only in your browser)…
What our server sees
…
Nonce (IV)…
Key— never sent —
Key hierarchy

From passphrase to a single file

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.

Passphraseonly in your head
Argon2id64 MiB, 3 passes – slows attackers down
Key (KEK)opens the master key
Master key256 bit, random, stored wrapped
File keyone per file, wrapped with the master key
Encrypted fileAES-256-GCM, 32 MiB pieces

Recovery kit: 24 words also open the master key – in case you forget your passphrase.

The path of a file

Encrypted, stored several times, proven daily

On your devicesplit into pieces and encrypted individually
Fil One, EUS3 storage in eu-west-1 – ciphertext only
Filecoinbundled with two independent storage providers
Daily proofproviders prove cryptographically that everything is still there
Example: one new storage proof per day
Secure Send

The key lives in the link – and never reaches us

Browsers do not send the part after “#” to the server. Only someone with the full link can decrypt.

https://everhold.io/s/Xk2p9QmZ#k=Pq7vN2…eR4
Transparency

What we see – and what we don’t

What we see
  • Email or wallet address
  • Plan, storage usage, invoices
  • Number and size of encrypted blocks
  • Times of sign-ins and changes (audit log)
What we never see
  • File names and content
  • Passwords, notes, 2FA codes
  • Your passphrase and recovery kit
  • Keys of Secure Send links
Methods

What we use

AreaMethod
Files, passwords, notesAES-256-GCM, one key per file
Key from passphraseArgon2id (64 MiB, t = 3) + HKDF-SHA-256
RecoveryBIP-39 recovery kit (24 words, 256 bit)
Sharing in teamsECDH P-256 + HKDF + AES-GCM per person and generation
PasskeysWebAuthn; unlocking optional via PRF extension
TransportTLS 1.2+ with HSTS
Breach checkk-anonymity: only 5 characters of a SHA-1 hash
Responsible disclosure

Found a vulnerability?

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.