What Happens to Your Digital Time Capsule If You Die Before the Delivery Date?
You set a message to arrive on your daughter's 30th birthday, fifteen years from now. Then comes the thought that ruins the moment: what if I'm not here?
It's the right question, and most digital time capsule services never answer it. Understanding what a service actually does — not what it promises — is the difference between a nice idea and something your family will really receive.
Most "time capsules" are scheduled emails
The typical digital time capsule works like this: you upload photos, write a message, choose a date, and on that date the system sends an email.
A scheduled email is indifferent to everything that happens in between. It doesn't know whether you're alive. It doesn't know whether the recipient's address still exists. It doesn't know whether the family it was written into still looks the same. It fires on a date, into whatever the world has become.
For a five-year letter to yourself, that's fine. For anything meant to outlive you, it leaves three problems unsolved.
Problem 1: the address stops working, and nobody notices
This is the most common failure, and the least dramatic. People change jobs and lose work addresses. Providers shut down. Accounts get abandoned. Over fifteen years, the odds that a given email address still works are not good.
A date-based system discovers this at the worst possible moment — at delivery, when the person who could have fixed it is gone.
What has to happen instead is unglamorous but decisive: the address has to be checked, and checked again over time. When you seal a capsule at MemWall, each recipient gets a short, neutral email asking only that they confirm the address is active. It reveals nothing — not the capsule, not its contents, not that anything exists for them at all. (If you'd rather they weren't contacted, you can switch that off per recipient, and that choice is permanent for contact messages.)
After that, the system watches. If an email to a recipient hard-bounces, that address is marked unreachable and you are told, while you can still do something about it. A temporary failure — a full mailbox, a server hiccup — is treated as temporary and retried, not written off. And for capsules with long horizons, the check repeats: once a year, quietly, asking only whether the address still works. An unanswered check doesn't condemn the address; it simply returns it to unconfirmed so it can be asked again.
If email is exhausted entirely, and you have recorded a mobile number and consent for that recipient, there's an SMS fallback — and it says nothing about what's waiting. No capsule title, no names, no link token: only that there is a message at MemWall, with a way to opt out.
Problem 2: the message arrives into the wrong moment
Picture a letter set to arrive on an anniversary, delivered eight months after the writer's funeral, addressed as though they were still here. Nothing in the system knew. What was meant as a gift lands as a shock.
The reverse happens too: a family loses someone and never learns that recordings existed, because the delivery date is still four years away and nobody has the password.
A legacy capsule is built for exactly this. Instead of a fixed calendar date, delivery is tied to a confirmation-of-life process — often called a dead man's switch. The service checks in with you at intervals. You confirm; nothing happens; the capsule stays sealed. Only when check-ins go repeatedly unanswered does a careful, multi-step escalation begin, designed so an ignored email or a holiday can never trigger delivery on its own.
The principle worth insisting on, from any service: a lapsed payment must pause monitoring — never deliver, and never delete. A "goodbye" message delivered to a living person's family is the worst possible failure, and it should be structurally impossible rather than merely unlikely.
Problem 3: nobody else knows it exists
The simplest failure of all. Capsules are made privately, and private things get lost.
This is why a fallback contact matters — someone who can be reached if the recipients can't be. But there's a catch most people don't consider: naming someone doesn't mean they've agreed. At MemWall a fallback contact receives a request and must actively accept before they're part of the chain. Someone who declines is never contacted again. A person who never agreed to a role isn't a safety net; they're an assumption.
The same blind spot applies to everything else you leave behind online — see your digital legacy for the accounts side of the problem.
Six questions to ask any capsule service
Whichever service you choose, including ours:
- What happens if I die before the delivery date — is there any death-aware delivery, or only a calendar?
- What happens if my payment fails: pause, delete, or deliver?
- Do you check whether my recipients' addresses still work — once, or over time?
- Will you tell me if a recipient becomes unreachable, while I can still fix it?
- How do recipients find out a capsule exists, and what does that message reveal?
- Can I update recipients and contents as life changes?
A service that answers all six clearly is one you can plan around. A service that answers none is a scheduled email with better photography.
What you can do, on any platform
- Tell one person it exists. A single trusted person who knows something is waiting eliminates the most common failure on its own.
- Name more than one recipient, so one dead address doesn't end the story.
- Keep contact details current — the same discipline as a will: review it when life changes.
- Keep the irreplaceable things in more than one place. A capsule is a delivery mechanism, not a backup strategy.
The point of writing to the future is that somebody reads it. Everything above exists to protect that one outcome.