Privacy starts before your file reaches the cloud.
Every file is encrypted on your device with XChaCha20-Poly1305 before it touches the network. The upload is ciphertext from byte one.
“The cloud should never have access to your files. With DRIVUNO, it doesn't.”
For professionals, studios, families and individuals who refuse to send plaintext to a server.
Built for confidentiality
Sealed on your device
Per-file keys are generated locally. The file is encrypted in chunks before any byte leaves your machine.
Keys you actually hold
Your master key is derived from your password with Argon2id, on your device. The server never sees it.
Ciphertext only on our servers
We store opaque encrypted blobs, wrapped keys and minimal metadata. There is nothing readable to scan.
No server-side analysis
No previews, no OCR, no AI features running on your plaintext. Encryption before upload makes them impossible.
Modern, audited primitives
XChaCha20-Poly1305, Argon2id, X25519, Ed25519 — via libsodium, widely reviewed and modern.
Streaming-friendly
Chunked authenticated encryption means large files stream and resume cleanly without weakening the model.
Three timings of encryption — only one is enough
Encryption at rest protects against stolen hardware. TLS protects against network eavesdroppers. Neither prevents the provider from reading your file once it lands on their servers. Only encryption before upload removes the provider from the trust chain — and that is the model DRIVUNO is built on.
What our servers actually receive
When you upload a file to DRIVUNO, the server receives an opaque ciphertext blob, a wrapped per-file key it cannot open, and minimal operational metadata. No filenames in clear inside the envelope, no thumbnails generated server-side, no content indexing. The cloud sees a blob — and that is the design.
Why this changes confidentiality
Confidentiality built on policy depends on the provider behaving well over time. Confidentiality built on encryption before upload depends only on the cryptography. The first model is breakable. The second is architectural.
Frequently asked questions
Can DRIVUNO read my files?
+
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.
What is zero-knowledge encryption?
+
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.
Is DRIVUNO safer than Google Drive or Dropbox?
+
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.
What happens if I lose my password?
+
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.