01 / 03
We cannot read your files.
Files are encrypted on your device with keys we never see. What lands on our servers is opaque ciphertext.
Security
Security you
can check.
02 / 03
We cannot recover your password.
If you lose your password and your recovery phrase, your data is gone. By design — the alternative is a backdoor. Which we don’t offer.
03 / 03
We comply with valid legal requests.
When legally compelled, we hand over what we have. What we have is ciphertext. Nothing decryptable.
This page describes what Beebeeb does, how, and where we draw the line. It does not describe what we hope to do. Last reviewed: 06 May 2026.
Go deeper
The evidence, one page at a time.
- How the encryption works The upload in eight steps, every primitive named, keys, your login, sharing, and what changed.
- What we protect against, and what we do not The threat model, including the parts we cannot defend.
- If someone asks us for your data Our law enforcement guidelines: who may ask, how, and what we can and cannot hand over.
- Read the code Every repository, and how to verify a release.
- Found a problem? Tell us first How to report a vulnerability.
Infrastructure
EU-based.
Today, and by design.
Where your encrypted data physically sits matters even when the data is ciphertext. Jurisdiction determines which laws govern any request for it.
Today
In production
Stored in the EU (data centers in Germany and Finland)
All ciphertext lives in data centers in Germany and Finland, inside the EU. The Netherlands is coming soon. No data is replicated outside the EU.
In testing
Not yet live
Beebeeb-operated EU storage
We’re building our own storage fleet in EU datacenters. Because we value the trust customers place in us, we will only migrate to it after extensive redundancy testing and proven operational maturity. We will document the move when it happens.
Jurisdiction
EU law applies
Beebeeb is established in the Netherlands. Our processing is governed by the GDPR and Dutch implementing law. We do not transfer personal data to non-adequate jurisdictions.
Data we can see
Metadata only
Account email · billing details · masked IP addresses · file size · upload timestamp · owner · share recipients (when applicable). We see no filenames (those are encrypted), no file contents, and no folder structure beyond what’s required to render your file list.
Data we cannot see
Files, filenames, keys
File contents are AES-256-GCM ciphertext. Filenames are encrypted with the same per-file key. Your master key, your password, and your recovery phrase never reach us in any form.
Legal compulsion
What we’ll do when asked.
We don’t pretend to be above the law. We just made sure the law can’t extract what we don’t have.
We comply with valid legal requests from competent authorities in the Netherlands and the EU, and from foreign authorities through a valid legal assistance route. We do not comply with requests that lack a legal basis.
The full procedure, with what we can and cannot provide, is in our law enforcement guidelines.
When we receive a valid request, we hand over what we have:
- Account email, billing records, and IP addresses we have logged
- Encrypted file blobs (ciphertext)
- Storage metadata: amount of data stored, number of files, upload and modification timestamps, and share recipients where files are shared
- Encrypted file names and metadata, as stored (ciphertext, not readable)
What we do not have, and therefore cannot hand over:
- Decrypted file contents
- File names, folder structures and other metadata, insofar as they are encrypted on your device
- Your master key, password, or recovery phrase
- Any means by which we could decrypt the ciphertext
If we’re asked to add a backdoor:
we will refuse, contest it through every legal avenue, and — if
ultimately compelled — disclose it publicly to the extent the law allows.
No ongoing user can be silently downgraded.
Verifiability
Read the code yourself.
Every piece of software that handles your encryption keys is open source. If we said one thing on this page and shipped another, the code would show it.
core Rust Cryptographic core, shared types, sync engine github.com/beebeeb-io/core → web TypeScript Web client — encrypted file management in your browser github.com/beebeeb-io/web → cli Rust bb — your vault from the terminal github.com/beebeeb-io/cli →
How to verify a release
- Clone the repo at the commit SHA listed on the release page.
-
Read
core/src/— everything that touches your keys is in there. About 12,600 lines. - Build the client locally and compare its behaviour to what this page describes. The only data leaving your machine should be ciphertext, the wrapped per-file key, and OPAQUE protocol messages.
- Use a network proxy to confirm. We’d rather you verify than trust.
On audits: we have not yet had a third-party
cryptographic audit. Our clients are open source so anyone can review them today.
We will publish audit results here when we have them.
Responsible disclosure
Found something?
Tell us first.
If you’ve found a vulnerability in our clients, our protocol, or our infrastructure, we want to hear about it before anyone else does.
Beebeeb does not currently run a paid public program, and we do not yet make response-time commitments. We will use your report to investigate and coordinate any needed fix. A fuller policy is coming; see responsible disclosure.
Common questions
Straight answers.
What is zero-knowledge encryption?
Zero-knowledge encryption means the provider cannot read your data. Your files are encrypted on your device with a key only you hold, before they ever reach the server. Beebeeb stores ciphertext and never receives the key — so we cannot decrypt your files, by design.
Can Beebeeb read my files?
No. Files are encrypted on your device with AES-256-GCM before upload, using a master key derived from your 12-word recovery phrase and unlocked by your password. We never receive that key, so we hold only ciphertext. No engineer, admin or founder at Beebeeb can read them.
What happens to my files if Beebeeb is breached?
A breach of our servers only exposes ciphertext and limited metadata — file size, timestamps, owner. The decryption keys never touch our infrastructure, so an attacker who steals the entire database still cannot read a single file.
What can Beebeeb hand over to law enforcement?
Only what we have: encrypted blobs we cannot decrypt, plus metadata such as your email, billing details, file sizes and timestamps. We cannot produce file contents or filenames, because they are encrypted with keys we never hold.
What if I lose my password and recovery phrase?
Your data becomes permanently inaccessible. There is no backdoor and no master key on our side — the recovery phrase is the master secret. We cannot reset it for you. That is the cost of encryption only you can unlock.
Encryption you can verify.
14-day free trial. No card or iDEAL needed to start. Zero-knowledge from the first byte. Read the code, then decide.
Start a 14-day trial