Zero-knowledge encryption means we can't access your files — not because of a privacy policy, but because of mathematics.
When you upload a file to Vaulternal, it's encrypted in your browser before it ever reaches our infrastructure. The encryption key is derived from your wallet — which only you control. We never receive, store, or have access to your plaintext files or encryption keys.
Every layer of the system is designed so that only the intended recipient — with the correct key — can read your data.
Your encrypted data is distributed across decentralized networks — no single company, server, or cloud provider can take it down.
Permanent Storage
Distributed Availability
Metadata Anchoring
Triggers automate delivery using double-layer encryption. The oracle can verify conditions but never access your files.
Files are decrypted entirely in the recipient's browser. At no point does Vaulternal, the oracle, or any third party have access to plaintext data.
Zero-knowledge architecture means there are things we are mathematically unable to do — even if compelled.
| We CAN do | We CANNOT do | |
|---|---|---|
| Files | Store and deliver encrypted files | Read or access your plaintext files |
| Keys | Generate wallet key pairs for you | Access your private key after creation |
| Triggers | Execute trigger logic when conditions are met | Override, bypass, or cancel triggered deliveries |
| Recovery | Provide keyfile and seed phrase recovery paths | Recover your data without your encryption key |
| Compliance | Respond to legal requests with account metadata | Decrypt your files for anyone, including authorities |
We build in the open. Here's what's shipped, what we're working on, and what's coming next.