Malwarebytes outlines planning digital accounts after death
First merged summary.
Malwarebytes says telling loved ones your wishes and using platform legacy tools beats sharing passwords after death.
Malwarebytes published a Lock and Code interview and a companion guide on managing online accounts after death. Jed Brubaker of the University of Colorado Boulder’s Digital Legacy Clinic told host David Ruiz that companies often control digital remains and that stating wishes to loved ones matters more than any single platform setting. He said the average American internet user has 190 accounts. The guide advises an inventory of accounts and desired outcomes kept separate from passwords, recovery codes, and seed phrases, and describes Apple, Google, Facebook, Instagram, and Microsoft tools. It notes that rules differ and that, in US states that adopted RUFADAA, access to private communications generally needs the account holder’s consent.
- Brubaker says the average American internet user has 190 online accounts.
- Inventory should omit master passwords, recovery codes, and seed phrases.
- Apple Legacy Contacts need an access key and a death certificate.
- Google Inactive Account Manager is triggered by inactivity, not death confirmation.
- Facebook legacy contacts get limited memorialization powers, not full access.
- OneDrive Digital legacy gives a contact read-only access to files and photos.
What each outlet adds
beyond the shared facts- Malwarebytes LabsPodcast interview: Brubaker, 190 accounts, and the interpersonal priority.
- Malwarebytes LabsPractical guide covering RUFADAA consent and named platform legacy tools.
- Organizations
- Digital Legacy ClinicUniversity of Colorado Boulder
- Countries
- United States
Coverage
oldest first · one row per article · UTCPodcast covers how to prepare digital accounts before death
Jed Brubaker says telling relatives your wishes matters more than any single platform’s death setting.
How to prepare digital accounts for access after death
Keep an inventory separate from passwords, name trusted people, and use provider legacy tools instead of sharing credentials.