Skip to main content
Protect your family's digital future

Your passwords and crypto shouldnt disappear with you.

VaultPass keeps your passwords and wallet recovery phrases locked on your own device — and passes them to the people you choose if you're ever no longer able to reach them yourself.

Create Your Vault
🔒 Encrypted on your device✓ No banks · No lawyers✓ Cancel anytime

Takes about 10 minutes to set up.

You
Encrypted vault
Trusted family

Unlocked only if you stop checking in.

Why this exists

Crypto doesn't get inherited.
It just stops.

A bank account has a next of kin. A wallet has a seed phrase and nothing else. When the person who memorised it is gone, so is the money.

1 in 5
bitcoins may already be lost forever

Not stolen — stranded. Chainalysis estimates that 2.8 to 3.8 million coins have sat untouched since Bitcoin's early years. They still exist; nobody alive can move them.

No one
can reset a seed phrase for your family

There is no support line and no password reset. If the phrase is gone, the wallet is gone.

1 sheet
of paper is the whole plan for most people

A safe, a drawer, a deposit box. It survives fire and flood right up until it doesn't — and your family still has to find it.

Loss estimate: Chainalysis — 2.78–3.79M BTC dormant since Bitcoin's early years. A cumulative total since 2009, not a yearly figure, and an estimate rather than a count.

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 owner shard never leaves your device — we store only ciphertext.
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 → 7-day grace period (100 days on Annual & Founder) → heirs are automatically unlocked.
See the full architecture →

Before you trust us with anything

Why your secrets stay yours.

You shouldn't need to understand cryptography to trust us with something this important. Here is what it means in plain English — and where to check each promise for yourself.

Unreadable before it leaves your device

Your passwords and recovery phrases are encrypted on your own device, before anything is stored or sent. What reaches our servers is unreadable text — never the secrets themselves.

See how encryption works →

We hold the timer, not your passwords

Your key is split into three pieces. We keep two of them encrypted, and only bring them together if your check-ins stop. We publish exactly what we hold — and what could still go wrong.

Read our security model →

It still works if we disappear

The code that opens a vault is public and permanently archived. Decrypting doesn't depend entirely on VaultPass — not on our servers staying online, our app, or an active subscription.

View the recovery guarantee →

Real people behind VaultPass

Built in the open by a named founder, Suresh Kumar Ramar, with a published security review and a standing invitation for researchers to find our flaws.

Meet the people behind it →

Rather not take our word for any of it? Good — neither would we.

2 of 3
Shards To Recover
0 bytes
Plaintext Stored
AES-256
Encryption Standard

Instead of testimonials

We're early. Judge the code, not the quotes.

VaultPass is a young product, so we have no customer stories worth printing yet. Here is what you can verify without trusting us.

Under the hood

The detail, if you want it.

Everything above, stated precisely — the algorithms, the key-splitting scheme, our audit status, and a snippet you can paste into your own browser console to check the encryption yourself.

Hide the technical proof

SECURITY FOUNDATION

Don't trust us.
Verify us.

The cryptography here you can check yourself — in your browser, without taking our word for it. Our audit status is a roadmap, not a result.

⬡ AUDIT ROADMAP

3-Phase Audit Roadmap

Internal Security Review✓ Done
Community Bug Bounty● Live
External Professional AuditPlanned
⬡ 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"])

Shard Distribution · Illustrative

tap a node to inspect
🇺🇸US-East-1Virginia🇩🇪EU-Central-1Frankfurt🇸🇬SG-West-1Singapore

Shard Locations

No single server holds the whole key — any 2 of 3 shards reconstruct your vault.

Shamir's Secret Sharing · 2-of-3

Master Key

splits into

SHARD α

Device

SHARD β

Heir

SHARD γ

Sentinel

2 of 3

Like cutting a physical key into 3 pieces — each is useless alone. Any two together unlock the vault.

Shamir's Secret Sharing2-of-3 ThresholdInformation-TheoreticOwner Shard On-Device

Protocol Standards

AES‑256‑GCMWEB CRYPTO APIBIP‑39 PHRASESSHAMIR SSSSOC 2 ‑ PLANNED

Why not just 1Password or Bitwarden?

They're great password managers.
Inheritance is an afterthought.

Both encrypt on your device — and we respect them. But neither is built for crypto succession. That's the whole point of VaultPass.

Feature1Password / BitwardenVaultPass
Client-side encryptionYesYes
Purpose-built for crypto seed phrasesGeneral credentialsYes
Inheritance modelBolt-on emergency accessDead man's switch + grace period
How the heir gets your keyAccess to your whole vaultShamir 2-of-3 — released only when the switch fires
Recovery if the company shuts downVault tied to their serviceOpen-source recovery — decrypt without us

The unique advantage:VaultPass is built ground-up for crypto succession — a dead man's switch, Shamir-sharded keys, and recovery that survives even us.

Ready when you are

Your digital legacy deserves a plan.

Zero plaintext. Zero custody. Zero compromise.

Get StartedSee Plans →
or join the community@getvaultpass