How Do Evoke's Liveness Check-Ins Work?

Evoke's liveness check system sometimes called a "dead man's switch" — is what ensures your inheritance plan activates when it's needed. Here's exactly how it works.

Check-in frequency

Evoke sends you periodic notifications asking you to confirm you're still active. The frequency depends on your plan:

• Personal plan: Annual check-ins
• Business plan: Quarterly check-ins

How to respond to a check-in

When you receive a check-in notification, you simply confirm your status through the Evoke app or by responding to the notification email. The whole process takes less than a minute. You can also use the check-in as an opportunity to update your inheritance plan if anything has changed — new wallets, new heirs, or updated contact information.

What happens if I miss a check-in?

If you miss a check-in, Evoke sends follow-up reminders through multiple channels:

1. Email reminders at increasing intervals (1 week, 2 weeks, 4 weeks)
2. SMS text message reminders (if you've provided a mobile number)
3. A final grace period notice

Only after all reminders are exhausted without a response — typically 30–60 days after the initial check-in — does Evoke escalate to your nominated contacts.

What happens during escalation?

When escalation triggers, your nominated contacts receive:

• A notification that you've been unresponsive to Evoke's check-ins
• Access to your Digital Asset Schedule
• Instructions for next steps, including how to contact Evoke support

Your contacts do not receive your private keys — only the documentation needed to begin the recovery process through proper legal channels.

Can I pause check-ins if I'm traveling?

Yes. You can log into your Evoke account and extend your next check-in date if you know you'll be unreachable for a period. This prevents false escalations when you're on a long trip or in an area without internet access.

Privacy note: Your contacts are never notified during normal operation. They only receive information if the full escalation protocol has been exhausted without a response from you.