How Heritage protects vault content, personal recovery and delivery of the packages you choose.
Content is encrypted on your device with authenticated encryption and a 256-bit key: an invalid change fails verification and cannot be opened. XChaCha20-Poly1305 protects content and key envelopes; the password path combines Argon2id, HKDF and an independent factor. AES-256-GCM protects specific envelopes sealed to the device.
While your account is active, Heritage cannot read your vault content. This boundary covers encrypted content. Account, identity verification and notification data are handled as described in the service privacy notice.
Release uses tlock and drand quicknet, a public distributed randomness network from the League of Entropy. Release material can only be opened after a future network round. Administrators and operators have no path to advance or force delivery.
You check in every 15, 30, 60 or 90 days, with 30 as the default. After a missed check-in, default timings are 7 days of reminders, a 24-hour pre-alert, a 24-hour countdown and a final 7 days: 16 days of notices in total, plus required checks. Your confirmation stops the process before final delivery. Notices use verified channels available in your account.
With a surviving authorized device, you regain access through security checks. If you lose your password and all devices, full recovery first has a 24-hour notice window, then fresh identity verification and checks to restore access. You can cancel the request during the initial window. There is no fast lane; overall time also depends on verification.
Each beneficiary receives only the package you assigned to them, after the required steps and waiting periods. You can also prepare the vault for your own recovery without naming beneficiaries.
Heritage prepares access to information and instructions. It is not a will, transfers no ownership, and inheritance outcomes are not guaranteed. It does not replace a notary, lawyer, accountant, fiduciary or tax and financial advice.
| Algorithm | Use | Key | Nonce | Key derivation | Where keys live |
|---|---|---|---|---|---|
| XChaCha20-Poly1305 | Vault content and packages | 256 bits | 24 bytes | Random keys generated on the device | Readable on authorized devices; only encrypted material reaches the service |
| XChaCha20-Poly1305 | key envelopes | 256 bits | 24 bytes | Argon2id + HKDF-SHA256 and independent factor | The authorized device combines password and protected factor; no separate component is sufficient |
| AES-256-GCM | Factor sealed to the device | 256 bits | 12 bytes | P256 + HKDF-SHA256 | The factor travels sealed to the authorized device |
| Stage | Duration | Checks and cancellation |
|---|---|---|
| Heartbeat cadence | 15, 30, 60 or 90 days; default 30 | A check-in updates the heartbeat |
| Delivery: reminders | 7 days | Owner confirmation |
| Delivery: pre-alert | 24 hours | Owner confirmation |
| Delivery: countdown | 24 hours | Owner confirmation |
| Delivery: final window | 7 days; default 16 days of notices in total | Owner confirmation before delivery |
| Recovery: initial notice window | 24 hours before identity verification | Cancellation during the initial window |
| Recovery: identity verification | After the initial window; duration depends on verification | Identity and security checks |
| Recovery: restore access | After verification and authorization; no fixed total | Authorized-path checks |
| Recovery with a surviving device | Access from an authorized device with required checks | No full recovery procedure needed |