How it works
From encrypted today to inherited tomorrow
Here's the full journey — how LifeWyn keeps your data private while you're here, and releases it to the people you trust only after your rules are met and a passing is verified beyond doubt.
- Step 1
Encrypt & store
Your documents, credentials, and messages are encrypted on your own device — client-side — before anything is uploaded. Only ciphertext ever reaches our servers. The keys that can unlock it never leave your control.
- Step 2
Set your rules & nominees
Decide who inherits what. Add nominees, executors, and trustees, then configure thresholds and primary, secondary, and tertiary fallbacks. Grant each person least-privilege access down to the individual item.
- Step 3
Stay checked in, stay protected
On a cadence you choose, you confirm you're well with a simple tap. Everything stays private and dormant. Miss your check-ins and a graduated escalation begins — reminders first, then your trusted contacts.
- Step 4
Multi-signal verification
Release is never triggered by a single event. Documents, trusted-contact confirmations, and independent signals are combined by a confidence engine that only proceeds once a high threshold is crossed. Disputes can pause the process for review.
- Step 5
Key-share release
Once verification succeeds, our servers release encrypted key-shares — never plaintext data — to the nominees your rules authorize. Threshold cryptography ensures no single party could have reconstructed those keys alone.
- Step 6
Nominees claim & access
Nominees use the accountless portal — no sign-up required — to verify their identity with a one-time code, decrypt exactly what you left them, and complete their claim. Every step is tracked and timestamped.
We release keys — we never hand over your data
Most services would simply share your files with a beneficiary. LifeWyn works differently: your data stays encrypted end to end, and inheritance happens by releasing encrypted key-shares to authorized nominees. The server never sees, copies, or decrypts your content.
The server never decrypts
We only ever hold ciphertext and encrypted key-shares. There is no moment in the flow where your plaintext exists on our infrastructure.
Nothing to leak, nothing to subpoena
A breach or a legal demand reaches ciphertext, plus the account details we need to run the service. The keys that decrypt your vault are derived on your device and are not on our servers.
You stay in control until the very end
Access is unlocked by releasing key-shares to the people you chose, under the rules you set — not by us copying or forwarding your data.
Ready to set it up for yourself?
Create your vault, add the people you trust, and configure the rules that decide when — and only when — access is released.