Zero Knowledge: How We Secure Your Data Without Ever Seeing It
The most secure database in the world is one where the admins have lost the password.
That is essentially how EnvShareApp works.
We call this "Zero Knowledge Architecture". It means that while we store your data, we have mathematically proven that we cannot read it.
The "Blind Courier" Analogy
Imagine you want to send a diamond to your friend, but you have to use a courier service you don't fully trust (that's us, the server).
- Standard Security: You put the diamond in a box. You give the courier the box and the key. You ask them, "Please don't open it." (This is how most websites work).
- Zero Knowledge: You put the diamond in a virtually indestructible titanium safe. You lock it. You keep the key. You give the courier the locked safe only.
The courier (EnvShareApp) transports the safe. We can weigh it, measure it, and store it. But without the key, we cannot see the diamond.
How It Works Technically (The "Hash Fragment")
The magic trick of Zero Knowledge on the web lies in the URL Hash Fragment (the part after the #).
When you create a secret:
- Generation: Your browser generates a random encryption key.
- Encryption: Your browser uses
AES-256-GCMto encrypt your file using that key. - Upload: You send only the encrypted blob to EnvShareApp.
- Display: We construct the URL and append the key
#keylocally in your browser url bar.
We (the server) see the blob. We never see the key.
Why This Matters
Trust is good. Math is better.
Data Breach Proof
If hackers dump our database, they get useless ciphertext.
Privacy Preserving
Not even EnvShareApp employees can read your secrets (we technically can't).
You Own the Key
The URL *is* the key. If you lose the URL, the data is gone forever.
Verification
You don't have to take our word for it. Our cryptography code is client-side javascript. You can inspect the network traffic in Chrome DevTools. You will see that the payload sent to `/api/secrets` is unreadable garbage, and the `key` is never in the request body.
The One Exception (Metadata)
While we can't read the content, we do need to store some unencrypted metadata to make the service work:
- Expiry time (so we know when to delete it)
- View count (so we know when to burn it)
Conclusion
Zero Knowledge isn't just a marketing term for us. It's the core engineering constraint of the entire platform.
Use EnvShareApp knowing that your secrets are mathematically yours, and yours alone.