About Digital Keep
Digital Keep is a digital legacy planning platform in private beta. It is being built to help people organize important information, explain what matters and choose the people it is intended for.
The private beta is a place to test preparation: vault items, instructions, attachments and intended recipients. Legacy verification and release are still being developed and are not active services. Access to the beta is by invitation.
Why we are building it
Important information often lives in several places: an email account, cloud files, a password manager, a document folder or someone's memory. A trusted person needs more than a list of services. They need context, clear instructions and a legitimate way to act.
Digital Keep's focus is that preparation. The intended experience is to record what an item means, decide who it concerns and make the next steps understandable. A family message and a business continuity note may need different recipients and different handling.
What is available and what is still in development?
| Area | Current status |
|---|---|
| Public planning resources | Free guides, an account-planning checklist and a printable worksheet. No beta account is needed. |
| Private beta workspace | Invited testers can prepare example vault items, attachments and instructions, and assign intended recipients. |
| Account and content protection | Server-side AES-GCM encryption, two-factor authentication and account-scoped access checks are implemented in the private build. |
| Legacy verification and release | Still in development. There is no active death-verification or legacy-delivery service. |
| Public launch | No confirmed date. Joining the waitlist does not guarantee an invitation on a particular date. |
What the product does not promise
Digital Keep does not automatically detect a death or connect to government death registries. It does not transfer ownership of money, cryptocurrency or accounts. It is not a will, and it does not replace a password manager or an account provider's own access process.
The beta uses server-side encryption: the application server can decrypt content using its configured keys. It is not end-to-end or zero-knowledge encryption. Read the security explanation before deciding what a future production service would need to meet your requirements.
During testing, use fictitious information and sample files. Keep real handoff arrangements and working copies elsewhere. The beta data policy covers test accounts and their content; the public-site privacy notice covers the website and waitlist.
How we write our planning resources
Digital Keep publishes its guides as practical product and planning information. They separate features available today from features still being developed. Examples are illustrative, rather than customer stories or evidence of a completed inheritance process.
- Use primary sources: provider-specific guidance links to the provider's own instructions so readers can check the current requirements.
- Make limits visible: explain what a tool covers, what it leaves out and where a separate plan is needed.
- Show context: dated guides identify when they were published or reviewed; the date is not a promise that an outside service will stay the same.
- Keep advice in scope: planning guides are general information, not personalized legal, financial or estate-planning advice.
If you spot an outdated instruction or an unclear product claim, email contact@digital-keep.com with the page link and the point that needs checking. Do not include private account contents or credentials.
← Back to Digital Keep