Dutch public broadcaster NOS published a piece this week with a question that used to sound niche:
Who inherits your passwords and crypto?
That question is not niche anymore.
It is not only for crypto holders. It is not only for people with complex estates. It is not only for the unusually organized person with a label maker, a fireproof box, and a spreadsheet called "Emergency - final final v3".
Almost everyone now has a digital estate.
Email. Photos. Phones. Two-factor authentication. Password managers. Cloud storage. Subscriptions. Social media. Banking apps. Domain names. Business systems. Crypto wallets. Recovery codes. Private notes. Family documents. Accounts nobody else knows exist.
Some of it has financial value. Some of it has emotional value. Some of it is boring until it becomes urgent.
That is the problem with digital legacy. It stays invisible right up to the moment a family needs it.
Awareness is arriving
The NOS article covers a Dutch political push for more awareness around digital inheritance. MP Barbara Kathmann wants a national campaign and wants digital legacy to become part of digital-skills education, especially for older people.
Good.
The article also points to Data na de Dood, an awareness campaign from Alliantie Digitaal Samenleven. Their eight-step plan walks people through the obvious problem areas: make an inventory, check Meta accounts, document services where nothing formal can be arranged, handle email, Apple and Android, phone subscriptions, passwords, and identity fraud.
That is useful. More people should start there.
But awareness is not the same as execution.
Knowing that your family may need your email account is not the same as giving them a safe, lawful, understandable way to deal with it. Knowing that your phone contains the keys to your digital life is not the same as explaining which information matters, who should receive it, and what should happen if you can no longer unlock the device yourself.
A checklist can start the work. It cannot be the whole plan.
The hard part is not making the list
Making a list of accounts is uncomfortable, but manageable.
The harder question is what the list is for.
If someone receives a password manager emergency kit, what should they do with it? Which accounts are important? Which should be closed? Which contain family photos? Which are business-critical? Which subscriptions keep billing? Which email address controls password resets for everything else? Which documents belong with your partner, your children, your executor, your business partner, or nobody at all?
A password without context is often just another problem.
That sounds harsh, but imagine the situation from the other side. Someone has died or become unreachable. The family is tired, grieving, and suddenly responsible for reconstructing a digital life from fragments. They may have a phone. They may have a laptop. They may have a binder with old passwords, some of which still work, many of which do not.
Now add modern security.
Passkeys may be device-bound. Two-factor codes may live on a phone nobody can unlock. A recovery email may point to another account with its own recovery loop. A crypto wallet may technically still exist but be practically gone. A business domain may renew from a card that gets cancelled. A cloud account may contain the only copy of important documents, but nobody knows which folder matters.
Security did its job. It kept outsiders out.
Unfortunately, after death or incapacity, the family may look exactly like outsiders to the systems involved.
Platform tools are fragmented
Some platforms have legacy features. Apple has Legacy Contact. Google has Inactive Account Manager. Meta has memorialization and legacy-contact options for some services. Password managers may have emergency access. Crypto wallets have their own recovery realities.
Use those tools where they fit.
But they do not add up to a digital estate plan.
Each platform solves its own slice. Each has its own assumptions, waiting periods, proof requirements, access rules, and blind spots. Some require death certificates. Some depend on inactivity. Some assume the family already knows where to start. Some preserve memories but do not help with operational access. Some handle accounts but not instructions.
The result is a patchwork.
Patchwork is fine when life is calm and someone has time to read documentation. It is much less fine when the person who understood the setup is no longer available.
What families need is not a dozen separate platform policies. They need a map.
What exists?
Where is it?
Who should know?
Who should get access?
What is urgent?
What should be preserved, transferred, cancelled, deleted, or ignored?
That is the layer most people have not written down.
The email account is the quiet center
The NOS article mentions passwords and crypto, which are the obvious attention-grabbers.
The quieter problem is email.
Your email account is often the control plane for your digital life. Password resets go there. Subscription notices go there. Invoices go there. Domain-renewal warnings go there. Account-recovery links go there. Financial traces go there. Old conversations and attachments go there.
Lose access to the primary email account and the rest of the estate becomes much harder to understand.
That does not mean you should hand someone your mailbox password on a sticky note. Please do not turn estate planning into a phishing starter kit.
It means your digital legacy plan should explain the role of that account. Who may need access? Under what circumstances? What should they look for? Which accounts depend on it? Which recovery methods are configured? Which parts are private and should not be casually opened?
Again, context matters.
Families do not only need keys. They need instructions for using the keys without making everything worse.
Crypto makes the stakes obvious
Crypto gets attention because failure is so clean.
If nobody has the seed phrase, the wallet is gone. There is no support desk for Bitcoin. No probate officer can call the chain and ask it to reset access. From the outside, the asset still exists. From the family's perspective, it may as well have been burned.
That makes crypto inheritance a useful warning sign for the rest of the digital estate.
Most accounts are not as unforgiving as a self-custody wallet. But the pattern is the same: ownership on paper does not mean practical access. Legal entitlement does not tell anyone where the recovery material is. Knowing that something exists does not explain what the owner wanted done with it.
The same logic applies to business accounts, domains, family photos, creative archives, financial records, and private documents.
Digital inheritance fails when there is no bridge between the person who understood the system and the people who later need to act.
A digital estate plan needs release logic
This is the part most checklists do not solve.
Where should the plan live?
If it sits in a paper folder, will anyone find it? If it sits in cloud storage, who can access it? If it sits in a password manager, who knows the emergency process? If it contains sensitive material, how do you stop the wrong person from seeing everything too early? If it is too vague, how will anyone use it? If it is too detailed in the wrong place, how do you keep it safe?
A useful digital estate plan needs four things.
First, an inventory: accounts, assets, documents, devices, services, and recovery paths.
Second, context: what matters, what does not, and what should happen.
Third, separation: not every trusted person should receive the same information.
Fourth, release logic: a controlled way to deliver the right information when you can no longer do it yourself.
That release logic is the missing piece.
Without it, the plan depends on someone finding the right document, at the right time, understanding it correctly, and being authorized to act. That may work for some families. It will fail for many.
What Trustbourne is trying to solve
Trustbourne is not a will. It is not a notary. It is not a magic override for platform policies. It does not make every account recoverable, and it does not replace legal estate planning.
That distinction matters.
Legal authority still matters. Inheritance law still matters. Taxes, guardianship, business ownership, and formal estate administration still belong with the proper professionals.
Trustbourne sits underneath that.
It is a secure place to store the practical digital layer: files, recovery notes, instructions, account context, crypto guidance, business continuity information, and anything your trusted contacts may need if you cannot respond.
You choose trusted contacts. You decide what belongs in the vault. You decide who should receive which information. Trustbourne checks in with you. If you stop responding after the configured process, the release flow begins.
The goal is not to make death more technical.
The goal is to stop making families solve technical problems while grieving.
Start with the checklist. Then make it usable.
The Data na de Dood checklist is a good starting point.
Use it. Walk through your email account. Look at your phone. Check Apple, Android, Meta, your password manager, phone subscription, and identity-fraud risks. Write down what matters.
Then ask the harder question:
If something happened to me, could the right person actually use this?
Would they know where to find it?
Would they understand what each account is for?
Would they know which information is private, which is urgent, and which belongs to someone else?
Would they receive the right information without getting everything?
Would the plan still work six months from now?
That is where digital legacy becomes real.
The public conversation is moving in the right direction. Governments are paying attention. Campaigns are teaching people the basics. Platforms are slowly adding legacy features.
Good.
But your family does not need awareness someday.
They need a plan that works when you cannot explain it anymore.
Trustbourne helps you prepare the digital layer of your estate before anyone needs it: encrypted storage, trusted contacts, check-ins, and clear release rules for the accounts, files, and instructions that matter. Learn more.