Accounts
- Primary email
- Password manager
- Banking and billing
- Cloud and domain accounts
Create a safe access plan for accounts, devices, documents, and trusted contacts without typing secrets into a web page.
Plan status
4 priorities
4 risk items selected. No secrets are required.
Core recovery
Covered
Vault and email usually control the rest.
Trusted access
Unassigned
Use roles and approval rules instead of secret sharing.
Risk level
High
Reduce risks before saving the plan.
This page is for pointers, owners, roles, and steps. Add raw passwords, recovery codes, private keys, seed phrases, and ID numbers only inside your trusted vault or legal workflow.
Copy this into your private vault, then add sensitive details there. The output is generated locally in your browser.
# Emergency Access Checklist Use this as a safe planning document. Do not add passwords, recovery codes, private keys, seed phrases, document numbers, or account security answers. ## Plan context - Scope: Household - Scenario: Preparedness - Trusted contact or role: Name a trusted contact or role - Secure storage location: Name the vault or secure location - Next review date: Set a review date ## First priorities 1. Password manager or vault - Document the vault name, owner, trusted-contact path, and where an approved person should start. Do not write the master password here. 2. Primary email and recovery inbox - List the recovery inbox, recovery phone owner, and identity proof needed for reset. Keep actual backup codes in the vault. 3. Phone, laptop, and trusted devices - Record device owners, where spare devices or hardware keys live, and who can approve carrier or device recovery. 4. Two-factor and backup methods - List authenticator locations, hardware-key owners, and backup-code storage location without copying the codes into this plan. ## Risk checklist - [ ] Only one person knows where access lives Fix: Name at least one trusted backup contact and document when they are allowed to act. - [ ] Devices cannot be unlocked by an approved person Fix: Confirm approved recovery paths for phone, laptop, hardware keys, device backups, and carrier account ownership. - [ ] 2FA backup methods are not documented Fix: Record where backup codes or hardware keys are stored, who owns them, and how to verify they still work. - [ ] Trusted contact authority is unclear Fix: Write down who can approve emergency access, what proof is required, and what access must be removed afterward. ## Safe handoff rules - Share access through the vault or legal process instead of copying secrets. - Keep temporary exports out of email, chat, screenshots, shared drives, and ticket systems. - Remove emergency access after the incident, role change, or executor task is complete. - Review the plan after changing phones, email, 2FA, vaults, executors, or trusted contacts. Generated locally by https://passlock.to/tools/emergency-access-checklist
Start with the vault, primary email, phone, and 2FA. Those usually unlock the rest of the recovery chain.
No. Use this page to build the structure. Put secrets only inside the trusted vault or legal process that will store the final plan.
Use a named trusted contact, executor, admin, or role with clear approval rules and a path for removing access later.
Review the password manager, primary email, phone, 2FA backup methods, financial access, and identity or ownership documents.
Passlock for Mac · $14 lifetime
The browser is fine for one-off checks. The app keeps your passwords, passkeys, and notes locked behind your Mac — offline by default, no cloud account, no subscription.
Vault
All items
Bank · login
support@bank.com
iCloud
you@icloud.com
GitHub
@you
Email · personal
you@kitze.io