Should you put passwords in a dead man's switch?

A dead man's switch can support emergency password access, but it should not become an unstructured copy of every live credential. Start with an account inventory, provider-approved recovery methods, instructions, and the minimum recovery material the recipient genuinely needs.

Passwords change. Passkeys may be device-bound. Two-factor authentication can block a correct password. Financial, workplace, and health accounts may prohibit credential sharing. A usable plan has to explain the complete recovery path and the authority required to use it.

For many accounts, the safest handoff is not “here is my password.” It is “here is the provider, account identifier, recovery contact, authoritative document, and approved process to follow.”

Password manager versus dead man's switch

The tools solve different problems.

A password manager • Stores and fills everyday credentials • Is designed for frequent updates • May offer family or emergency-access features • Usually relies on manager-specific recovery

A dead man's switch • Delays a selected handoff until inactivity • Is designed for continuity and recipient context • Can carry instructions outside one password ecosystem • Can point to several providers and physical records

Use the password manager as the working system of record. Use a dead man's switch as a conditional map to the accounts, emergency kit, provider recovery process, and any separately protected factors an authorised recipient may need.

If your password manager already provides suitable emergency access, configure and test it. Do not duplicate secrets merely to use another tool.

What password information should the delivery contain?

Prefer:

• A list of critical accounts and why they matter • The email address or username associated with each account • The password manager and emergency-access process in use • Locations of printed emergency kits, hardware keys, and sealed records • Which device receives authenticator codes • Where 2FA recovery codes are protected • Provider-specific legacy-contact settings • Instructions for contacting the executor, solicitor, employer, or provider • Explicit notes about accounts the recipient must not access without authority

Only include a live password when it is necessary, permitted, and protected appropriately. Separate the most sensitive recovery factors instead of putting the username, password, 2FA secret, and recovery code in one file.

How do passkeys and two-factor authentication change the plan?

A password alone may be useless if the recipient does not have the device, passkey, hardware security key, authenticator seed, phone number, or recovery code.

Document:

  1. Which devices hold passkeys
  2. Whether passkeys sync through Apple, Google, Microsoft, or a password manager
  3. How the device itself can be lawfully accessed
  4. Where spare hardware keys are stored
  5. Which phone number or email receives recovery messages
  6. Where one-time recovery codes are kept
  7. What the provider requires after death or incapacity

Never assume biometrics are an inheritance plan. Devices can require the passcode after restart, inactivity, security events, or operating-system rules.

How do you protect the recovery secret?

For assisted recovery, understand exactly which provider systems and authorised processes can recover the key.

For self-custody recovery, preserve the code through an independent channel: for example, a sealed envelope with estate records, an appropriately controlled safe, or another arrangement reviewed with your legal and security advisers. Do not place the only recovery code inside the encrypted delivery.

Avoid “clever” schemes that nobody else can reconstruct. A recovery design that defeats the executor is not more secure; it is permanent loss. Document the process, test it with sample material, and ensure the recipient knows where to ask for help.

Password dead man's switch threat model

Consider:

• Premature access: Can the recipient or provider see secrets while you are active? • Account takeover: What can an attacker do after compromising your email or ZeroLatch account? • Recipient compromise: What happens if their inbox or device is breached? • Provider failure: Can you move or reconstruct the plan if a service closes? • Stale credentials: How quickly do included passwords become wrong? • Coercion and legal process: Who can compel or authorise access? • Permanent loss: What happens if a self-custody code disappears? • Malicious files: Can the recipient safely inspect attachments?

The right design is rarely one container with every secret. Use separation, minimum disclosure, expiry, recipient verification, independent legal authority, and rehearsed recovery.

Dead man's switch for passwords checklist

  • Turn on provider-native legacy or emergency access where suitable
  • Maintain a current account inventory
  • Identify the password manager and its emergency kit
  • Document passkeys, 2FA, devices, phone numbers, and hardware keys
  • Remove passwords the recipient does not need
  • Separate high-impact recovery factors
  • Confirm the intended recipient and their email address
  • Explain the legal or provider process for restricted accounts
  • Test decryption and file integrity with synthetic data
  • Review after changing password managers, devices, email, phone number, executor, or family circumstances