# Seal: Posthumous Digital Legacy App Using Hardware Keys

iOS app encrypts messages for loved ones, accessible only after death via hardware keys.

- **Source:** [Hacker News: Show HN](https://news.ycombinator.com)
- **Published:** 2026-09-19
- **Topic:** [Data & AI](https://brifing.si/c/data-ai)
- **Original article:** <https://github.com/jasonepage/Seal>
- **On Brifing:** https://brifing.si/s/cbd361a8-f5c8-442b-869e-d618360cd136

## Hardware key-based access control

Seal uses hardware keys as the sole authentication method for accessing encrypted envelopes containing passwords, photos, and voice memos. Each recipient must physically possess their assigned key to open their designated envelope. The system eliminates centralized servers, relying instead on Cloudflare's static site and Apple's Cloud Kit for storage. This approach differs from password managers by distributing access rather than centralizing it.

## Multi-stage inheritance protocol

The app implements a 125-day countdown process before releasing contents: 90 days of inactivity detection, 21 days of warning notifications, and 14 days of grace period. During this time, the envelope creator receives multiple alerts to check in and prevent premature release. This extended timeline provides safeguards against accidental triggering while ensuring eventual access for designated recipients.

## Zero-knowledge encryption model

All envelope contents remain encrypted end-to-end using Apple's Crypto Kit, with no backdoor access for developers, Apple, or other third parties. Each recipient receives only their designated materials, preventing disputes over shared assets. The system specifically addresses crypto wallet inheritance needs by allowing precise distribution of seed phrases to multiple heirs without centralized mediation.

## Developer origins and stack

Created by a CS undergraduate with prior hardware key experience, Seal was conceived through brainstorming with Claude AI. The current implementation uses iOS-native technologies including Passkey authentication, Face ID/Touch ID, and Cloud Kit storage. The development team consists solely of the creator and Claude AI, with no independent security audits completed yet. The codebase remains open-source on GitHub for community contributions.

## Target user scenarios

Primary use cases include crypto investors needing to securely pass wallet access to heirs and families wanting to leave personal messages. The app solves inheritance conflicts by providing unambiguous, time-released distribution of digital assets. Early adoption shows particular interest from cryptocurrency users who require decentralized solutions for seed phrase management without trusted third parties.

## Current limitations

The initial release supports only iPhone users with hardware key authentication. The unaudited status means users are cautioned against storing live seed phrases. Technical constraints include iOS exclusivity and reliance on Apple's ecosystem services. The developer actively seeks community feedback to address these limitations in future versions.

## Architectural advantages

Seal's serverless design eliminates single points of failure and ensures continuity regardless of company survival. By distributing encrypted envelopes directly to recipients' hardware keys, it prevents centralized data breaches. The system maintains privacy even from the developers themselves, as all encryption occurs client-side using iOS's native cryptographic libraries.

## Future development directions

Potential expansions include Android compatibility, professional security audits, and additional authentication methods. The open-source model invites community improvements while maintaining transparency. The concept demonstrates how hardware security keys can enable novel applications beyond traditional authentication, particularly in sensitive scenarios requiring guaranteed future access.

## Sources covering this story

- https://github.com/jasonepage/Seal — 

---

_Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._