Private means private
This isn't a promise we're asking you to trust — it's an architecture. Here's an honest explanation of how it actually works.
Encrypted before it ever leaves your device
Every journal entry, every photo, every letter is encrypted in your browser before it's ever sent anywhere. We store ciphertext — scrambled data we have no way to read, not just data we've promised not to look at.
Your password is the only key
Your password is turned into your encryption key through a deliberately slow, memory-hard process (Argon2id) designed to resist exactly the kind of brute-force attacks that target weaker systems. We never see your password, and we never see the key it produces.
Search happens on your device, not ours
Finding an old entry means searching decrypted content in your own browser — not sending a query to a server that would need to read your data to answer it. This is a permanent architectural choice, not a setting.
Sharing, on your terms only
A shared link carries its own key in a part of the URL that's never sent to any server. Nothing is shared until you explicitly choose to, and every access is logged so you always know if something was opened.
Legacy access, without a master key
If you choose to set up a legacy plan, your encryption key is split using real cryptographic secret-sharing (Shamir's Secret Sharing) across your trusted contacts and our servers. No single party — including us — ever holds enough pieces alone to reconstruct it.
Because we genuinely cannot see your data, we also cannot reset your password for you if you forget it. There is no "forgot password" recovery. This is the same design choice behind services you may already trust with sensitive information — the alternative would mean giving up the very privacy this page describes. We built a real safety net for this (your own recovery sheet, plus optional trusted contacts) rather than a shortcut around it.