Continuity plan

What we commit to so a 20-year time capsule is actually trustworthy.

Active today

✅ Domain auto-renewal with a backup payment method on file.
✅ Daily server snapshots retained 30 days.
✅ Zero-knowledge encryption — even the people running this service cannot read your vault.
✅ HTTPS/TLS via Let’s Encrypt with auto-renewal.
✅ Encrypted vault export — download a complete encrypted backup anytime from Settings.
✅ Printed Legacy Access Code per trusted contact — your contact can decrypt their scoped portion of your vault using a 24-word code on a sheet you hand them. The code travels by paper, not over the wire; it’s the artefact that makes release work even if Patrimo is gone.
✅ Annual heartbeat email — yearly reminder of every scheduled release on your account so you can review/edit/cancel/extend.
✅ Wellness-check pre-warnings at day N-14 and N-1 to give you multiple chances to sign in before contacts are alerted.
✅ This page, kept current as commitments evolve.

Planned (designed, not yet built)

⏳ Successor-maintainer process — named successor + documented credential handover under a separately-encrypted operator-vault. Target: before public launch.
⏳ Self-host fallback documentation — a written guide so any user can run their own copy from the encrypted export tarball. Target: before public launch.
⏳ Mobile apps (iOS & Android) via React Native. Target: post-beta, week 8+.

We’d rather under-promise. Items above marked ✅ are active; items marked ⏳ are not yet active. Last reviewed: 2026-05-10.