Skip to main content

Your Digital Soul,Secured Forever.

Like a bank's safety deposit box — only the right person can open it, only when the time comes. Your keys stay yours — until the day they need to become theirs.

✓ Internal Audit Complete◎ External Audit — Scheduled Q3 20267-day heir safety buffer
📉Estimated Lost Crypto:$142,394,029,102Don't let your assets be part of this number.📉Estimated Lost Crypto:$142,394,029,102Don't let your assets be part of this number.
heartbeats verified today0 vaults compromised since foundingZero plaintext ever transmittedAES-256-GCM · Zero plaintext stored · Zero breaches heartbeats verified today0 vaults compromised since foundingZero plaintext ever transmittedAES-256-GCM · Zero plaintext stored · Zero breaches
Zero-Knowledge EncryptionDead Man's SwitchSeed Phrase Guard
scroll
01
AES-256-GCMWEB CRYPTO API
BIP-39SHAMIR SSS
GDPRSOC 2 — Planned

Security Foundation

Don't trust us.
Verify us.

Every security claim on this page is independently verifiable — in your browser, without taking our word for it.

Independent Audit

3-Phase Audit Roadmap

Internal Security Review✓ Done
Community Bug Bounty● Live
External Professional AuditH2 2026

Responsible disclosure programme active. Valid findings earn public Hall of Fame credit and CVE. Full audit report published publicly upon completion.

View audit roadmap →
Open Source Verification

Verify in Your Browser — Right Now

All cryptographic primitives are browser-native. Open DevTools → Console and run:

AES-256-GCM

crypto.subtle.generateKey({name:"AES-GCM",length:256},true,["encrypt","decrypt"])

PBKDF2 key derivation

crypto.subtle.importKey("raw",new Uint8Array(32),"PBKDF2",false,["deriveKey"])

Full crypto-core open-source release scheduled H2 2026 following external audit. No proprietary cryptography — ever.

View encryption standards →
AES-256-GCM
Vault Encryption

NIST-standardised authenticated encryption. Same standard used by NSA for TOP SECRET data. Browser-native via Web Crypto API — no external libraries.

PBKDF2-SHA-256
Key Derivation

100,000 iterations of key stretching. ~150ms per guess locally — brute force is economically unviable. Your master key never stored or transmitted.

Shamir 2-of-3
Key Sharding

Vault key split into 3 shards. Any 2 reconstruct — 1 alone reveals nothing. Information-theoretically secure. VaultPass holds at most 1 shard, never enough.

Zero-Knowledge Architecture

Every encryption step occurs in your browser before any data leaves your device. Zero VaultPass employees have the technical ability to read your vault — not because of policy, but because of mathematics. A full server compromise yields only encrypted ciphertext.

Run the proof in your browser →
0Staff with vault access
0Plaintext bytes stored
0Breaches since founding
Full security whitepaper →

How It Works

Three steps to protect your digital legacy.

No third-party custody. No plaintext stored. Your secrets stay yours — even after you're gone.

1
Set Up Your Vault
AES-256-GCM encryption. Your master key never leaves your device — we never see it.
2
Add Trusted Heirs
Your vault key splits into shards via Shamir's algorithm. 2-of-3 threshold — no single heir can unlock alone.
3
Set Your Heartbeat
Check in periodically. Miss it → 10-day grace period → heirs are automatically unlocked.
See the full architecture →
$0B+
Crypto Lost Annually
0 bytes
Plaintext Stored
AES-256
Encryption Standard

Trusted By

People who take legacy seriously.

Get Started

Your digital legacy deserves a plan.

Zero plaintext. Zero custody. Zero compromise.

Get StartedSee Plans →
or join the community@getvaultpass