Skip to content

The Everabyte encryption model

Everabyte's zero-knowledge model encrypts files on your device before upload, with local decryption, a recovery passphrase and an additional storage-level layer.

Everabyte protects your files with zero-knowledge, client-side encryption plus an additional storage-level layer. This article explains how the model works and what it means for you.

In short

Your device encrypts files before upload, and Everabyte stores ciphertext without the keys needed to decrypt file contents. Decryption takes place on your authorized devices. A second storage-level layer protects the stored ciphertext.

What happens to a file

  1. Your authorized device encrypts the file and its name locally with AES-256-GCM.
  2. The encrypted file is sent over a TLS 1.3 connection.
  3. Everabyte stores ciphertext and applies an additional storage-level encryption layer at rest.
  4. An authorized device downloads and decrypts the file locally; Everabyte cannot read the file contents.

Master key management

Everabyte protects infrastructure master keys through secure Vault-based key management. These storage-layer keys do not decrypt your zero-knowledge file contents; those keys remain on authorized devices and are protected by your recovery setup.

Owner-controlled decryption

Your zero-knowledge keys remain under your control. Everabyte receives ciphertext, not the file decryption keys or plaintext content. Authorized clients perform encryption and decryption locally.

Recovery passphrases

Your recovery passphrase helps you restore access to your zero-knowledge keys on an authorized device. Keep it secure, never share it, and store it separately from your devices.

Zero-knowledge and end-to-end protection

Everabyte encrypts files on your device before upload and does not hold the keys needed to decrypt their contents. The platform stores ciphertext; authorized clients decrypt locally. File content remains protected end to end between your authorized devices. For a plain-language tour of these terms, see Zero-knowledge and encryption models explained.

The same model everywhere

This encryption model applies across Everabyte’s standard storage platform, including white-label deployments. If a dedicated environment or custom module changes the cryptographic flow, the applicable configuration is stated in your order form or DPA.

Important — Keep your account credentials and your recovery passphrase safe. See Lost encryption key or recovery passphrase and How to protect your recovery passphrase.

Common issues

Is Everabyte zero-knowledge?

Yes. File encryption and decryption happen on authorized client devices. Everabyte stores ciphertext and does not receive the file decryption keys.

Does the encryption apply to shared files?

Yes. Shared files remain encrypted client-side; authorized recipients decrypt locally with keys shared through the client workflow. The storage layer adds its own protection at rest. See our sharing best practices.

Can Everabyte read my files?

No. Everabyte’s zero-knowledge design keeps file decryption keys on authorized client devices, so the platform cannot decrypt or read file contents. We do not use file content for advertising, profiling or AI training. See Can Everabyte read files.

Where can I read about the security layers around it?

See How we protect your files for TLS 1.3, layered encryption, Vault-backed key management, retention controls and threat detection.

Still need help?

Can't find what you're looking for? Our support team can help.