Digital legacy checklist

• Phone, tablet, laptop, desktop, smartwatch
• PIN, pattern or password for each device
• Where the recovery key for disk encryption is kept

• This is the master key: most password resets run through it
• Note the provider, the address and where the password lives
• Check whether two-factor authentication is on, and where the backup codes are

• Which manager you use, and where the master password is kept sealed
• Emergency access for a trusted person, if the manager supports it
• Export or recovery kit stored offline

• Bank accounts, brokerage, pension and savings products
• Standing orders and direct debits that should stop
• Crypto: where wallets and seed phrases are, and never in plain text online

• Streaming, cloud storage, software, memberships, mobile contracts
• Which ones should be cancelled and which should continue
• The payment method each subscription is tied to

• For each account: delete, memorialise or hand over
• Legacy contact on Apple, Facebook and Google where available
• Whether photos and messages should be exported first

• Cloud storage and external drives
• What should be preserved for the family
• Where the backups are and how to reach them

• Registrar, hosting, shops, invoices
• Anything with running obligations towards customers
• Who can take over technically

• Life, accident, liability, legal expenses
• Policy numbers and where the paperwork is
• Employer and pension entitlements

• Who should receive what — not everyone needs everything
• Phone numbers and email addresses that are actually current
• Tell them in advance that you have named them

• One sentence per account about what should happen
• Personal messages that should only be read afterwards
• Wishes for the funeral, music, notifications

• A handwritten or notarised will (§ 2247 BGB)
• A transmortal power of attorney for quick account access
• A pointer in the will to where the digital schedule is kept

Never write passwords into a document that others can read while you are alive. Record where the credentials are — not what they are. That is exactly the gap Erbnis closes: encrypted storage plus a release you control.