Family email
Site: mail.google.com
Username or email: alex@example.invalid
Where the password is kept: __________________________________
US Tech Automations · Private family copy
Heir Packet
This is an account list, not access permission or a password backup. Start with the owner’s instructions. Use official recovery and bereavement routes; this packet does not unlock an account or change ownership.
Account count: 8. Review UNKNOWN.csv for skipped rows and missing details. The separate accounts.csv holds this account list. Groups are suggestions; check them before sharing. Print this file with your browser’s Print command.
Arrange access while you can
Use your password manager’s own arrangements below. Write only where the separate access instructions are kept, never passwords or recovery codes, on this packet. Plans and features can change; the official links need internet when opened. Help checked 2026-10-03.
- Bitwarden: In Emergency Access, invite a trusted person, have them accept, then confirm them. Set a wait and view or takeover access. Eligible paid plans can grant it; the contact requests access from their own vault.
Export layout: Bitwarden. See the password-manager reference at the end for other managers and generic CSVs.
Trusted person: ____________________
Manager and location of separate access instructions: ____________________
Date reviewed: ____________________
No legal advice. Follow the provider’s current requirements.
Apple account
Site: icloud.com
Username or email: alex@example.invalid
Where the password is kept: __________________________________
Banking and money
Household banking
Site: bank.example.invalid
Username or email: alex.family
Where the password is kept: __________________________________
Phone
Mobile phone
Site: phone.example.invalid
Username or email: family@example.invalid
Where the password is kept: __________________________________
Shopping
Shopping account
Site: www.ebay.com
Username or email: family-shop
Where the password is kept: __________________________________
Social
Social account
Site: www.pinterest.com
Username or email: alex-art
Where the password is kept: __________________________________
Work
Work account
Site: github.com
Username or email: alex-work
Where the password is kept: __________________________________
Other
Library account
Site: library.example.invalid
Username or email: alex-reader
Where the password is kept: __________________________________
Provider death or inactivity steps
Matched by website domain only. A missing match or UNKNOWN is not proof that a provider has no process. Check official help before acting. These summaries do not grant account access.
Beforehand, configure Inactive Account Manager and choose the data and contacts. After a death, the family can use Google’s deceased-user request process for closure, funds or data. Google does not supply passwords; requests are reviewed.
https://support.google.com/accounts/answer/3036546
https://support.google.com/accounts/troubleshooter/6357590
Official help checked 2026-10-03.
eBay
Open eBay’s deceased-member help page and use its report form. Follow the prompts to identify the account and explain the request.
https://www.ebay.com/help/account/changing-account-settings/reporting-death-ebay-member?id=5574
Official help checked 2026-10-03.
Contact Pinterest through its official help process to request deletion of a deceased family member’s account, with verification such as an obituary or death certificate. Pinterest does not disclose personal or login information.
https://help.pinterest.com/en/article/deactivate-or-close-your-account
Official help checked 2026-10-03.
Apple
Beforehand, add a Legacy Contact in Apple Account settings and arrange to keep the access key separately. The contact requests access with that key and a death certificate. Keychain passwords, payment details and passkeys are excluded.
https://support.apple.com/en-us/102631
Official help checked 2026-10-03.
4 account(s) did not match the provider directory. Find the company’s official help from its known website; avoid unsolicited recovery offers.
Password-manager reference
- Bitwarden: In Emergency Access, invite a trusted person, have them accept, then confirm them. Set a wait and view or takeover access. Eligible paid plans can grant it; the contact requests access from their own vault.
- 1Password: Prepare the separate Emergency Kit using 1Password’s instructions, and keep it securely accessible to your trusted person. It contains secrets: never attach it to this packet. This is not an automatic timed handover.
- LastPass: In your vault’s Emergency Access section, choose a trusted LastPass user and a waiting period. Arrange acceptance ahead of time. The trusted person later requests access from their own vault. Check plan eligibility.
- Proton Pass: Proton’s paid-plan Emergency Access is set in account Recovery settings. Add a trusted Proton contact and choose the wait. The contact later requests access from their Recovery settings. Check any extra Pass password arrangements separately.
- Apple Passwords: Apple Legacy Contact covers eligible Apple data, but NOT Keychain passwords or passkeys. Set up Legacy Contact in Sign-In & Security for eligible data; arrange password access separately.
- Chrome / Google Password Manager: Configure Google Inactive Account Manager for the eligible data and contacts it lists. Do not assume it hands over your saved passwords. Keep separate password-access instructions in a secure place.
- Microsoft Edge: The export guide is not an emergency-access feature. Read Microsoft’s deceased-account guidance and arrange separate password-access instructions while you can. This packet cannot unlock Edge.
- Firefox: The export guide documents an unprotected CSV, not a legacy handover. No automatic emergency-access process is confirmed here. Arrange access instructions separately; never leave the exported CSV for your family.
https://support.mozilla.org/en-US/kb/export-login-data-firefox
- Dashlane: No automatic legacy-access process is confirmed here. Make separate access arrangements with your trusted person. Its CSV export is unprotected and must be deleted after use.
https://support.dashlane.com/hc/en-us/articles/32905278138002-Export-your-Dashlane-data-to-a-CSV
Remove the unprotected export
Delete the original export after checking your packet. On Windows, select the export in File Explorer, press Shift+Delete and confirm. On Mac, move it to Trash and empty Trash. On Linux, delete it and empty Trash. Also remove any Dashlane export ZIP and extracted export folder, and any copies in synced folders or backups you control. Deleting is not a guarantee of secure erasure on SSDs or backups. Keep exports off shared computers, email and cloud-synced folders. The packet still reveals account names and usernames: store it privately.
The importer skips secret columns while reading. Raw bytes briefly pass through browser memory; JavaScript cannot promise secure memory erasure. Secrets placed in a name, site or username field can evade column filtering. Review the account list privately before sharing.