Plan for ordinary unavailability

You do not need a medical prediction to justify a recovery plan. You may be travelling, unavailable, unable to find a device or simply unable to recall a rarely used secret. Your chosen person may never have known that secret in the first place. A system that depends entirely on one person remembering everything has a practical continuity gap.

Writing a backup creates a different responsibility: protecting it from disclosure and making its location known to the right person. The answer is a deliberate storage and access arrangement, not a promise that memory or a particular material cannot fail.

Keep different kinds of secrets distinct

A wallet recovery phrase, an optional wallet passphrase, a device PIN, a password-manager master password and a ZeroLatch Private secret can serve different purposes. Label the instructions clearly without putting every secret into one general document. Never substitute a made-up sentence for a wallet-generated recovery phrase.

Use the wallet or password manager’s official backup procedure. Check whether imported accounts, additional passphrases or recovery shares need separate records. Avoid cutting words into improvised fragments; that can create a backup that is harder to restore without providing the security you expect.

Choose a location and an access route

Consider who can physically reach the backup, what protects it from theft or damage and what happens if the usual location becomes unavailable. Durable storage can still be lost or disclosed. An encrypted copy also requires a way to recover its password without depending on the same failed device.

Discuss the arrangement with the intended helper. Use a harmless test example to check that the labels and sequence make sense. Keep a dated record of the test and review it after changes to the device, secret, recipient or storage location. Do not share live recovery words with a support agent to prove the backup works.

Give a future recipient a clear starting point

ZeroLatch can deliver a scoped inventory and instructions after a missed check-in and safety period. It does not transfer assets, establish legal authority or confirm death. Simple permits authorised service-managed key recovery; Private requires a separate password or ZeroLatch recovery phrase. Neither option replaces an independent backup or a real recipient rehearsal. Start with harmless information and read the security model and backup checklist.

The first handoff can simply identify the inventory, document location and trusted contact. It should tell the recipient when to seek help and which unsolicited recovery messages to ignore. Planning for access should preserve privacy and the legal authority needed to act.