Guides

How to make a dead man's switch: code it, use built-in tools, or choose a service

By the myAngelVault team · 9 min read

Listen to this article · 9 min

There are three real ways to make a dead man’s switch: write your own script (a small program that releases your messages or files when you stop checking in), use inactivity features built into tools you already have (like Google’s Inactive Account Manager or a password manager’s emergency access), or use a dedicated service that treats the switch as a multi-step safety process. The code is the easy part — the hard problems are false triggers, deliverability, and the years of maintenance a homemade switch needs from the one person who may no longer be there to provide it.

Full disclosure: we build myAngelVault — the third route on this page. The comparison below is an honest one all the same. Already know you want a service? Skip to what to demand from one →

First, be clear about what you’re building

Strip away the implementations and every dead man’s switch is the same three decisions. What counts as a sign of life? A reply to an email, a click on a link, a login, an app on your phone confirming quietly in the background. How much silence means something is wrong? A week? A month? A season? And what happens then — an alert to someone, a file released, a set of letters delivered?

Everything below is just a different way of answering those three questions. And one of them is far harder than it looks: the silence rule. People land in hospital and come home. Phones drown. Grandparents take seven-week cruises with no data plan. A switch that treats every quiet stretch as the worst case will eventually fire while its owner is alive — which, if what it releases is a farewell letter, is the one failure you cannot take back.

Are dead man’s switches real?

Very — you have probably used one this week. The safety key that stops a treadmill when it pulls free, the trigger a chainsaw needs held down to run, the lever a train driver keeps pressed so the engine halts if they let go: all dead man’s switches, all built on absence of a signal triggers a protective action. Digital versions are just as real: journalists protect their source archives with them, system administrators guard servers against being the single point of failure, and families use gentler versions to make sure letters and photos actually reach the people they were prepared for. If you want the full story of how the idea traveled from locomotives to inboxes, we’ve written a separate guide to what a dead man’s switch is.

Route 1: Code your own

The engineer’s route, and as a weekend project it’s genuinely satisfying. In words rather than code, the build is: a small service that hears from you (an endpoint you ping, an email you reply to, a link you click); a scheduled job that measures the silence against your rule; and an action — usually an email through a sending API, perhaps with encrypted files attached or linked from storage. Any capable developer can have a prototype running in a day or two.

Before you trust it with anything that matters, walk through what the prototype doesn’t solve:

  • The maintenance paradox. Your switch needs hosting bills paid, API keys rotated, and breaking changes patched — for years, possibly decades. It demands exactly the kind of ongoing care its owner will, by definition, one day stop providing. A homemade switch with a single administrator quietly rots, and nobody is notified when it does.
  • Deliverability. An email fired from a personal server, from a domain with no sending reputation, has a real chance of ending its journey in a spam folder. For the most important message you will ever send, that’s not a rounding error.
  • The bare timer problem. “No ping for 60 days → send everything” is a countdown, not a safety process. A trustworthy switch escalates first: it tries hard to reach you, over multiple channels and weeks, before it so much as considers acting.
  • The secrets question. If the payload is encrypted (it should be), where does the key live, and how does it reach your recipients — but nobody else, and not too early? This is the part of the design most weekend builds quietly skip.

An honest verdict: if you’re a tinkerer protecting data — server credentials, an archive, instructions for a colleague — a self-built switch with eyes open is a reasonable choice. If what it guards are words for the people you love, the failure modes above land on them, not on you.

Route 2: No new code — the built-in options

Several tools you may already use have a dead man’s switch hiding inside, and they deserve an honest look.

Google’s Inactive Account Manager is the best of them: free, well built, and worth turning on today if you live in Gmail and Google Photos. After an inactivity period you choose (3–18 months), Google can notify up to ten trusted contacts and share selected data with them. Its limits are the flip side of its simplicity: it watches one account, covers only Google data, waits months by design, and no human being confirms what actually happened before it acts. And what your contacts ultimately receive is access to data — the same bundle for everyone, rather than words prepared for one person in particular.

Password managers’ emergency access (1Password, Bitwarden, and others offer versions of this) lets a trusted person request access to your vault; if you don’t veto the request within a waiting period you set, they get in. For making sure passwords and account access outlive you, this is a genuinely good mechanism. What it hands over, though, is a password list — not the letter you would have wanted to send with it.

The endlessly postponed scheduled email — write the message, schedule it a month out, keep pushing the date back — is the most popular trick and the most fragile. The burden points the wrong way: the system doesn’t ask “are you gone?”, it asks “did you remember your chore?” One busy month and your most sensitive email sends over a scheduling slip. We take this apart, along with the other email approaches, in our guide to dead man’s switch emails.

Route 3: A dedicated service

The third route is letting a service whose entire job is this problem run the switch for you. The good ones differ from every option above in one fundamental way: they treat release not as a timer expiring but as the last step of a safety process. Signs of life ride on normal living instead of being a chore. A planned absence is a setting, not a gamble. Silence triggers escalating attempts to reach you first, over weeks. A human being you chose confirms what actually happened before anything is released, and a single click from you stops the whole process at any stage.

We’ve published a six-question checklist for evaluating any service in this category — ours included — and an honest side-by-side comparison of the 2026 services, competitors and all. The short version: demand effortless check-ins, escalation measured in weeks, a human in the loop, instant cancellation, recipients who need nothing but an inbox, and a written answer to the question every long-term service owes you: what happens if you disappear?

myAngelVault is our answer to that standard. Your letters, photos, and practical guidance wait in a private vault, organized into envelopes for the people you choose — each envelope in your own voice for that one person, because what you want to say to your children is not what you want to say to your oldest friend. And the vault grows along with your life: adding a letter, a photo, or a voice note from the mobile app takes a minute. Visiting the site or letting our mobile app confirm quietly in the background counts as your sign of life; Travel Mode covers the weeks you plan to be away. If everything goes quiet, delivery comes only after escalating check-ins, confirmation from a trusted person you named — your Guardian Angel — and a final safety check. And because we’re asking for trust measured in decades, our Trust & Longevity page answers the uncomfortable questions in writing, including a six-month continuity commitment and a vault you can download in full at any time.

Which route is yours?

Protecting data, and comfortable maintaining software for years? Build your own — with the checklist above taped to the monitor. Life mostly inside Google? Turn on Inactive Account Manager today; it costs nothing and covers real ground. Add your password manager’s emergency access and the practical side of your digital life is in decent shape.

But if what you’re really trying to deliver are words — the letters, the photos, the things you’d want said in your own voice — the bar is different, because the cost of both failure modes is carried by the people you love. Start with the honest comparison of ways to leave messages for your loved ones, and when you want to see a switch built as a safety process rather than a timer, myAngelVault is ours.

myAngelVault

Some things are too important to leave to chance.

myAngelVault keeps your words safe and delivers them to the people you love — only when it truly matters.

Start your vault — free 30-day trial →

Questions about privacy and safety first? Read how we protect what you entrust to us.