Secure file sharing is usually described as “end-to-end encrypted” or “privacy-first”.
Most platforms advertise things like:
- AES-256 encryption
- secure file transfer
- GDPR compliance
- privacy-focused infrastructure
These are meaningful practices, but in most cases the underlying model still relies on trust in the service provider.
In practice:
- encryption is often limited to transport (TLS)
- files may still be accessible server-side in some form
- and infrastructure-level guarantees are difficult to independently verify
So users are often relying on policy and assurances rather than strict technical constraints.
This raises a question:
What would secure file sharing look like if the provider could not access the data at all by design?
Not “we promise not to”.
But “we are technically unable to”.
I’ve been exploring this idea through a small open-source project called PrivCloud.
The goal is:
- client-side end-to-end encryption
- server never has access to encryption keys
- zero-knowledge design at the architecture level
While trying to keep usability simple:
- fast uploads, including large files
- browser-based usage
- no setup required
Repo: https://github.com/Simthem/PrivCloud_Sharing
Demo: https://share.privcloud.fr/
I’m mostly curious about the broader discussion:
Why do you think most file sharing systems still rely on trust-based models instead of strict zero-knowledge architectures?
Is it mainly usability, cost, or something else?