Digital Legacy · Memory Vault

Seal what matters.
Unlock it when it must.

A privacy-first vault for memories, letters, and encrypted assets — released to your loved ones only when verified conditions fire. A dead man's switch. A quorum of trusted hands. The choice is yours.

0
Servers
Holding Your Data
256
Bit AES-GCM
Client-Side
M-of-N
Shamir
Consensus
VERIFIED
0xA1B9
SHA-256
PBKDF2
How the vault works
01 · Encrypt

Write & seal in your browser

Compose a letter, attach a file, mark a beneficiary. Your master password derives a key locally via PBKDF2; content is sealed with AES-256-GCM. The ciphertext never leaves your machine unless you choose to export it.

02 · Arm

Set the conditions of release

A dead man's switch releases the vault if you stop checking in. A multi-party consensus requires M of N trusted custodians to attest before the seal breaks. Combine both for layered safety.

03 · Verify

The trigger fires, the seal cracks

When a deadline passes — or enough custodians come forward — the vault becomes UNLOCKABLE. At that point, your beneficiary presents their claim code and the contents decrypt in their browser.

04 · Decentralize

No single point of failure

Unlock shares are split with Shamir's Secret Sharing — no individual custodian can release the vault alone, and missing shares do not lose the secret as long as the threshold is met. The bundle is exportable; you decide where it lives.

Lamport is an open-source reference implementation. Cryptography is performed entirely in your browser via the Web Crypto API. No data is transmitted. Treat this as you would any cryptographic software: review the code, keep your master password offline, and test your recovery flow before you need it.
The Vault

Your sealed legacies

Each entry is encrypted at rest. Check in regularly to keep your dead man's switches from arming.

Heartbeat · Last check-in
New Vault

Seal a memory

Walk through four steps. Everything is encrypted before it ever touches storage.

Seal
Contents
Conditions
Custodians
The person (or role) who may claim this vault when conditions are met.
The beneficiary will need to enter this exact code to unlock the vault.
Markdown is preserved. The text will be encrypted before storage.
Drop files here or click to choose
Images, PDFs, text — up to 10MB each. Encrypted client-side.
60 days
If you don't return to check in within this window, the vault becomes unlockable for the beneficiary.
Final review

Confirm master password

Re-enter your master password to seal this vault. It will derive the encryption key locally; the password itself is never stored.

L

?
Beneficiary Portal

Claim an inheritance

If a vault has been left to you and its conditions have fired, enter the vault ID and the claim code you were given.

Settings

Master controls

Export encrypted bundle
Download a single JSON file containing every sealed vault. The file is useless without the master password. Store it wherever you like — IPFS, a USB stick, a safety deposit box.
Import encrypted bundle
Restore vaults from a previously exported bundle. Existing vaults are kept.
Trigger all dead man's switches test
For demonstration: simulate the check-in deadline passing. This will mark your DMS-armed vaults as unlockable. Useful for walking a beneficiary through the claim flow.
Reset check-in timers
Marks every vault as freshly checked in. Use after running a DMS test.
Wipe everything
Permanently delete all vaults, shares, and metadata from this browser. There is no recovery.
Lamport runs entirely in your browser. Clearing site data, switching browsers, or wiping without an export will lose your vaults irrecoverably. Test your recovery path before relying on it.