Cryptocurrency Seed Phrases & Private Keys

A seed phrase (12 or 24 words) gives complete control of a cryptocurrency wallet. If intercepted in transit, anyone can drain the wallet instantly and irreversibly. Unlike passwords, seed phrases cannot be changed or revoked.

Safer alternatives:

• Location instructions: "The seed phrase is engraved on a metal plate in the fireproof safe. Combination is [X]. The safe is in [location]."
• BIP39 passphrase split (25th word): Protect the wallet with a passphrase. Store the seed in Break Glass, store the passphrase in a physical safe or with your lawyer. Both are needed — neither alone is useful.
• Multiple approvals: Require 2 or more trusted contacts to agree before the scenario activates. No single person can trigger your plan alone — even if one person's PIN is compromised.
• Hardware wallet + PIN: Leave the hardware wallet (Trezor/Ledger) with the recipient. Use Break Glass to send the PIN and recovery instructions. The physical device plus the PIN are both needed.

Passwords & Master Passwords

Passwords give direct access to accounts. A master password for a password manager exposes every credential stored in it.

Safer alternatives:

• Password manager emergency access: 1Password, Bitwarden, and LastPass all offer emergency access features. Set up a trusted contact who can request access after a waiting period. Send instructions via Break Glass: "Accept the emergency access request in Bitwarden."
• Emergency Kit: 1Password generates a downloadable Emergency Kit PDF. Print it, store it in a safe. Use Break Glass to say where the kit is.
• Physical channel for master password: If you must share the master password, do it via a physical channel (sealed letter in a safe deposit box), not email.

Bank Account & Financial Details

Full bank account numbers, routing numbers, and credit card numbers can enable unauthorized transfers and fraud. Credit card networks explicitly prohibit transmitting full card numbers via email.

Safer alternatives:

• Bank contact info: "Contact Sarah at ANZ, phone [number]. Reference account ending in 4567. She has authorization to assist."
• Sealed envelope: "Bank details are in the sealed envelope in the safe deposit box at [bank], box number [X]."
• Partial reference only: Share the last 4 digits for identification, never the full number.
• Power of attorney: Set up a financial power of attorney with your bank. Send the POA activation instructions via Break Glass.

Government ID Numbers

Social Security numbers, passport numbers, tax file numbers (IRD in NZ), and driver's license numbers enable identity theft. Unlike passwords, these cannot be changed once exposed.

Safer alternatives:

• Location instructions: "Passport is in the top drawer of the filing cabinet. IRD letter is in the blue folder."
• Partial reference: "IRD ending in 678" — enough for identification but not enough for fraud.
• Professional referral: "Contact our accountant [name] at [firm] — they have all tax records on file."

API Keys & Access Tokens

API keys grant programmatic access to services. Exposed keys can be used to access data, incur charges, or compromise infrastructure. Keys found in email are routinely harvested by automated scanners.

Safer alternatives:

• Revocation instructions: "Revoke all API keys and generate new ones. Here's how: [steps]." Treat any emailed key as compromised.
• Password manager reference: "API keys are stored in the password manager under [service name]. Use emergency access to retrieve them."
• Key rotation plan: Include instructions to rotate all keys after access transfer, not just the keys themselves.

Cryptographic Private Keys (SSH/GPG)

SSH and GPG private keys grant access to servers, signing authority, and encrypted communications. A leaked SSH key is equivalent to giving someone root access.

Safer alternatives:

• Hardware security keys: "SSH keys are on the Yubikey in my desk drawer. The PIN is [X]." The physical device is required.
• Revocation + regeneration: Send the GPG revocation certificate and instructions to generate new keys, not the private key itself.
• Access transfer: "Contact [sysadmin] to set up new SSH keys on the server. My access should be revoked."

2FA Recovery Codes

Two-factor authentication recovery codes bypass 2FA entirely. If intercepted alongside a password, they defeat the purpose of two-factor authentication.

Safer alternatives:

• Password manager storage: Store recovery codes in your password manager and set up emergency access for your trusted contact.
• Physical storage: "2FA recovery codes are printed and stored in the safe, behind the insurance documents."
• Separate channels: If you must share codes, send them via a different channel than the password (e.g., password via Break Glass, codes in a physical letter).

Managed vs Manual Distribution

Each contact in Break Glass can be set to "managed" or "manual" communication mode. This controls how Break Glass interacts with them.

When to use managed:

• Convenience: Break Glass emails activation links, recovery notifications, and annual health check-ins directly. Best for most contacts.
• Automated invitations: Trusted contacts receive email invitations and can accept or decline their role. You can track who has been contacted and who has confirmed.

When to use manual:

• High-security situations: You distribute activation cards and PINs in person or via a separate encrypted channel (Signal, sealed envelopes).
• Air-gapped contacts: The contact doesn't use email regularly or prefers not to receive automated messages from your security systems.
• You verify manually: You'll get reminders to verify manual share holders yourself. Contact them directly to confirm they still have their shares.

Best practices for share distribution:

• Store shares securely: Password manager, safety deposit box, or sealed envelope in a fireproof safe. Never in plaintext on a phone or sticky note.
• Never send shares and PINs through the same channel. If the activation link goes via email, share the PIN in person or via a separate app.
• Tell holders what to expect. Explain that they may receive an annual check-in email, and that in an emergency they'll need to visit a URL and paste their share.

Location Tracking for Missing Person Scenarios

If you have a scenario for going missing or disappearing, include a live location sharing link in your message. When the scenario activates, recipients can track your last known position without needing to log into your accounts.

Recommended services (recipient needs NO account):

• Google Maps location sharing (recommended): Open Google Maps → tap your profile → Location sharing → Share location → "Until you turn this off" → Copy link. Paste the link into your message. Anyone with the link sees your live position in a browser — no Google account, no app, no MFA required.
• Glympse: Generates a shareable URL showing live location. No account needed to view. Good for time-limited sharing during travel.
• OwnTracks (self-hosted): If you run your own OwnTracks server, create a public "view" URL. Fully self-hosted and private — no third-party dependency.

How to set it up:

• Set sharing to "until you turn it off" — not a time limit. The link stays active indefinitely so it works whenever the scenario activates.
• Test the link in an incognito browser — verify it shows your location without being logged into any account.
• Include it in your "Missing" scenario message with context: "My live location can be tracked at [link]. This updates in real-time as long as my phone has battery and signal. Last known location is shown even if the phone goes offline."
• Include backup info too: Last known travel plans, hotel booking confirmations, flight numbers, car rental details, and contacts who saw you last. Location tracking alone may not be enough if your phone is destroyed.

General Principles

• Never put sensitive information in a will. Wills become public documents during probate. Anyone can read them.
• Use the "location instructions" pattern. Tell recipients WHERE to find the information, not WHAT it is. The sensitive information never touches the internet.
• Split sensitive information across channels. Half digital (Break Glass), half physical (sealed letter, safe deposit box). No single point of compromise.
• Test your plan. Verify your recipients know what to do. Send a test notification. Walk them through the process before it's needed for real.
• Review and update regularly. Accounts change, keys rotate, people move. Review your scenarios at least annually.
• Use the Scenario Runbook. Each scenario in Break Glass has a "How It Plays Out" view. Review it to confirm everything is complete and correct.