Recipient-keyed sharing means files are encrypted for the people you choose — not for the server that moves them.
“Secure collaboration shouldn't require lowering the confidentiality bar.”
For teams, studios, legal counsel, agencies and partnerships exchanging confidential material.
Files are wrapped under each recipient's public key. The server transports sealed material it cannot open.
No 'anyone with the URL' tier. Access is granted to identified recipients only.
Revoking a share is a key-rotation event, not just a permission flip on a server that already saw the content.
Shared documents are not rendered on our infrastructure. Recipients decrypt locally.
Every grant, revocation and access event is logged — without exposing the contents of the file.
Same model on web, desktop and mobile, in 11 languages.
Most cloud sharing relies on server-readable URLs and permission tables tied to plaintext. That makes sharing easy and the provider a participant in every exchange. Private collaboration means designing the share so the provider is a transport, not a participant.
No surprise widening of audiences. No silent server-side rendering. No 'company-wide' tier that quietly grants access to people you did not name. Just clear, identified, auditable grants.
No. Files are encrypted on your device before upload using XChaCha20-Poly1305. DRIVUNO servers only ever store ciphertext. The keys required to decrypt your files are derived from your password on your device and never leave it unencrypted.
Zero-knowledge is an architecture in which the service provider has no technical ability to access user data. With DRIVUNO, your master key is derived locally from your password using Argon2id. The server never sees that key, so it cannot decrypt your files even if compelled to.
DRIVUNO uses a different architecture. Google Drive, Dropbox and similar consumer clouds hold the encryption keys to your files, which means their staff, automated systems, and any party with legal access can in principle read your content. DRIVUNO is designed so that this is technically not possible on our side.
Because we cannot read your data, we also cannot reset it for you. You can configure a recovery key when creating your account. We strongly recommend storing it offline. Without your password or recovery key, encrypted data cannot be recovered — by design.
Start free with 2 GB. Zero-knowledge encryption from the first upload — no admin override, no AI scanning, no plaintext on the server.
