Consultancies hold competitors' strategies at the same time. Cryptographic separation per engagement is the only honest way to promise isolation.
“Two competing clients, two sets of keys, zero overlap.”
For management, technical and creative consultancies, agencies and independent advisers under nda.
Keys are sealed per member per engagement, so access does not spread across the firm by default.
Removing a freelancer revokes access and rotates remaining envelopes, with an audit entry.
Send a report with expiry, passphrase and watermark instead of a permanent email attachment.
Give a client an encrypted channel rather than a shared consumer messaging group.
Draft deliverables in encrypted documents instead of a suite that indexes everything you write.
An access record you can show when a client asks how their material was handled.
Most consultancies sign strict NDAs and then store the material in a suite where every employee account, every integration and the provider itself can technically read it. The contract says one thing; the architecture says another. Per-engagement encryption closes that gap.
External collaborators are normal in consulting and are also the most common source of lingering access. Invite them into a single engagement space, and remove them the day the statement of work ends — rotation makes that removal meaningful rather than cosmetic.
Being able to say that your provider cannot read the client's data is a differentiator in competitive processes, particularly with legal, healthcare and public-sector buyers who will ask the question anyway.
You can export the append-only access trail for their engagement, showing grants, revocations and share events without exposing content.
Yes. Multi-gigabyte video and design files upload in resumable chunks and can be shared with watermarked, expiring links.
No. Everything is encrypted on the device before it is uploaded, 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.
No. There is nothing to self-host and no key server to operate. You create an account, invite colleagues and clients by email, and the encryption happens transparently in the browser, desktop and mobile apps.
We do not currently hold SOC 2 or ISO 27001 certification, and we say so publicly rather than implying otherwise. Our compliance page documents where we are, what is in progress, and what is planned. What we can demonstrate today is the architecture itself: client-side encryption, per-member key envelopes and an append-only audit trail.
Removing a member revokes access and rotates the remaining key envelopes, so an old copy of a key stops opening anything new. Every membership change, share creation and revocation is written to an append-only log.
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 be stored offline. That is the same property that stops anyone else, including us, from reading the account.
Yes. The free plan includes 1 GB with exactly the same zero-knowledge architecture as paid plans, so you can validate a real client workflow before committing.
Start free with 1 GB. Zero-knowledge encryption from the first upload — no admin override, no AI scanning, no plaintext on the server.
