Email attachments, fax bridges and consumer transfer services all create copies you cannot revoke. A protected link does the opposite.
“Every disclosure deliberate, time-boxed and recorded.”
For practices and health services sending records to patients, referring clinicians, insurers and legal representatives.
Passphrase, expiry, view budget and one-click revocation, with the key material carried in the URL fragment that never reaches our servers.
Optional per-recipient watermark for material that should be read rather than redistributed.
Creation, first use and revocation are logged, giving you an evidence trail for each disclosure.
The document is ciphertext before it leaves your device; the recipient's browser decrypts it locally.
Patients open a link and type a passphrase. Nothing to install, nothing to sign up for.
Links stop working on their own, so old disclosures do not accumulate indefinitely.
Once an attachment is sent, it exists on mail servers, in backups and in the recipient's client forever, and it cannot be withdrawn. It is also trivially misdirected by autocomplete. A revocable link with a separate passphrase turns a permanent broadcast into a controlled, reversible disclosure.
Use a different channel from the link itself — a phone call, an in-person handover, or an SMS if the link went by email. Splitting the two across channels is what makes interception of one channel insufficient.
For referrers you work with regularly, a shared encrypted drive with per-person keys is better than repeated links: access is continuous, revocation is instant, and the audit trail stays in one place.
Yes. Revocation stops further access immediately. It cannot recall a copy the recipient already downloaded, which is why view-only watermarked mode exists for the most sensitive material.
No. The key material lives in the URL fragment, which browsers never transmit to the server, and access is additionally gated by a passphrase.
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.
