It's alive.
Be the first to try it.
MyMissingNote is in public beta on iOS and Android. Download it now, put it through its paces, and help shape what comes next.
New here? Read the guide to understand how MyMissingNote works before you dive in.
Not ready to download yet?
Join the list and we'll keep you posted as the beta evolves.
This is a beta — read before you start
MyMissingNote is in active development. While we take the security and integrity of your data seriously, beta software can have bugs, unexpected behaviour, and breaking changes.
- Data may be lost or reset during the beta period. Do not store information you cannot afford to lose until we reach a stable release.
- We will do our best to preserve your data across updates, but we cannot guarantee continuity during this phase.
- Features may change — flows, settings, and terminology are still evolving based on your feedback.
- Found something broken? Please report it via TestFlight feedback or email contact@mymissingnote.com. Every report matters.
What we encrypt — and what we don't
We believe you deserve a clear, honest picture of how your data is protected. Here is exactly what MyMissingNote encrypts end-to-end today, and what it does not.
- Note content Encrypted on your device with a key derived from your password using PBKDF2. We store only the ciphertext — we cannot read your notes under any circumstances, including legal requests.
- Note disclosures to recipients When a note is linked to a recipient, it is re-encrypted with a unique per-link disclosure key before being stored. Only the final recipient, via their disclosure link, can decrypt it.
- Vault notes (trustee access) Notes shared via a vault are encrypted using a key derived from an ECDH exchange between the trustor and trustee. Neither party's private key leaves their device.
The following data is protected by our security practices and access controls, but is not end-to-end encrypted — we can access it:
- Recipient contact details Name, email address, and phone number of your recipients. Required in plaintext so our system can deliver disclosures when your Proof of Life escalates.
- Account metadata Your email address, account settings, and authentication data.
- Proof of Life configuration Your check-in schedule, last check-in timestamp, and current escalation phase.
- Vault state Which trustees have access, request history, and vault lifecycle state.