Cloud Storage
Storage where the client encrypts before upload. The claims differ in scope, and audits are the evidence.
4 zero KYC
Privacy, evidence, and risk are separate. See the published method.
Change ranking
Choose how to order services. Scores do not change.
How to choose
The storage listings encrypt files on the client before upload, so the operator stores ciphertext it holds no keys for, and each allows signup with only an email address. What differs is scope and evidence: whether filenames and folder structure are encrypted along with contents, whether the client code is open to inspection, and whether independent audits have tested the claims.
Real client-side encryption has a hard consequence: a lost password is lost data, because the provider has no key to reset with. Features that soften that, such as account recovery or link sharing, work by weakening the property somewhere, and where each provider makes that trade is worth reading on its record. Jurisdiction is recorded for every listing.
- What the encryption covers: contents, names, folder structure, and shares.
- The audit record, and whether the clients are open source.
- The recovery model, which reveals whether the provider can reach the data.
- Jurisdiction.
Frequently Asked Questions
What does zero-knowledge storage mean?
The provider stores ciphertext and holds no keys to it. The practical test is password recovery: a provider that can restore access to files after a lost password holds a key path to them.
Can the provider reset a lost password?
With client-side encryption, resetting the password without losing data is only possible where the provider keeps a recovery path. Each record notes the recovery model.
Are shared files still encrypted?
Share links typically carry the key material, so anyone holding the link can read the file. How links are constructed and whether they can be scoped or expired differs per provider.