Recipient-keyed envelopes, encrypted folder trees and expiring public links — all built so we hold no key that opens your data.
“Share widely. Trust narrowly.”
For teams and individuals who share sensitive material regularly and want cryptographic, not administrative, access control.
Argon2id turns your passphrase into a master key locally. The server sees wrapped keys, never the master.
Each grant seals the content key to a specific X25519 public key, so access is provable and revocable.
Grant a whole encrypted folder, including future files, without exposing the rest of the vault.
Public shares put the decryption key in the URL fragment, which never reaches our infrastructure.
Blind-index HMAC tags let you find files by name without the server ever learning the name.
Primitives, threat model and limitations are published rather than summarised as 'bank-level security'.
It means our servers hold ciphertext and wrapped keys, and no process on our side can unwrap them. It does not mean we see nothing at all: we necessarily process account identifiers, membership, sizes and timestamps to operate the service. We publish exactly what that includes.
In a conventional cloud, permission is a row in a table; anyone who can edit that row can read the file. Here, permission is possession of a sealed key envelope. Editing a database row grants nothing readable.
If you lose your passphrase and your recovery key, your data is unrecoverable — that is the direct consequence of the design. Endpoint security remains your responsibility: an attacker with a fully compromised, unlocked device sees what you see.
No. Messages and files are encrypted on the device before they are sent. DRIVUNO Rooms seals every message with XChaCha20-Poly1305 under a room key that is itself wrapped per member with X25519. Servers relay and store ciphertext only.
Slack and Teams encrypt data in transit and at rest, but the provider holds the keys, so administrators, automated systems and legal requests can reach message content. DRIVUNO is designed so that this is technically impossible on our side: we never hold a key that opens your content.
Removing a member revokes their sealed copy of the room or folder key and triggers a key rotation, so future content is sealed under a key they never had.
Only what is strictly required to operate: account identifiers, membership, timestamps, sizes and security/audit logs. File and channel names are encrypted; search runs on blind indexes (HMAC tags), not on plaintext.
Yes. The free plan includes 1 GB with the exact same zero-knowledge architecture — encrypted drive, Rooms messaging and encrypted sharing.
Start free with 1 GB. Zero-knowledge encryption from the first upload — no admin override, no AI scanning, no plaintext on the server.
