Everything you need to know.

No. Your password derives your master key, and we never have access to either. If you lose your password and your recovery phrase, your data is gone. This is the trade-off of zero-knowledge encryption: the security guarantee requires that no one -- including us -- can bypass it. Write down your recovery phrase and store it somewhere safe.

All client code is open source. You will always be able to export your encrypted vault from the web app or the CLI — open formats, no lock-in. Your data is yours, and it stays yours regardless of what happens to us.

No hard limit per file. Files are chunked and encrypted individually, so even large files (videos, disk images, archives) are handled efficiently. Your total storage is determined by your plan -- from 200 GB on Basic, scaling to 99 TB self-serve on paid plans (with a custom quote beyond that).

Web and CLI are available; native macOS, Windows, Linux, iOS, and Android apps are coming soon. The web app uses WebAssembly for client-side encryption; native apps use Rust bindings.

All four offer end-to-end encryption. The differences are in jurisdiction, transparency, and architecture. Beebeeb is EU-based (Dutch company, German and Dutch servers), fully open-source on the client side, and uses OPAQUE for authentication so your password never leaves your device in any form. We publish our infrastructure locations and comply with valid legal requests under Dutch and EU law — see our Law Enforcement Guidelines.

Yes. Team workspaces support shared folders with per-user key wrapping. Each team member has their own identity key pair, and folder keys are wrapped for each member individually using X25519 key exchange. Admins can manage members and rotate keys without re-encrypting stored data.