What 'operator-decryptable' means (and why it isn't end-to-end)

HIIE encrypts your data with strong, server-side keys, but it's important to be precise about the trust model: this is operator-decryptable encryption, not zero-knowledge or end-to-end encryption.

What operator-decryptable means

HIIE uses envelope encryption. A server-only master key (the KEK) derives per-project and per-folder keys, and the server decrypts your data just in time to serve a request. The KEK lives only on the server — it's never sent to the browser and never bundled into client code. The internal name for this is the "Camelia-blind guarantee," which specifically means the key never reaches the browser. It does not mean HIIE or its operators are technically unable to decrypt your data.

Why it isn't end-to-end

In end-to-end or zero-knowledge encryption, only you hold the keys, and the service provider cannot read your content even in principle. That is not how HIIE works. Because the server holds the KEK and decrypts on your behalf, the operator can technically access plaintext when serving requests. We are transparent about this so you can make informed decisions about what you store.

What you still get

This model still provides meaningful protection: AES-GCM encryption at rest, a distinct key per project/folder, keys that never leave the server, fail-closed behavior if the master key is missing, and per-user data isolation. Sensitive values like bring-your-own keys and project secrets are encrypted and never returned to the browser.

The takeaway

Treat HIIE's encryption as a strong at-rest and key-isolation guarantee, not as a promise that no one at the operator can ever read your data. For policy commitments on data use, see our article on data not being sold or used to train third-party models.