Privacy isn't a promise — it's architecture

Two ways to keep a secret There are two structurally different ways a cloud service can keep your data confidential.

The first is a promise: the provider commits — through policies, contracts, audits and culture — to behave well with your data. This is how most consumer clouds operate. It can be sincere, well-resourced, and effective. It is also, by construction, breakable. Policies change. Staff change. Legal contexts change.

The second is architecture: the system is built so that the provider has no technical ability to read your data. There is nothing to promise, because there is nothing to access.

Why the distinction matters A confidentiality model built on promises depends on every link of a long chain remaining trustworthy over time. A confidentiality model built on architecture depends only on the cryptography — which is public, widely reviewed, and does not change behind closed doors.

For a casual photo or a working document, a promise is usually enough. For an NDA file, a contract draft, a medical record or an identity paper, architecture is the right standard.

How to recognise architectural privacy Ask a single question: "If I forget my password, can you recover my files?" - If yes, the provider holds the keys. Confidentiality is a promise. - If no, the provider cannot decrypt your content. Confidentiality is architecture.

What DRIVUNO commits to Confidentiality at DRIVUNO is not a brand value. It is the system design. Files are encrypted on your device using XChaCha20-Poly1305. Keys are derived locally with Argon2id. Servers store only ciphertext and minimal metadata. There is no decryption path on our side — by design.

The honest trade-off Architectural privacy means we cannot reset your password for you. That is the price of a model that does not depend on our behaviour. We think it is the right price for files that matter.