Live proof

See exactly what our servers see.

Type any text on the left. It is encrypted on your device in real time, using the same crypto module our apps run. The right pane shows the opaque ciphertext — the only form in which DRIVUNO stores your content.

Your device (plaintext)stays here
58 chars · 62 bytes Never transmitted
XChaCha20-Poly1305
Our servers (ciphertext)—
Entropy: 0.00/8 What we store
Shown for illustration only — entropy on a small sample is not a cryptographic security test.
Try to break it
Flip a single byte of the ciphertext, then try to decrypt it. The Poly1305 authentication tag makes any modification detectable — decryption is refused outright instead of silently returning corrupted data.
A fresh random key is generated for every encryption
Your key is never sent to our servers. Without it, the ciphertext on the right is indistinguishable from random noise — recovering the plaintext is computationally infeasible with any realistic computing resources.
Nonce (24 bytes)
—
Symmetric key (32 bytes)local only
—
Authenticated encryption
Poly1305 MAC tags detect any tampering. A single flipped bit makes decryption fail safely.
Metadata minimisation
Filenames, sizes and timestamps are encrypted with the file payload — not stored in plaintext columns.
Isolation between shares
Each public link uses its own X25519 keypair, and the private key never leaves the URL fragment. Compromising one link cannot expose any other.
What this page demonstrates — and what it doesn't This demo calls the same production encryption functions (symEncrypt / symDecrypt from the DRIVUNO crypto module, XChaCha20-Poly1305-IETF) inside your browser. It demonstrates that this code encrypts locally without transmitting plaintext. The broader claim — that production always behaves this way — rests on the combination of this demo, the published crypto source, build-manifest fingerprints, network inspection and independent audits, not on this page alone.
How to verify our claims
We separate what you can check yourself, today, from what we document and assert. Both are listed below — deliberately in two groups.
Independently verifiable
  • Network inspection
    Open your browser's DevTools → Network while using the app: sync and upload requests carry only opaque ciphertext. Plaintext file content never appears in any request.
  • Share keys in the URL fragment
    Public share links carry the decryption key after the # character. Browsers never send the fragment to any server — you can watch this yourself in DevTools.
  • Open crypto module
    The crypto library our apps import is published with its source and known-answer tests, so anyone can audit the primitives line by line.
  • Build-manifest fingerprint
    Each deployment ships a manifest of file hashes. Your browser recomputes the fingerprint of the files it actually received, so you can detect a build that differs from the published manifest.
Documented by DRIVUNO
  • Sub-processors
    The infrastructure providers that store or relay ciphertext on our behalf, with their roles and locations.
  • Retention & deletion
    How long ciphertext, backups and logs are kept, and what happens when you delete content or close your account.
  • Data Processing Agreement
    The contractual framework that governs how we handle encrypted customer content for business accounts.
  • CI privacy gate
    Our CI pipeline blocks changes that would let plaintext content reach the network layer. The pipeline is not public, so treat this as our assertion — not something you can replay today.
This page runs entirely in your browser. Inspect network in DevTools to verify — no request carries your plaintext.
Sign inRegister
End-to-end encrypted