Partition by partner, not by convenience
The most common structural mistake is one shared folder for all externals. Separate encrypted spaces per partner limit blast radius and make attribution possible when something surfaces publicly.
Pipeline
Encrypted file sharing across the whole development pipeline.
Concept art, source assets, captures, localisation kits, milestone builds and design documents move between a dozen organisations before launch. Each hop is a chance to lose control.
“One encrypted pipeline instead of ten uncontrolled hand-offs.”
For studios working with outsourcing partners, publishers, localisation vendors, marketing agencies and platform holders.
Built for confidentiality
Heavy assets without pain
Source art, captures and packages transfer in resumable chunks with deduplication and verification.
Per-partner spaces
Give each partner their own drive or room with its own membership, so an outsourcing studio never sees the publisher's material.
Expiring protected links
Passphrase, expiry, view budget and revocation on every external hand-off.
Watermarked previews
Show work in a protected viewer that stamps context onto what is displayed.
Discussion next to the file
Feedback stays in the same encrypted workspace as the asset, instead of scattering across three chat products.
Versions and recovery
Version history and a 30-day trash mean an overwritten asset is not a crisis.
Return paths matter as much as delivery
Vendors send back captures, bug reports and localised builds. If the return path is personal email, the material has already left your control. Give every partner an encrypted upload destination.
Closing a partnership cleanly
At the end of an engagement, remove the partner's members: keys rotate, links can be revoked in bulk and the audit trail records the closure.
Frequently asked questions
Do partners need to install software?
+
No. Web access covers external collaborators; desktop and mobile apps are there for the people living in the workspace.
Can we enforce that links always expire?
+
Public links carry a maximum lifetime that cannot be extended indefinitely, so 'forever links' are not an option to begin with.
Can DRIVUNO read our messages, files or builds?
+
No. Everything is encrypted on the device before it leaves it, with XChaCha20-Poly1305, using keys derived locally with Argon2id and wrapped per member with X25519. Our servers hold ciphertext and sealed key envelopes, so there is no admin view, no support tool and no classifier that can reach your content.
Do we need a technical team to run it?
+
No. There is nothing to self-host and nothing to configure: you create an account, invite people by email, and encryption happens transparently in the browser and apps. Zero-knowledge here is the default, not an expert mode.
Is there a free plan?
+
Yes. The free plan includes 1 GB with exactly the same zero-knowledge architecture as paid plans, so you can validate the workflow before moving a studio onto it.
What happens if someone leaves the team?
+
Removing a member revokes their access and rotates the remaining key envelopes, so their old copy of the key stops opening anything new. Every membership change is written to an append-only audit trail.
What if we lose a password?
+
Because we cannot read your data, we cannot reset it for you. Each account creates a Recovery Kit — a printable PDF with a QR code — to keep offline. That is the same property that stops anyone else, including us, from reading your workspace.
Related
Your sensitive files deserve more than a traditional cloud.
Start free with 1 GB. Zero-knowledge encryption from the first upload — no admin override, no AI scanning, no plaintext on the server.