Quietly on watch

If you stop checking in, Contingency acts.
Exactly as you configured. Nothing more.

A calm, precise way to make sure the right people and information reach the right place if something happens to you. No skulls, no countdown clocks flashing red — just a plan that quietly does what you told it to.

Free to start. Encrypted before it touches disk. Open registration, no sales call.

How it works

  1. 01

    Set a check-in schedule

    Every day, every week, every month — whatever suits how you live.

  2. 02

    Tell us who and what

    Nominate trusted contacts, write messages, attach files. Each contact only ever receives what you explicitly give them — never anyone else's.

  3. 03

    Check in, or don't

    One button confirms you're safe and resets the clock. Miss it, and after your grace period, the plan you configured runs.

Built the way something like this has to be

Encrypted before it's written

Messages and files use envelope encryption with a master key that never lives in the database. Cancellation secrets and passwords are hashed with Argon2id, never stored or logged in plaintext.

Tamper-evident audit trail

Every check-in, arming, release and cancellation is recorded in a hash-chained log.

Never fires by accident

An explicit, validated state machine drives every contingency. No release fires twice.

Passkeys, MFA, scoped API tokens

Sign in with a passkey or authenticator app. Automate check-ins with bearer tokens scoped to exactly one job. Webhooks are HMAC-signed and durably queued. Read the API reference →

What Contingency can help with

  • You become unable to access the service.
  • You deliberately stop checking in.
  • You need information released after a period of inactivity you define.

What it can't do

Trust comes from precision, not marketing waffle, so here it is plainly. Contingency cannot protect against compromise of your email account, someone obtaining your cancellation secret, simultaneous compromise of Contingency and your encryption keys, badly configured recipient access, or an unreachable remote server you asked it to contact. We'd rather tell you this now than have you assume otherwise.

Set it up once. Check in when you're asked.

Takes about five minutes. Everything is reversible until the moment you tell it not to be.

Questions before you start? [email protected]