Built from the ground up
for hostile environments.

All files are encrypted client-side using AES-256-GCM before they are transmitted to our servers. Your encryption keys never leave your device. We store only ciphertext.

Even if our servers were seized, the data would be mathematically useless without your key. We cannot decrypt your files. Law enforcement cannot compel us to decrypt your files. We simply do not have the keys.

Your vault is accessed via a Tor hidden service — a .onion address that routes traffic through the Tor anonymity network. This means your IP address is never revealed, even to our servers.

Tor hidden services also provide protection against server-side deanonymization. We cannot log your IP even if we wanted to, because Tor hidden services never receive the client's real IP address.

We use a zero-knowledge password protocol (SRP — Secure Remote Password). This means your password is never sent to our servers, even during login. We verify that you know your password without ever seeing it.

If our authentication database were compromised, an attacker would find no passwords — not even hashed ones they could crack. We simply don't store them.

We do not log IP addresses, connection times, access patterns, or file metadata. Our systems are configured to avoid generating logs in the first place — because logs that don't exist can't be subpoenaed.

This is not a policy we can be pressured to change retroactively. The architecture makes logging technically impractical for most sensitive data.

Our primary storage tier is air-gapped and offline during normal operations. Data is only accessible during brief, audited synchronization windows. This means that even a successful server compromise yields only stale, encrypted data.

Backups are encrypted with independent keys and stored in separate physical locations. A compromise of one location does not compromise your data.