Dead man's switch email: how to send a message if something happens to you

Full disclosure: we build myAngelVault — a dead man’s switch email built to the standard this guide describes. Past the DIY options already? Skip to what a safe version needs →

Every way to set one up, at a glance

You’ll see it spelled dead man’s switch email, dead man switch email, or deadman switch email — it’s the same idea, borrowed from the train controls that stop the engine when the driver lets go. Here are the options side by side; each is explained, with its breaking point, further down.

Why email is the right delivery channel

Of all the ways a message can outlive its sender, email has a quiet advantage: the people receiving it need nothing special. No account to create, no app to install, no fee to pay, no password to remember at the worst possible moment. An inbox they already check every day is enough. That is why almost every serious approach to leaving messages behind — from a homemade script to a dedicated service — ultimately arrives as an email.

The hard part was never the sending. The hard part is the trigger: how does the email know it’s time? Get that wrong in one direction and your words never arrive. Get it wrong in the other direction and your farewell letter lands while you’re sitting on a beach with a dead phone battery. Everything that follows is really about that one question.

The DIY versions — and where each one breaks

1. The endlessly postponed scheduled email

The simplest trick: write the message, schedule it a month ahead, and keep pushing the date back every few weeks. If you ever stop pushing, it sends. The flaw is that the burden points the wrong way — the system doesn’t ask “are you gone?”, it asks “did you remember your chore?” One busy month, one long illness that has nothing to do with dying, one forgotten calendar reminder, and the most sensitive email of your life goes out over a scheduling slip.

2. The script on a server

The classic engineer’s answer: a small script checks for a periodic sign of life — a click, a reply, a login — and mails everything out if the signal stops. As a weekend project it’s genuinely elegant. As something your family depends on, it has a structural problem: the switch needs exactly the kind of maintenance its owner will no longer provide. Servers get decommissioned, hosting bills stop being paid, API keys expire, email providers tighten their rules — and a self-hosted script silently rots. There is a certain irony in guarding against your absence with a system whose only administrator is you.

Deliverability is the other quiet killer. An email fired from a personal server, from a domain with no sending reputation, has a real chance of arriving in spam — or not at all. For a newsletter that’s an inconvenience. For the last message you will ever send someone, it’s not a risk worth taking.

3. The draft someone is supposed to find

A letter saved in Drafts, a document shared with a spouse, an “open in case of emergency” note. No false-trigger risk — but no trigger at all. Delivery depends entirely on someone knowing the message exists, remembering it during the hardest weeks of their life, and still having access to wherever it lives. Ask anyone who has settled a loved one’s affairs how reliably that chain holds.

4. Google’s Inactive Account Manager

Google’s built-in option deserves an honest mention, because it’s free and well made: after a period of inactivity you choose (3–18 months), Google can notify up to 10 trusted contacts and share selected data with them. If you live in Gmail and Google Photos, turn it on — it costs nothing and covers real ground. Its limits are just as real: it watches one account’s activity, not you; it covers only Google data, not the letters you’d actually want to write; the waiting period is measured in months; and no human being ever confirms what actually happened before it acts.

The false trigger is the whole problem

Every version above rests on the same assumption: silence means the worst. But silence almost never does. People spend a month in hospital and come home. Phones drown. Grandparents take seven-week cruises with no data plan. Accounts get locked. We’ve written about this in depth in our guide to dead man’s switches, but the email case makes it unusually painful: a false trigger doesn’t just leak data, it delivers grief. A farewell email arriving while you’re alive wounds exactly the people it was written to comfort — and no follow-up message fully takes it back.

So the design goal for a trustworthy dead man’s switch email is not speed, and not cleverness. It is certainty before sending — being slow on purpose, biased toward the assumption that you are fine, and acting only when every gentler explanation has been checked and exhausted.

What a safe version needs

• Signs of life that ride on normal living. Opening a website, an app on your phone quietly confirming in the background — not a manual chore you must remember forever.
• A planned-absence setting. A long trip should be a checkbox, not a gamble.
• Escalation measured in weeks. Before anything is sent to anyone else, the system should try hard to reach you — repeatedly, over multiple channels, with plenty of time to answer.
• A human decision before release. Someone you chose confirms what actually happened, so that automation never makes the final call alone.
• Cancellation with a single click, from any stage, at any time.
• Sending infrastructure that actually delivers — authenticated senders and a real reputation, so the most important email you’ll ever send doesn’t end its journey in a spam folder.
• An honest answer to “what if the service itself disappears?” Anyone asking you to trust them for decades owes you that answer in writing.

How to set up a dead man’s switch email, step by step

Whatever tool you end up choosing, the work happens in the same order. Doing it in this order also keeps you from spending an evening on a mechanism before you know what it has to carry.

1. List the people. Not “my family” — names. A partner, each child, a sibling, the friend who will end up handling the practical side. Each one gets their own message.
2. Write the messages before you pick the tool. The words are the part that matters and the part people put off. The next section covers what to put in them.
3. Choose the trigger. Use the table above: how long you could plausibly be offline, and whether a human should confirm before anything is sent.
4. Turn on Google’s Inactive Account Manager anyway. It’s free and covers a different problem — your Google data. In your Google Account, under Data & privacy, look for Make a plan for your digital legacy: pick a waiting period, confirm the phone number and email Google will use to check on you, add up to 10 trusted contacts and choose what each can access, and decide what should happen to the account afterwards.
5. Test the delivery. Send a harmless test to yourself and to one person you trust, and check it arrives in the inbox rather than spam — and that attachments open on a phone.
6. Tell one person the plan exists. Not the contents — just that there is a plan, and who to contact. It turns a hidden mechanism into one somebody can vouch for.
7. Put a yearly review in your calendar. Email addresses change, children grow up, relationships shift. A message addressed to an inbox that closed four years ago never arrives.

What to write in it

The mechanism gets the message there; the message is what the person keeps. A few things make the difference between an email that helps and one that only shocks:

• Open gently. The first lines are read in the moment the person understands what this email is. Start with their name and a sentence that tells them, kindly, why it has arrived now.
• One person, one message. A group email to “everyone” ends up saying nothing to anyone. What you want your daughter to hear is not what your brother needs to know.
• Say where things are — not the secrets themselves. Point to the folder, the drawer, the lawyer, the password manager’s emergency access. Never put passwords, PINs, or full account numbers in an email: it ends up copied across inboxes, phones, and shared computers.
• Leave room for the personal. A memory you share, what you’re proud of, permission they might need — to sell the house, to stop keeping the tradition, to be happy again. These are the lines people reread for years.
• Keep attachments light. Most email providers reject attachments above roughly 20–25 MB, so a video sent as an attachment may simply bounce. Link to large files instead, or use a service that delivers them through a secure page.

How we built ours

myAngelVault is, at its heart, a dead man’s switch email built to the standard above. Your letters, photos, and practical guidance wait in a private vault, organized into envelopes for the people you choose. Normal life — visiting the site, our mobile app checking in silently — counts as your sign of life, and Travel Mode covers the weeks you plan to be away. If everything goes quiet, delivery is the last step of a long chain: a planned-absence check, escalating check-in messages over weeks, confirmation from a trusted person you named — your Guardian Angel — and a final safety check. Only then do the envelopes go out, by email, to people who need nothing but their inbox. Any single click from you stops the entire process instantly.

And because “what if the company goes away?” is a fair question to ask us too, we answer it in writing on our Trust & Longevity page: a six-month continuity commitment, your whole vault downloadable at any time, and terms that say so.

If you’re still weighing your options, start with the honest comparison of ways to leave messages for your loved ones or the practical walkthrough of how to make a dead man’s switch — and when you’re ready to see a carefully built switch in practice, myAngelVault is ours.

Frequently asked questions

Can Gmail send an email automatically if something happens to me?

Not on its own. Gmail’s scheduled send fires on a fixed date whether you’re fine or not. The closest built-in option is Google’s Inactive Account Manager, which notifies up to 10 people and shares the Google data you selected after 3–18 months of account inactivity — useful, but it isn’t a set of personal letters, and nobody confirms what happened before it acts.

Does Outlook have a dead man’s switch?

Outlook can delay or schedule a message, but it has no inactivity-based trigger comparable to Google’s. A delayed send is still a date-based send: it goes out on schedule unless you remember to stop it.

How long should the waiting period be?

Longer than the longest stretch you could realistically be offline — a hospital stay, a remote trip, a lost phone — with a wide margin on top. A pure 30-day timer is too short for most lives. The safer answer is not one long timer but a sequence: weeks of check-ins that try to reach you first, then a person you trust, and only then delivery.

Will my dead man’s switch email end up in spam?

It depends on who sends it. Messages from a properly authenticated sending service with an established reputation usually reach the inbox; messages fired from a personal server or a fresh domain often don’t. Whatever you use, send a test to yourself and one other person before you rely on it.

Is it safe to put passwords in the email?

No. Email is copied to every device and inbox it touches, and you can’t control where it’s forwarded. Use the email to say where things are and who to contact, and use a password manager’s emergency-access feature for the credentials themselves.

What if I change my mind, or someone’s email address changes?

Every message should stay editable and cancellable until the moment it’s delivered. Review your recipients once a year — an outdated address is one of the most common reasons a carefully written message never arrives.