Trust Center
Security you can verify, not just trust
LifeWyn is built so that your privacy is never the price of protection. Here is how your vault is encrypted, what has to be verified before anyone else can open it, and where our limits are.
Zero-knowledge by design
Your vault is encrypted on your device before it ever leaves it, and the keys that open it are never sent to us. Your account details and your nominees' contact details are stored readable, because we cannot notify or verify someone whose address we cannot read.
Key management
Hierarchical envelope encryption: your master key derives Category keys with HKDF-SHA-256, and each asset and document gets its own random key wrapped under its category key. Inheritance shares are split with Shamir and encrypted to each recipient's public key. Server-side key wrapping uses a software key store today, not a hardware or managed KMS.
Modern cryptography
XChaCha20-Poly1305 authenticated encryption and HKDF key derivation on the client; TLS 1.2/1.3 in transit; threshold (Shamir) secret-sharing for escrow.
Hash-chained audit
Every sensitive action is written to an audit trail, each entry hash-chained to the one before it, and the hashes travel with audit exports so records can be checked against them. The store is not yet append-only at the database level, so we do not claim the trail is proof against an administrator.
Resilient infrastructure
Health-checked services, least-privilege access between components, and a single front door that validates every token. Encryption at rest is our hosting provider's default rather than a control we configure. Because your vault arrives already encrypted, a breach of our storage reaches ciphertext plus the account details we need to run the service — not your vault contents.
Recovery without lock-out
Arm recovery in advance — a recovery phrase, plus trusted contacts who each hold a sealed share — and a lost device stops being a lost vault. Recovery has to be set up before you need it: if it was never armed there is nothing on our side to restore from. Completing a recovery is currently web-only.
Documentation
Trust resources
How the zero-knowledge model, encryption, and key hierarchy fit together.
Our posture on GDPR, India's DPDP Act, and data-subject rights.
What we collect, what stays encrypted, and how we handle your data.
Scope, safe harbour, what we commit to when you report a vulnerability — and what we do not offer.
Live operational status of the platform.
Responsible disclosure
Found a vulnerability? Report it privately. We acknowledge within three working days, we will not pursue research done in good faith under our policy, and we will tell you what we did about it. There is no paid bounty programme and no published audit report — the full policy says so plainly.
Backups and availability
The database is backed up nightly and encrypted before it leaves the server, and there is a written restore procedure we rehearse. LifeWyn runs in a single region with no automatic failover, and there is no point-in-time recovery — a restore returns the platform to the last nightly backup. No uptime SLA is published yet.
System status