Matters, not one giant shared drive. Client exchange, not email attachments. Encryption that happens on your device, not a promise printed in a security page.
“The file cabinet nobody outside the matter can open — including your cloud provider.”
For solo practitioners, boutique firms and in-house counsel who handle privileged and commercially sensitive documents daily.
One encrypted drive per matter or client, with keys sealed individually for each authorised person.
Your device computes blind indexes so the server matches opaque tags; the browser decrypts the hits. No server-side content index exists.
Internal discussion of a matter does not have to live in a chat product whose history the vendor can read.
Recover a previous draft or an accidentally deleted exhibit without asking a provider to restore plaintext.
Installable apps with an encrypted local cache, so a hearing room with bad signal is not a blocker.
Sign in with a passkey and hardware-backed device trust rather than a reusable password typed in public.
Every serious provider encrypts disks. The question that matters is who holds the key. If the provider does, then an internal tool, a compelled disclosure or a compromised administrator account can produce readable client documents. If only your devices do, none of those paths lead anywhere.
Explaining cloud use to a cautious client is simpler when the answer is architectural. You are not asking them to trust a vendor's staff policy; you are describing a system where the vendor never receives a decryption key in the first place, and where every access is logged.
Storage, internal chat, calls, client exchange links and password sharing in one encrypted place removes the copies that accumulate when a document travels between products. Fewer copies, fewer places to forget, fewer offboarding checklists.
No. Names and structure are encrypted as well, not just contents. What we necessarily see is operational metadata such as object sizes and timing, which we minimise and document.
Yes. Clients open a link, type a passphrase you gave them by another channel, and read or download. There is no software to install and no key to manage on their side.
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.
