VaultProtocol Documentation
Official documentation for the VaultProtocol platform – a Zero-Knowledge end-to-end encrypted vault management system. Learn how to integrate, build, and extend using our API.
What is VaultProtocol?
VaultProtocol is a privacy-first platform built from the ground up on a Zero-Knowledge Architecture. This means our servers are entirely blind to the contents of your data. All encryption and decryption happens exclusively on the client's device.
Core Technology Stack
| Layer | Technology | Purpose |
|---|---|---|
| Framework | SvelteKit (Svelte 5 Runes) | Lightning-fast reactive UI without virtual DOM overhead |
| Key Derivation | PBKDF2-SHA256 | Derives 256-bit encryption keys (100,000 iterations) |
| Encryption | AES-GCM 256-bit | Authenticated encryption of all vault data |
| Storage | SHA-256 Namespace | Local storage isolated per Master Password hash |
| Memory | Ephemeral RAM State | Strict session wipe on vault lock / component destroy |
Architecture Flow
Master Password Entry
User enters a Master Password locally. The browser uses PBKDF2 (100,000 iterations) to generate a secure encryption key entirely in RAM.
Client-Side Encryption (AES-GCM)
Data entered into the vault is immediately encrypted locally. No plaintext data is ever exposed to the network or saved to disk.
Isolated Local Storage
The resulting Ciphertext is saved in the browser's Local Storage, within a specific namespace derived from the SHA-256 hash of the Master Password.
Session Wiping
Upon clicking "Lock Vault", the reactive state (Svelte $effect) forcefully wipes all sensitive variables from the browser's RAM, ensuring zero-knowledge isolation.