Security by Design
LifeWyn is architected so your vault reaches our servers already encrypted, with its keys left behind on your device. We release only what your rules permit — key-shares, never plaintext.
Zero-Knowledge
By Design
Encryption
XChaCha20-Poly1305
Key Derivation
scrypt (N=2^15)
Threshold Crypto
Shamir, threshold you set
In-Transit
TLS 1.2 / 1.3
At Rest
Client-encrypted
Release gates
Fail closed
Architecture
Four Pillars of Zero-Knowledge
Every layer adds defense in depth. From your device to our servers — no single point of trust.
Client-Side Encryption
All encryption happens on your device, and your master password never leaves it. The keys that decrypt your vault are derived there and are not sent to us.
Implementation
scrypt (N=2^15, r=8, p=1) → 256-bit master key
Ciphertext-Only Storage
Vault items and document bytes are stored as ciphertext, and the keys that open them are not stored with them. Your account and your nominees’ contact details ARE stored readable — the service cannot notify or verify someone whose address it cannot read.
Implementation
XChaCha20-Poly1305 (AEAD) for vault items and document bytes alike
No Server-Side Vault Decryption
Your vault key is derived on your device and never transmitted, so no code path on our side decrypts it. We do hold a server-side wrapping key for stored key envelopes — it protects those envelopes and does not open your vault.
Implementation
Vault key derivation and every key operation happen client-side
You Hold the Keys
Your master key derives category keys via HKDF-SHA-256, and asset keys below those. Each document gets a fresh random key wrapped under its category key. You control the root of trust.
Implementation
HKDF-SHA-256 with domain separation; Shamir Secret Sharing for vault key
Cryptography
Standardized Primitives — No Custom Crypto
We use only battle-tested, standardized algorithms. No proprietary constructions.
Vault items & documents
XChaCha20-Poly1305 (AEAD)
Wire format
SVAULT:v2
Key derivation
HKDF-SHA-256
Vault passphrase stretching
scrypt (N=2^15)
Account login password
Argon2id (server-side)
In transit
TLS 1.2 / 1.3
Key Management
Threshold Cryptography & Key Hierarchy
Your vault key is never stored whole. It is split into shares with Shamir's Secret Sharing, and you choose how many shares exist and how many are needed to rebuild it.
Key Derivation Hierarchy
Master Key (MK)
scrypt (N=2^15) → 256-bit
Vault Key
HKDF(MK, 'vault')
Credentials Key
HKDF(MK, 'credentials')
Documents Key
HKDF(MK, 'documents')
Assets Key
HKDF(MK, 'assets')
Bank
DEK → wrapped by CK
Insurance
DEK → wrapped by CK
Will
DEK → wrapped by CK
Crypto
DEK → wrapped by CK
Property
DEK → wrapped by CK
Investment
DEK → wrapped by CK
Medical
DEK → wrapped by CK
Digital
DEK → wrapped by CK
Each asset/document gets a unique random DEK, wrapped by its category key. Category keys derive from master key via HKDF-SHA-256 with domain separation.
Shamir Secret Sharing
Vault Master Key
Split into the shares you choose — any threshold-many reconstruct
Every share is encrypted to its recipient's own public key before it leaves your device. LifeWyn holds no share of its own, and stores only the sealed envelopes and the audit trail. You choose the recipients and the threshold.
Inheritance
Controlled, Verified, Proportional Disclosure
Different life events trigger different disclosure scopes. Hospitalisation ≠ Death.
Multi-Signal Verification
Confirmations and screened documents raise confidence; conflicts, tamper flags and duplicate cases raise fraud risk against it. No single signal decides.
Least Privilege Release
Nominees receive only key-shares for assets they're entitled to. Scoped by asset, condition, and timing rules you define.
Verified & Auditable
Every release is written to the hash-chained audit trail. Nominees get claim kits with forms, contacts, and step-by-step guidance.
Transparency
What We Can & Cannot Do
Honest capability model — no marketing fluff, just technical reality.
What LifeWyn Can Do
- Store your ciphertext securely
- Release encrypted key-shares to nominees
- Run automated life-signal check-ins
- Notify nominees when rules trigger
What LifeWyn Cannot Do
- Read your vault contents
- Reconstruct your master key
- Grant access without verification
- Reset your master password
Compliance
Standards, and what we have not certified
What the platform implements, and — just as plainly — which certifications nobody has audited us against.
SOC 2 Type II
No audit has been performed or scheduled
ISO 27001
No certification has been sought
GDPR
Access, rectification and export are implemented; erasure is a recorded request
DPDP Act (India)
Consent records and data-rights workflows are implemented
Data residency
One deployment region today; per-region hosting is not offered
Deep Dives
Explore Security Topics
Technical deep-dives for engineers, auditors, and security-conscious users.
Your Keys. Your Rules. Your Legacy.
LifeWyn never holds your master key. You decide who gets shares, when they rotate, and when to revoke. Start securing your digital legacy today.
Standard, well-reviewed primitives — no proprietary cryptography