← Back to What we build
12 · DIGITAL ESTATE & TIME-LOCKS

LegacyVault

Concept detail · target pilot

A metadata-only concept for planning time-delayed access and recovery. The current pilot creates a simulated plan; it does not encrypt or store real payloads. It is not a zero-knowledge service, and its cryptography, key custody, recovery, and time-lock behavior are not implemented or independently validated. Never enter production credentials, secrets, keys, or recovery phrases.

Why it exists

Important digital instructions often outlive the apps and people that created them, so access rules need to be explicit and verifiable.

Proposed pilot workflow

  • A proposed test would model a time rule and recovery plan using non-sensitive sample data only.
  • Design goal: make the proposed rule, key-handling assumptions, and recovery steps visible to a reviewer.
  • Design goal: provide a review artifact after key management, security, and export behavior are implemented and tested.

Prototype boundary

Zero-knowledge is an unverified design goal, not a current capability. The pilot accepts metadata only and does not implement payload encryption, key custody, release, or recovery. Never place production credentials or secrets in it. Cryptographic and jurisdiction-specific estate review remain external requirements.

Planned service shape

Target pilot pricing for validation—not a live subscription or promise of availability.

$15/moCapsule · 1 lock
$49/moFamily · 5 locks
$149/moEstate pilot
Discuss a pilot →Bring a use case, a test group, or a data sample. We’ll define the safest first experiment.