├── Use Cases.md ├── README.md ├── legacy_contact ├── yahoo_US.md ├── facebook_US.md ├── TEMPLATE.md ├── linkedin_US.md ├── github_US.md ├── apple_US.md ├── google_US.md ├── google_workspace_US.md └── 1password_US.md ├── CONTRIBUTING.md ├── .github ├── PULL_REQUEST_TEMPLATE │ └── legacy_contact_process_pr.md └── ISSUE_TEMPLATE │ └── use-case-template.md ├── cybersecawareness2025 ├── proposal.md └── planning_guide_outline.md ├── charter.md └── resources.md /Use Cases.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | **READ ME** 2 | 3 | Welcome to the Death and the Digital Estate (DADE) GitHub repo. See our [Wiki](https://github.com/openid/death-and-the-digital-estate/wiki/) for meeting information, meeting notes, etc. 4 | 5 | Have resources to share? Please file an issue if the item doesn't already exist in our [Resources wiki](https://github.com/openid/death-and-the-digital-estate/wiki/Resources). 6 | 7 | [DADE Mailing List](https://lists.openid.net/mailman/listinfo/openid-digital-directives) 8 | 9 | Slack: #DADE channels on both [OpenID Foundation](https://openid.net/) Slack and [IDPro](https://idpro.org) Slack 10 | -------------------------------------------------------------------------------- /legacy_contact/yahoo_US.md: -------------------------------------------------------------------------------- 1 | **Adding a Legacy Contact** 2 | 3 | **Service:** 4 | 5 | * Yahoo 6 | * [https://yahoo.com](https://yahoo.com) 7 | 8 | **Account Country / Countries** 9 | 10 | * Unknown 11 | 12 | **Account Type:** 13 | 14 | * Unknown 15 | 16 | **The Process:** 17 | 18 | * Yahoo's help documentation: https://help.yahoo.com/kb/SLN2021.html 19 | 20 | * _write a narrative describing how you created a legacy contact._ 21 | 22 | **Qualitative assessment of what went well, what went wrong, what would have helped, etc.:** 23 | 24 | * _what went well/what went poorly_ 25 | 26 | **Additional Data** 27 | 28 | * _any other data? URLs or links to reference materials can go here._ 29 | -------------------------------------------------------------------------------- /legacy_contact/facebook_US.md: -------------------------------------------------------------------------------- 1 | **Adding a Legacy Contact** 2 | 3 | **Service:** 4 | 5 | Facebook 6 | https://facebook.com 7 | 8 | **Account Country / Countries** 9 | 10 | USA 11 | 12 | **Account Type:** 13 | 14 | Personal 15 | 16 | **The Process:** 17 | 18 | [Facebook - Legacy Contacts](https://www.facebook.com/help/991335594313139/) 19 | 20 | [Account Ownership and Control](https://accountscenter.facebook.com/personal_info/account_ownership_and_control) 21 | 22 | Follow the prompts to select a legacy contact. 23 | 24 | **Qualitative assessment of what went well, what went wrong, what would have helped, etc.:** 25 | 26 | Easy to do, once I found the right help documentation. 27 | 28 | **Additional Data** 29 | 30 | None 31 | -------------------------------------------------------------------------------- /legacy_contact/TEMPLATE.md: -------------------------------------------------------------------------------- 1 | **Adding a Legacy Contact** 2 | 3 | **Service:** 4 | 5 | * _service name_ 6 | * _URL_ 7 | 8 | **Account Country / Countries** 9 | 10 | * _Countries which the account is configured in. Add additional information if required._ 11 | 12 | **Account Type:** 13 | 14 | * _Personal account, joint account, business account, etc._ 15 | 16 | **The Process:** 17 | 18 | * _URL documenting the process, if it exists_ 19 | 20 | * _write a narrative describing how you created a legacy contact._ 21 | 22 | **Qualitative assessment of what went well, what went wrong, what would have helped, etc.:** 23 | 24 | * _what went well/what went poorly_ 25 | 26 | **Additional Data** 27 | 28 | * _any other data? URLs or links to reference materials can go here._ 29 | -------------------------------------------------------------------------------- /legacy_contact/linkedin_US.md: -------------------------------------------------------------------------------- 1 | **Adding a Legacy Contact** 2 | 3 | **Service:** 4 | 5 | * LinkedIn 6 | * https://linkedin.com 7 | 8 | **Account Country / Countries** 9 | 10 | * United States 11 | 12 | **Account Type:** 13 | 14 | * Personal Account 15 | 16 | **The Process:** 17 | 18 | * [Closing the account of a deceased member](https://www.linkedin.com/help/linkedin/answer/a1336663/memorialize-or-close-the-account-of-a-deceased-member) 19 | * I could find no specific information on how to assign a legacy contact for this process. 20 | 21 | **Qualitative assessment of what went well, what went wrong, what would have helped, etc.:** 22 | 23 | * LinkedIn does not appear to offer any mechanism to establish a legacy contact for an account. 24 | 25 | **Additional Data** 26 | 27 | * None 28 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | **How to contribute** 2 | 3 | Welcome to Death and the Digital Estate Community Group (DADE CG). We're glad you're here, because we need volunteers to help this effort come to fruition. 4 | 5 | Here are some important resources: 6 | 7 | [Death and the Digital Estate Community Group Home Page](https://openid.net/cg/death-and-the-digital-estate/) has background data on DADE CG. Sign the [participation agreement](https://openid.net/cg/death-and-the-digital-estate/dade-participation-agreements/) to contribute to DADE CG. 8 | 9 | The DADE CG [Charter](https://github.com/deansaxe/death-and-the-digital-estate/blob/main/charter.md) describes the group's charter and proposed deliverables. 10 | 11 | Mailing list: Join our [mailing list](https://lists.openid.net/mailman/listinfo/openid-digital-directives) to ask questions or provide feedback 12 | 13 | 14 | Thanks, 15 | 16 | DADE CG co-chairs 17 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE/legacy_contact_process_pr.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Legacy Contact Process Documentation Template 3 | about: Template for PRs to describe how online services enable legacy contacts 4 | title: "[Legacy Contact Process] Description Here" 5 | labels: usecase, legacy_contact 6 | --- 7 | 8 | _Thank you for completing documentation of the legacy contact process!_ 9 | 10 | Before submitting a pull request, please make sure your documentation includes the following data: 11 | 12 | **Service:** 13 | _Examples include Apple, Google, etc. Please add a URL for the service. If the service is not available in English, please provide a description of the service._ 14 | 15 | **Dependencies:** 16 | _Examples: personal account, business account (e.g. Google Workspaces), other_ 17 | 18 | **The Process:** 19 | _Describe the process as you experienced it. Describe any issues you encountered in adding a legacy contact. If there is a URL with documentation on the process, add the URL here. 20 | 21 | **Qualitative assessment of what went well, what went wrong, what would have helped, etc.:** 22 | -------------------------------------------------------------------------------- /legacy_contact/github_US.md: -------------------------------------------------------------------------------- 1 | **Adding a Legacy Contact** 2 | 3 | **Service:** 4 | GitHub 5 | https://github.com/ 6 | 7 | **Account Country / Countries** 8 | 9 | USA 10 | 11 | **Account Type:** 12 | 13 | Personal, free tier account 14 | 15 | **The Process:** 16 | 17 | [Successors](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories) 18 | 19 | I was unable to execute the process. There is another page describing the [GitHub Deceased User Policy](https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy). 20 | 21 | **Qualitative assessment of what went well, what went wrong, what would have helped, etc.:** 22 | 23 | Since my designated successor does not have a GitHub account, I was unable to add her as my successor. However, in the [GitHub Deceased User Policy](https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy) there are manual mechanisms to obtain access as a next of kin or designated successor. 24 | 25 | **Additional Data** 26 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/use-case-template.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Use Case Template 3 | about: Template for describing DADE Use Cases 4 | title: "[Use Case] Description Here" 5 | labels: usecase, technical, legal, cultural, environmental, financial, medical, retail, government 6 | assignees: '' 7 | 8 | --- 9 | 10 | _Thank you for filling out a DADE use case! Please delete any labels that don't apply._ 11 | 12 | **Roles involved:** 13 | _Examples include *deceased*, *surviving family member*, *neighbor who helped out*, *family “sys admin”*, etc. Potentially useful concepts to employ: [advanced healthcare directives](https://en.wikipedia.org/wiki/Advance_healthcare_directive), [Revised Fiduciary Access to Digital Assets Act](https://www.uniformlaws.org/viewdocument/final-act-with-comments-40?CommunityKey=f7237fc4-74c2-4728-81c6-b39a91ecdf22&tab=librarydocuments)._ 14 | 15 | **Dependencies:** 16 | _Examples: the relevant platform, app, jurisdiction, etc._ 17 | 18 | **Additional context:** 19 | _Examples: industry or cultural factors._ 20 | 21 | **The goal of the interaction:** 22 | 23 | **What actually happened:** 24 | 25 | **Qualitative assessment of what went wrong, what would have helped, etc.:** 26 | -------------------------------------------------------------------------------- /legacy_contact/apple_US.md: -------------------------------------------------------------------------------- 1 | **Service:** 2 | * Apple 3 | * https://www.apple.com 4 | 5 | **Account Country / Countries** 6 | * United States of America 7 | 8 | **Account Type:** 9 | * Personal account 10 | 11 | **The Process:** 12 | * https://support.apple.com/en-us/102631 13 | 14 | * On a Mac logged into my iCloud account, I opened the System Settings -> Apple Account -> Legacy Contact setting. I chose a contact and wsa offered to send the legacy contact recovery code to my chosen contact via SMS/iMessage or to print a physical document. I chose to print the physical document which will be stored with other related recovery documents in my safe deposit box. 15 | 16 | **Qualitative assessment of what went well, what went wrong, what would have helped, etc.:** 17 | * This was easier than expected, it took less than 5 minutes while on a flight. 18 | * More than one contact can be added, which is nice. However, it is unclear as the owner of the iCloud account and payer on the account, how or if this works 19 | when my credit card is cancelled and stops paying the monthly fees. This needs to be explored further. 20 | 21 | **Additional Data** 22 | * https://digital-legacy.apple.com/ is used by the legacy contact to gain access to the account. 23 | * https://support.apple.com/en-us/102431 has additional information for survivors. 24 | -------------------------------------------------------------------------------- /legacy_contact/google_US.md: -------------------------------------------------------------------------------- 1 | **Adding a Legacy Contact** 2 | 3 | **Service:** 4 | 5 | * Google 6 | * [https://google.com](https://google.com) 7 | 8 | **Account Type:** 9 | 10 | * Personal Account 11 | 12 | **The Process:** 13 | 14 | * [Google Inactive Account Manager](https://myaccount.google.com/inactive) 15 | * Inactive Account Manager is a way for users to share parts of their account data or notify someone if they’ve been inactive for a certain period of time. You can use this tool to designate a third party, like immediate family members, to receive certain account data in the event of the user's death or inactivity. 16 | * In this tool, the user can 17 | * Choose recipients for data sharing 18 | * Choose which data is shared 19 | * Choose a period of time for inactivity, after which planned actions will take place 20 | * Once the account has been inactive for the specified amount of time, chosen contacts will receive an email with a link they can follow to download the data. 21 | 22 | **Additional Information** 23 | 24 | * In some cases, Google can work with immediate family members and representatives to close the account of a deceased person where appropriate. A full description is available in the [Google Help Center article](https://support.google.com/accounts/troubleshooter/6357590?hl=en) for requests regarding a deceased user’s account. 25 | -------------------------------------------------------------------------------- /legacy_contact/google_workspace_US.md: -------------------------------------------------------------------------------- 1 | **Adding a Legacy Contact** 2 | 3 | **Service:** 4 | 5 | * Google Workspace 6 | * https://workspace.google.com/ 7 | 8 | **Account Country / Countries** 9 | 10 | * USA 11 | * Configured as Google Workspace Business Starter account 12 | 13 | **Account Type:** 14 | 15 | * Personal 16 | 17 | **The Process:** 18 | 19 | * No help documentation found on assigning a legacy contact. 20 | 21 | * In order to minimize the risk of loss of the account, I took the following steps in the console: 22 | * Added a second super admin user to the account 23 | * Added second user to receive billing statements as a Payment Contact under Billing -> Payment Accounts -> More -> Payments Settings 24 | * Paid annually to reduce the risk of the service expiring as soon as the first payment fails 25 | 26 | * Additional ideas to reduce risk: 27 | * Add a second payment option bound to the additional payment contact to allow payments to continue after the primary contact is deceased and the credit card is frozen. 28 | * Develop documentation for the second super admin to take control of the account if the primary contact is deceased. 29 | 30 | **Qualitative assessment of what went well, what went wrong, what would have helped, etc.:** 31 | 32 | * There is no defined process for handling this at Google Workspace. 33 | 34 | **Additional Data** 35 | 36 | * None 37 | -------------------------------------------------------------------------------- /cybersecawareness2025/proposal.md: -------------------------------------------------------------------------------- 1 | As we prepare for [Cyber Security Awareness Month](https://www.cisa.gov/cybersecurity-awareness-month) 2025 (October, 2025), the Death and the Digital Estate CG proposes delivering a white paper and planning resources for managing a digital estate. These resources are planned for release in October 2025 where they can be cross promoted at venues such as the [Internet Identity Workshop](https://internetidentityworkshop.com/) and [Authenticate 2025](https://authenticatecon.com/). 2 | 3 | The planned whitepaper will review the current state of digital estate management. Using the real life examples from DADE CG members, the white paper will document the known current state of digital estate/legacy management, challenges faced by individuals, and identify broad areas for improvement (e.g. legacy account management availability). 4 | 5 | In addition to the whitepaper, we plan to deliver guidance to help individuals develop plans for managing their digital estate. Focusing on common scenarios - accounts with major platforms (e.g. Google, Apple, Microsoft), social media services (e.g. Facebook, Twitter, LinkedIn), and credential managers (e.g. 1Password, Dashlane), and other digital assets (e.g. photos, videos, audio) actionable guidance will be provided to enable individuals to take specific actions to choose how to disposition their digital estates. These assets will be available during Cyber Security Awareness Month and beyond. 6 | -------------------------------------------------------------------------------- /legacy_contact/1password_US.md: -------------------------------------------------------------------------------- 1 | **Adding a Legacy Contact** 2 | 3 | **Service:** 4 | 5 | * 1Password 6 | * https://1password.com 7 | 8 | **Account Country / Countries** 9 | 10 | * United States 11 | 12 | 13 | **Account Type:** 14 | 15 | * 1Password for Families 16 | 17 | **The Process:** 18 | 19 | * 1Password does not offer a mechanism to enable a legacy contact. However, there are two options that exist to support this use case: 20 | * [Emergency Kit](https://support.1password.com/emergency-kit/) can be saved offline and used to recover access to the account. This works for all 1Password accounts. However, the contact must know of the emergency kit and how to use it. 21 | * Add additional family organizers who can manage the account. 22 | * If the account is purchased directly from 1Password, the family organizers can be added to the [Manage Billing group](https://support.1password.com/manage-subscription/). 23 | * If the account payment lapses, a family organizer can [restore a frozen account](https://support.1password.com/frozen-account/). 24 | * If the account is purchased through an app store, family organizers cannot manage billing 25 | * If the account payment lapses through the app store, it must be restored through the app store. 26 | * There does not appear to be a mechanism to move between payment models, this may cause some users to be stuck. 27 | * Risk can be mitigated by paying annually instead of monthly. 28 | 29 | **Qualitative assessment of what went well, what went wrong, what would have helped, etc.:** 30 | 31 | * Additional recovery options are needed for app store based accounts. 32 | 33 | **Additional Data** 34 | 35 | * None 36 | 37 | -------------------------------------------------------------------------------- /cybersecawareness2025/planning_guide_outline.md: -------------------------------------------------------------------------------- 1 | # DADE Planning Guide 2 | 3 | An outline of a planning guide for your digital estate for Cybersecurity Awareness Month 2025. 4 | 5 | ## Overview 6 | 7 | TBD 8 | 9 | ## Getting Started 10 | 11 | - What is your digital estate? 12 | - Why do you need to plan for the management of your digital estate? 13 | - What can go wrong if you don't effectively plan for your digital estate? 14 | 15 | - How to plan 16 | - What are your digital assets? 17 | - Prioritizing digital assets 18 | - Why prioritize? Often, your digital accounts exist in a state where unlocking access to a few key services - usually an email address and phone - can be used to recover access to *other* accounts. 19 | - Everyone is different, but generally the most important assets are your email account(s), mobile ecosystems (mobile phone providers, Apple iCloud/Google), and credential managers (Apple Passwords, Google Password Manager, 1Password, Bitwarden, etc), utilities (land line, home networking via fiber/cable/DSL/sattelite, water, electric, etc.) 20 | - These accounts *usually* unlock access to everything else... but not always. If you have hardware security keys or similar devices... 21 | - Next, cryptocurrencies 22 | - Next up are accounts with large platforms (social media, shopping, search,), digital data including photos, home movies, etc. 23 | - Multiple services may hold photos (e.g. Flickr, Apple Photos, Google Photos, Snapfish, etc.). The same is true for files, and other kinds of digital data. If you have a credential manager, use it to find where your data is stored! 24 | - Alternatively, search your email inbox to find where you have accounts at common platforms.) 25 | - Local data - what exists on your phone, laptop? Is this backed up to the cloud? 26 | - Backups 27 | - Home based (local disk, NAS) 28 | - Online service 29 | - Home network 30 | - Local configuration - networks, WiFi SSIDs and passwords 31 | - Remote configuration via managed provider (e.g. UniFi) 32 | - IoT - light switches, robot vacuums, home video surveillance, automobiles, home solar controllers, doors 33 | - Building the plan 34 | - Create a list following the priority above for recovery as part of your digital estate 35 | - You might not get all the details right at first and that's ok! 36 | - For each element of your digital estate list 37 | - Name 38 | - URL (or other relevant identifier) 39 | - user name 40 | - Where is the credential stored? (e.g. in 1Password? Apple Passwords? Does the account use single sign on, if so from which account? If there's a second factor, what is it?) 41 | - are there any other related credentials? (e.g. KBA secret questions?) 42 | - Does the service offer a legacy contact or other mechanism for delegation of control? 43 | - If so, what was the chosen mechanism? Include URLs or other data as needed. 44 | - Does the service explicitly ban taking over access to a personal account? 45 | - How do you want your account managed by your estate? 46 | - Need to list options here. 47 | - Who will manage your digital estate? 48 | - How will they know your wishes? Have you communicated any recovery mechanisms to them already, e.g. Apple's recovery QR code? 49 | - How will they get access to your passwords, passkeys, OTPs (SMS and TOTP), and other credentials necessary to access your accounts? 50 | - If you store data securely in a safe deposit box, it may not be accessible when needed. Consider how you might be able to store this in a more accessible location, e.g. fireproof safe. (Consult local laws.) 51 | - How will you ensure the manager does not get access to the accounts/data before necessary? 52 | - Have you considered an estate attorney? If so, make sure you share this plan with them. 53 | 54 | 55 | -------------------------------------------------------------------------------- /charter.md: -------------------------------------------------------------------------------- 1 | # Death and the Digital Estate Community Group (DADE CG) Charter 2 | 3 | **Community Group Name** 4 | 5 | Death and the Digital Estate Community Group (DADE CG) 6 | 7 | **Introduction** 8 | 9 | In today's digital age, the internet permeates nearly every aspect of our lives, from social interactions and commerce, to accessing news and entertainment. However, amidst this digital revolution, a critical issue persists: the lack of tools for individuals to determine the fate of their digital accounts and data after temporary or permanent incapacitation or death. While some mechanisms exist, they are inconsistently available and often require individual configuration across various service providers—an arduous task beyond the reach of many. 10 | 11 | This glaring gap underscores the pressing need for more effective mechanisms for individuals to consent to the handling of their digital estate. At its core, this issue transcends mere technological convenience. Managing a human’s digital estate is a matter of human rights—the right of individuals to manage their data and likeness, even when they are no longer able to do so themselves. As stewards of identity innovation , it is our duty to address this fundamental need and enable mechanisms for individuals to maintain agency over their digital legacy. 12 | 13 | 14 | **Deliverables & Organizing Principles** 15 | 16 | The proposed DADE CG will focus on the following deliverables: 17 | 18 | - Document the current state of the art for managing individual choices for handling individuals’ digital estates. Identify and clarify examples of mechanisms currently deployed by platforms, social media services, and other large scale internet systems. 19 | 20 | - Document individuals' experiences with handling the digital estates of others to identify the difficulties they face managing the digital estate of incapacitated or deceased friends, family, and loved ones. These accounts may be anonymized at the discretion of the individuals involved. 21 | 22 | - Document the current state of government regulations, where they exist, for the management of individuals digital estates. 23 | 24 | - Development of use cases for the management of digital estates to include the data stored by, or on behalf of, the user, or containing the users likeness in audio, video, or other digital formats. Develop nomeclature and roles for establishing delegated autorities which operate on behalf of an individual within a defined scope of authority. 25 | 26 | - Identify and document use cases that are out of scope for additional DADE CG effort due to the existence of law or regulation where such use cases are sufficiently established and managed today. 27 | 28 | - Develop educational information to raise awareness of the challenge and empowering individuals to assert control over their digital legacies effectively. 29 | 30 | - Develop proposed high level data flows for a future set of mechanisms to enable a marketplace for management of individuals’ digital estates across providers. 31 | 32 | The following are out of scope for the proposed DADE CG: 33 | 34 | - Development of any protocols related to managing a digital estate. Any such protocol work will be deferred to a future working group. 35 | 36 | The community group will operate under the following Organizing Principles: 37 | 38 | - **Respect:** Death is a subject that touches every human. Yet, humans do not all consider death in the same light. A wide variety of cultural and religious traditions exist worldwide which must be respected and accommodated in all of the proposed CG’s actions and deliverables. 39 | 40 | - **Empowerment through Consent:** We seek to empower individuals to enable informed decision-making regarding the management of their digital estate. The DADE CG will advocate for consent-driven use cases which protect the privacy and security of individuals, living and deceased. 41 | 42 | - **Interoperability and Accessibility:** The CG’s work must promote interoperability among digital platforms to facilitate seamless data management and accessibility across diverse ecosystems, ensuring inclusivity, efficiency, and usability for individuals. 43 | 44 | The DADE CG will operate in English. The work will progress via mailing list and telephone/internet conference calls combined with face-to-face meetings, where possible. We seek a 2 year charter to develop the deliverables identified above. At the end of this 2 year charter, we will assess the state of the DADE CG and determine whether to extend the charter, charter a working group to develop related protocols, or disband the community group. 45 | 46 | **Proposers** 47 | - Dean H. Saxe (Beyond Identity) 48 | -------------------------------------------------------------------------------- /resources.md: -------------------------------------------------------------------------------- 1 | # **Resources for DADE** 2 | 3 | Please add resources and reference material links below. At the moment, these are in no clear order. 4 | 5 | ### Talks About Relevant Topics 6 | 7 | - [Kaliya Young's Talk about Digital Death Day](https://vimeo.com/42481807) 8 | 9 | 10 | - [The Good Death Preso from Summer of Protocols](https://www.youtube.com/watch?v=8sbGALYWcrA) 11 | 12 | ### Standards Related 13 | 14 | - https://kantara.atlassian.net/wiki/spaces/uma/pages/4849814/UMA+legal+subgroup+notes (and items linked therein) 15 | 16 | - https://datatracker.ietf.org/doc/html/rfc8693 (for on-behalf-of semantics) 17 | 18 | ### General Articles 19 | 20 | - [List of services related to death](https://www.thedigitalbeyond.com/online-services-list/) 21 | 22 | - https://sovrin.org/a-deeper-understanding-of-implementing-guardianship/ (and items linked therein) 23 | 24 | - https://www-smbc-co-jp.translate.goog/kojin/digital-safetybox/service/ (Japanese bank service that allows users to store digital data for disclosure to specified relatives after the owner has deceased.) 25 | 26 | - Digital end of life planning from the Japanese National Consumer Affairs Center [Register Article](https://www.theregister.com/2024/11/21/japan_digital_end_of_life/), [Original Source](https://www.kokusen.go.jp/news/data/n-20241120_1.html) 27 | 28 | 29 | 30 | ### **Legal Approaches / Pieces** (formal legal articles from journals, mainly) 31 | 32 | - https://trustandwill.com/learn/what-is-rufadaa 33 | 34 | - [Minors and Digital Asset Succession](https://ilr.law.uiowa.edu/sites/ilr.law.uiowa.edu/files/2022-10/Minors%20and%20Digital%20Asset%20Succession.pdf) 35 | 36 | - [Digital Purgatory and the Rights of the Dead: Protecting Against Digital Disinterment in the Age of Artificial Intelligence](https://download.ssrn.com/24/04/15/ssrn_id4795193_code6259402.pdf?response-content-disposition=inline&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEMj%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLWVhc3QtMSJGMEQCIBa5Ym2DN%2B60iXy0u4y%2BDkLuY8UeAk%2B4a1SuhJYfOI8AAiAh5VAlvQ4Y%2Fbx9PY3R2f77LMVAOt%2BWAHOeJYJUmoKY2yq9BQgwEAQaDDMwODQ3NTMwMTI1NyIMQd9hSFpOwrXluSgPKpoFfusS03ShPt5HUKBeZ4Q%2BhYjx5jGfhxaikoMvFoUqPCUGZD15qhxCcVQAT8c%2B0zSeDQLfHQ8QWVROiLz%2FbL2B4t9pWAAl4O5B%2B6VmdMAcZWHDMEYctdm5qTcOy%2B6LPqy2tzhCR9dwAa9HPy%2Fupx558Q3BSf7%2BOK04s91UEKzn7tKble4WBTERr0fDxfNWqz9cMBy9v1uGkaKFTc0UTVbhjPaoGRO2GZPjn4PsYtkGFEFqkCj6Fk2NGj6IVuRYmu0MLmRPoOfVFJwopS%2B1k5fkatGrm60D3EmIVy8GE1oqnhHp0sK12FZG5idOgNjPclQjRlazTuLaj3rB4LSHhPY0%2Be8ptHxZBRlcTrveCO1Hn74Gl%2FvrgkLjvUMfd0TJwSNztpeKDOWye7NgbFRK1ZDm6UlpbELVFuNgDcEGOj8etFCgpGCaOan6P85DhEoXbgV35wfn4D8TqEUMRgOSotpX3gBwdkiFJ3elCvvFQ2ANjZohjmJW6sruZAruInUwICsq5S9lVlER95GMeXn9CidNU0LhRU5RhcghLWjb3riDEvBgRS8zUHHT7m1%2BTmwfvXnQ%2FWxJLbt1lauizFvBqEZfxkdsh5T%2BxQVPlMuOBK2tT6ywur%2Fw59K8Kt%2FlmcdtBSBk%2F%2FEmL7QTWTPHGOVenshBk8Nqoel2gJXHeI685i%2FF9ffgCctxSnbHJLC1kbGu%2FhwWrYRpgJX3gnsCwQH3BVGZmW%2BCG0daC9n1Q7MIUFVol5PQps87FfRqUpTPozSJxPtVQ8EKYkacx%2BZjoycT0RoxTxLe3pVpY1SasOcZcxx4mpEcHh1EMlgiO%2F9%2FIpXXKvnpFBjMNkNp7M7uHItx457RKbepk5rTwW9Wwi7DyXHyPlaCkbArULaJ1lyQMJbPxLgGOrIBZg0cRiLoH3LJ16o2qQiGMjPDQFVq5y%2BJParN3DH2gLDL9KFJik1NU%2ByMBDz07FxNJL5gKXSb9O%2FcCZ7FWhSVSUykwhL5XoQDrleahs421eta%2FrXXF6pLqKAx5nDca1LoFVdXs3IsnD3l5eU8h%2Be3MuPbIzitedfbfcmLS84dkrbgROsag3YNfV4tqizU5rOiLE22%2F2lHhAppES5SZvFqjnyJCJIUeB0eeZum7w6bx%2Fln4g%3D%3D&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20241017T162718Z&X-Amz-SignedHeaders=host&X-Amz-Expires=300&X-Amz-Credential=ASIAUPUUPRWESWF72PUI%2F20241017%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=abeab5779e79b8cdea3d0d05ba2e40fed3a9a63446ff6db9c4e24f7d275a9581&abstractId=4620092) 37 | 38 | - [Estate Planning for Cyber Property – Electronic Communications, Cryptocurrency, Non-Fungible Tokens, and the Metaverse](https://epj.us/article/94177) 39 | 40 | - [The Social Afterlife](https://jolt.law.harvard.edu/assets/articlePDFs/v33/33HarvJLTech329.pdf) 41 | 42 | 43 | ### Tools/Applications 44 | #### [finaldocx.ca](https://finaldocx.ca/) 45 | A service offered by funeral homes (and others) to help loved ones cleanup the digital footprint and other identity related information. 46 | The service helps send information to the following reducing the need for death certificates and separate forms/requests: 47 | * Notification to Old Age Security Program 48 | * Notification to Service Canada 49 | * Canada Revenue Agency 50 | * HST/GST recalculation 51 | * Canada Pension Plan Death Benefit 52 | * Canada Pension Plan Survivor's Benefit 53 | * Equifax (Credit Reporting Agency) 54 | * Cancellation of Provincial Health Card 55 | * Cancellation of Provincial Driver's License 56 | * Cancellation of Provincial Photo I.D. card 57 | * Notification to Social Insurance Program 58 | * Transfer rewards cards 59 | * Provincial Outdoors Card 60 | * Blue Cross 61 | * Cancel or transfer utilities 62 | ** Hydro 63 | ** Telephone 64 | ** Cable 65 | ** Gas 66 | * Cancel Mobile Phone 67 | * Cancel Credit Cards 68 | ** Visa 69 | ** Mastercard 70 | ** Amex 71 | ** Credit Union 72 | ** Retail Cards 73 | * Nexus Travel Card 74 | --------------------------------------------------------------------------------