Legal
Privacy Policy
Last updated November 16, 2026. Vault content is encrypted on your device. Account, delivery and billing information have different processing needs, and each optional AI feature requires your consent.
Summary
- We process information required for authentication, billing, delivery and account operations.
- Vault documents and journal content are encrypted on your device, and stored Life Books are encrypted under a key only your vault can open. Optional Life Book composition sends the written material you select through our backend to Anthropic after your consent. Optional web stories send the public pages you submit to Jina Reader or Firecrawl, and their text to Anthropic, after separate consent. Optional writing help sends the words you select in your Book, with your instruction, to OpenAI after your consent.
- We do not sell your data. Analytics runs only if you allow it, on a separate page that cannot reach your vault.
- You can export your data and request account deletion. After Trusted Delivery activates, content is kept for 60 days for your recipients, or 100 years with Preservation for everything you did not leave out of it, as described below.
Data we collect
Account identifiers: email address, account creation timestamp, and an optional phone number you can add to your profile.
Billing metadata: subscription plan, billing status and payment processor customer, subscription and transaction IDs. Payment card details and billing address are collected by our payment processor (Stripe); card details never reach Henedo’s servers.
Ciphertext: the encrypted blobs of your vault contents, journal entries, contact bundles and signing keys. We cannot decrypt these.
Operational metadata: timestamps, file sizes, MIME types (required for quota and content-type headers), session events (last login, heartbeat, Trusted Delivery state transitions).
Preservation choices: when you leave vault folders out of Preservation, we store the identifiers of those folders and whether files that are in no folder are left out. Folder and file names stay encrypted on your device; we never receive them in readable form. When Trusted Delivery activates, we record the identifiers, count and total size of the files left out, so they can be erased on the stated date and their recipients told that date.
Household and Family copies: when you keep a copy of a file another member shared, we record which of your files is the copy, the original file, the member who added it, your membership and the file’s size. This link lets your vault show what you have already kept and prevents duplicate copies of the same file. It holds identifiers and a size, never names or contents, and it is deleted when you delete the copy or your account. The member who shared the file is not notified.
What a member left you: if you leave a Household or Family, or are removed from it, while another member’s Trusted Delivery is under way, we record your membership, that member, their Trusted Delivery and the date until which what they added to Shared stays readable for you. It holds identifiers and dates, never names or contents. It is deleted once what they left you has closed (that date has passed, and their Trusted Delivery has ended or been cancelled), or with your account or theirs.
Support requests: the subject, category and messages you submit through Help & Support are stored by Henedo in readable form, separate from your encrypted vault. Do not include passwords, decryption keys, private files or access links. The email alert we receive about a new request contains a request reference and category rather than your message text.
Two-factor resets: if you ask support to reset two-factor authentication, we record the reset, each step you take, and which support operator looked up your account, opened the reset or cancelled it, with the reason they gave and a fingerprint of the support reference they used, never the reference itself. The reset is deleted with your account; the record of each support step is kept after that, so every reset can be accounted for.
Delivery information: legacy-contact details, Ask recipient details and capsule delivery details are processed by the service to address and deliver messages. Their contact fields are encrypted at rest with a server-managed key; this is different from the device-only keys protecting vault documents. Some details are currently stored in readable form on our servers: your profile name, phone number and date of birth if you add them, and your billing email. Gift recipients, gift messages and partner invitations are also stored encrypted with the server-managed key, but a readable copy remains until our systems finish moving to the encrypted copy. Recovery-share holders and preserved-archive forwarding recipients are stored encrypted. Each email we send keeps its recipient address and text in our outgoing email queue until it is delivered and for a limited time afterwards, as described under Retention. Sign-in sessions, security alerts and similar records include IP addresses and browser user agents.
Reaching your legacy contacts: to know when to stop writing, Henedo records when a legacy contact first enters a key on their page and when their key first opens their delivery, only after Trusted Delivery has activated. We do not record an IP address or device for this. For a Household or Family member you share your Journal or Life Story with, or set a will, Book of Life or answers aside for, Henedo records instead the first time they sign in to their own account after Trusted Delivery has activated, in the same way. If a legacy contact has not entered a key on their page, or such a member has not signed in, we may write to them again and ask your verified backup email and your other legacy contacts who have opened their own delivery whether they can reach that person. These emails name that person, never what they receive, and your other legacy contacts are never asked about someone you keep private from them. The line you write for a legacy contact’s email is stored encrypted on our servers and sent in an ordinary email, so Henedo can read it. Your personal message stays inside the end-to-end encrypted delivery.
When someone asks as your legacy contact: a person signed in to Henedo can tell us that you named them and that your letters are not reaching them. To check, we compare the address they sign in with, an older address they may give and the name they type with the legacy contacts you named; the name they type is not stored. If they match a legacy contact you named at another address, we tell you at your sign-in and verified backup addresses, and the people who share your Household or Family membership (never one who is also your legacy contact, about someone you keep private from your other legacy contacts), naming that legacy contact and showing only the first two letters of the new address and its domain; you see the whole address in your dashboard. We keep the new address encrypted until the request is settled, and a record of how it was settled for about 13 months. The page never tells the person who asked whether you named them. They hear from us only when there is something for them: once their new address is confirmed or takes effect, or, if they ask from the very address you gave us once your delivery is open to them, their letter again, unless you chose to stay anonymous to them.
What your legacy contacts can receive: each legacy contact receives what you choose for them, person by person. A new legacy contact starts with all of it, and you can narrow it for each one. It can include your Journal and your Life Story, each with its photos, videos, recordings and files; the answers people gave you through the Ask, written and spoken; whole conversations you brought in from WhatsApp, Instagram, Messenger or Telegram, which hold other people’s messages, photos and voice notes as well as yours; and the memories people sent to your Legacy Inbox that you kept, with their photos, videos and recordings and each sender’s name, never their email address, but only where the sender allowed it to be shared beyond your inbox. A conversation with someone you left out of what you pass on stays behind unless you choose it by name. A Household or Family member you share your journal or Life Story with receives its photos, videos and recordings too. Household and Family members are never given your conversations or those memories. All of it is encrypted on your device before it is stored, and Henedo cannot read any of it: we store which of your conversations each legacy contact may open, by an identifier, and serve them only encrypted data. Once your Trusted Delivery has started, a legacy contact’s page can also say how many Ask answers and memories from friends reached you after their delivery was last prepared; we count them from dates we already hold, never what they say or who wrote them.
New in your Shared space: if you are in a Household or Family, Henedo can email you at most once a day when other members add to your Shared space. To write it, Henedo uses only information it already holds without opening anything: who added items, when, which items you are allowed to open, and each file’s type (photo, video, recording, document or other file) as recorded at upload. Henedo cannot read the files, their names or their contents, and the note never names or describes a file. Henedo also records when you last opened Shared, so the Vault can mark what is new and the note does not repeat what you have already seen. You can turn the note off in Settings, or from the link in any note.
Shared Capsule guests: a guest who adds a memory to a Capsule made together may give us an email address for a receipt and one email on the day the Capsule reaches its recipient. We can read that address. It is encrypted at rest with a server-managed key, used for those two emails only, and deleted once the second is on its way, or a week after the day if it is not. A guest who withdraws their memory, or a Capsule that is deleted, takes it with them. Copies of the two emails follow the email retention described under Retention.
Preservation keepsake: when you ask for the keepsake included with Preservation, you give us the text for its title plate and a postal address, with an optional phone number for the courier. We use them only to make the plate and post the disc. They are encrypted at rest with a server-managed key. The operators who prepare the disc can read the plate text while it is being made and the address when there is a disc to post, and each read is recorded. The courier receives the name, address and phone number it needs to deliver the parcel. We delete the plate text and address 30 days after delivery, or 120 days after shipping when delivery is never confirmed, and straight away if the order is cancelled. The disc holds your encrypted owner export; we record only its fingerprint and counts such as its size, never its readable contents or a key that opens it.
Optional Life Book composition: when you request AI composition and consent, the written material you select is sent in readable form through a Henedo Edge Function to Anthropic: your written Life Story answers, the written perspectives other people gave you, the web stories you saved, and any journal entries, written Ask answers or Legacy Inbox memories you turn on for that book, with your date of birth if you added it. Voice and video answers are never sent. The finished book is stored only in encrypted form, under a key only your vault can open: your browser encrypts a book it receives directly, and a book composed in the background is sealed by our server with a one-off key your browser created and locked under your vault’s master key. The readable material and that key exist only in memory while the book is composed; the handler does not persist the readable request or response. Revoking consent prevents future generations; it cannot undo processing already completed.
Optional writing help: after you allow writing help in your Life Book, each request sends the words you choose (selected words, one chapter, or each chapter in turn) and your instruction or the kind of help you picked, with your Book and chapter titles and a few sentences around the words, in readable form through a Henedo Edge Function to OpenAI, which writes a suggested change. If OpenAI is unavailable or declines the passage, the same request goes to Anthropic instead. If you allowed writing help when it named Anthropic, your requests go to Anthropic until you allow it again. Henedo does not persist the readable request or response and asks OpenAI not to store its response; each provider’s retention follows its API data policy. We record each request and the words it counted toward your monthly allowance, never the words themselves. A suggestion changes your Book only when you accept it and save, and your Book is encrypted on your device before storage. Stopping writing help prevents future requests; it cannot undo processing already completed.
Optional web stories: after separate consent for each draft, submitted public links are sent to Jina Reader or Firecrawl to retrieve page text. Extracted text, text you paste, your profile name, and any context you add are processed in readable form by Henedo and Anthropic to prepare an editable draft. Page retrieval receives only the public links; pasted text, your profile name and your context are sent separately for drafting. We do not fetch or send your profile’s email address, phone number or other fields for drafting. Henedo does not persist this readable request or response. We request no caching or tracking from Jina Reader; provider retention follows the providers’ API data policies. Only material you review and save is encrypted on your device before storage, including its title and source links. Stories you select for your Life Book are included when you separately consent to book composition. Saved web stories follow your Life Story sharing settings.
Error reports: when a page fails to load or crashes, your browser sends Henedo an anonymous error count: the app build, a general page area (for example “dashboard” or “capsule link”), the type of error, a short code and your browser family. It never includes the page address, link codes, error text, file names, your email address or any account or device identifier. Counts are kept for 30 days to find and fix failures.
Analytics: if you allow it, Google Analytics 4 records which Henedo pages and dashboard sections you visit, how long each is in front of you, how quickly the first page of a visit loads and responds, a fixed list of steps, such as starting sign-up, choosing a plan or writing a Journal entry, the kind of membership the account has, and the campaign labels of the link that brought you, if any. It never receives what you write, names, files or anything else in your vault. It runs on a separate address, measure.henedo.com, that cannot read your vault or keys. Private links, codes and email addresses are removed from page addresses before they are sent, and pages opened from a private link are not measured. See the Cookie Policy to change your choice.
Where a new account came from: when you create an account, Henedo records up to three labels from fixed lists: the Henedo page or link that led you to sign up (for example a comparison page or an Ask answer), the kind of page your visit started on (for example the blog, a feature page or pricing) and the kind of site that sent you (a search engine, an AI assistant, a social network, an email, another site, or none). It never records a page address, the other site’s address, a search term or a link code. Until you sign up, the labels wait in your browser’s session storage for at most 15 minutes. We use them only to learn which pages help people start.
Data we do not collect
- Readable contents of encrypted vault documents, photos, videos and journal entries. The optional AI-processing exceptions for selected Life Story answers, writing help and web-story drafts are described above.
- File names or folder names (encrypted client-side with your Master Key).
- Your readable Master Key or vault encryption passphrase. Account sign-in credentials are processed separately by the authentication provider.
- Your readable recovery key as part of normal vault storage. New contact and preservation notification emails contain no decryption key. We never see legacy contacts’ access keys, which owners hand over independently, unless an owner asks us to email one to a contact: we then pass that key to our email service once to deliver it and do not store it, though email providers along the way, including the recipient’s, may keep copies. Historical email and escrow records may retain material from earlier flows; escrow enrollment is retired.
Your rights (GDPR / CCPA)
You can request access to the account data we hold, export your vault, correct inaccuracies, request account deletion, and request restrictions on processing. Deleting your account deletes its content, which ends Preservation.
After a user dies, their personal representative can contact us at privacy@henedo.com. We verify the requester’s identity and authority before acting and keep a record of the evidence. We cannot decrypt vault content or give anyone access to it: content reaches people only through the Trusted Delivery recipients and keys the owner chose. A representative can ask us to confirm whether Trusted Delivery has activated, or to handle billing and erasure questions for the account. We do not start, bring forward or stop Trusted Delivery, or extend its retention period, on anyone’s request.
Requests: privacy@henedo.com. We respond within 30 days.
Subprocessors
We use the following subprocessors to deliver the service:
- Supabase provides authentication, the database, realtime updates and backend functions, hosted in the AWS eu-west-1 (Ireland) region. Vault document bodies reach storage as ciphertext; account and delivery services process their necessary operational information.
- Cloudflare R2 stores the encrypted objects for vault files and preserved archives. Your browser uploads and downloads those objects directly; they arrive as ciphertext.
- AWS Amplify, with Amazon CloudFront as its content delivery network, hosts and serves the web app. Like any web host, it receives standard request information such as your IP address, browser user agent and the pages requested.
- Stripe (payment processing), processes card data directly; Henedo never sees card numbers.
- Spacemail delivers our transactional email over SMTP: sign-in, check-in and Trusted Delivery notices, Ask and Capsule invitations, gift codes and support updates. It processes the recipient address and message content needed for delivery. New notification emails contain no decryption key, except the email a Capsule’s recipient receives on its day when its sender asked Henedo to deliver it.
- Postal and courier services deliver the Preservation keepsake. They receive the recipient name, postal address and, if you give one, a phone number.
- Google provides optional sign-in with a Google account. When you choose it, Google handles the sign-in and shares your account email and basic profile with our authentication provider.
- Anthropic processes the written material you select when you consent to Life Book composition, and source text when you separately request a web-story draft. For writing help, it processes a request only when OpenAI is unavailable or declines the passage, or when you allowed writing help before it named OpenAI and have not allowed it again.
- OpenAI processes the words you choose in your Life Book, with your instruction and the titles and nearby sentences sent with them, when you allow writing help, to write a suggested change.
- Jina Reader retrieves the public pages you submit when you consent to creating a web-story draft. Firecrawl may be used first when configured, with Jina Reader as the fallback.
- OpenFreeMap serves map tiles only when you open a map, for example on a Place. Your browser requests tiles directly, which shows OpenFreeMap your IP address and the map area being viewed. No referrer or credentials are sent with those requests.
- Google Analytics measures page visits, time on page, page speed and a fixed list of product steps, only after you allow analytics. It runs on measure.henedo.com, separate from your vault, with advertising features and Google signals turned off.
Retention
Account deletion has a seven-day cancellation period. Cleanup runs afterward and retries failed storage or database operations before finalizing. Billing records follow applicable retention requirements. Deleting your account deletes its content, which ends Preservation. During account closure, eligible verified archives can be released immediately to reviewed recipients and retained through those dates, after fresh authentication, key-possession confirmation and release notices. An archive that cannot be released this way, for example while it is still being checked in storage, keeps the account from closing until it can. Cancelling account deletion cannot retract that explicit release or copies already obtained. Deletion revokes ordinary account access and removes eligible source data while retaining the archives explicitly kept for recipients; it cannot recall content another person has kept in their own account, downloaded or forwarded. Storage-provider backups, audit records and historical delivery records require their own retention handling.
After Trusted Delivery activates: account deletion is no longer available, so the deliveries stay open for your recipients. Living Vault content, the deliveries prepared for legacy contacts and will drafts are kept for 60 days after activation. If your account has Preservation, they are instead kept for 100 UTC calendar years from the activation date, even when they are larger than its preserved capacity, except vault folders and files you left out of Preservation: those keep the 60-day period, and the recipients they were delivered to are told the date and reminded 7 days before it. Erasure also waits until every active recipient’s notice has been accepted by our email provider, for at most 12 months after activation (if a notice was still not accepted, your verified backup email gets a last email first, and erasure waits at least 30 days after it), and until at least 30 days have passed since the last accepted notice. If a legacy contact has never entered their key on their page when erasure is due, it waits once more, for 30 days, while we write to them and ask again whether anyone can reach them. Recipients are told the planned date and reminded 30 days and 7 days before it. If a recipient is still copying what you left them into their own Henedo account when that date arrives, erasure waits one day at a time while that copy keeps making progress, for at most three days. Your membership is cancelled at activation. Copies recipients kept, downloaded or forwarded remain theirs. Once that content is erased, we keep only a one-way digest of each delivery link that had started and the day it closed, so the link says that access has closed instead of that it was never found; it names no one and opens nothing.
Non-payment: a lapsed membership does not delete data. After a seven-day grace period the account uses the free plan limits, and items above those limits are hidden from the owner’s view until a membership is chosen again, except what the owner kept from a legacy, which is never hidden. If a membership is still unpaid 30 days after the most recent failed payment attempt, we cancel it with our payment provider so no further charges are attempted; that cancellation deletes nothing. A cancelled membership that stays inactive for 365 days is recorded; that record deletes nothing.
Inactive free accounts: this never applies to an account that our billing records count as paid (a current paid membership, including a trial, a payment grace period or a redeemed gift; an accepted seat in a current Household or Family membership; Preservation; or a storage add-on within its paid period), nor while a payment dispute, a billing freeze or a late-payment review holds the account. We decide whether an account is paid from billing records, never from how much it stores. It also never applies to an account that still holds something passed to it: a copy it kept of what someone left it through Trusted Delivery or a sealed archive, including hand-picked memories, or a copy of a Household or Family member’s shared file once that member’s Trusted Delivery has activated. A free account that Trusted Delivery has nobody to deliver to, and that has had no sign-in or check-in for 12 months, receives three notices by email, at its account email and its verified backup email. Its content is erased only if nobody signs in or checks in, only if a mail server accepted at least one of the notices, and no sooner than 60 days after the first notice and 14 days after the third; the account itself and its scheduled Capsules remain. Signing in while the erasure is under way stops it, and what has not yet been erased stays. When an erasure is complete, we send one email saying so to the account email and the verified backup email. If nobody would receive anything from you, Trusted Delivery never activates and never erases anything, with or without Preservation.
Network details and email copies: IP addresses and browser user agents stored with sign-in sessions, security alerts, recovery attempts, account deletion requests and device pairing are removed 90 days after they stop being needed, for example 90 days after a session is signed out. A session that is still active keeps them so you can recognize your devices. The recipient address and text of an email we sent are removed from our outgoing email queue 30 days after it was delivered or finally failed, and no later than 180 days after it was queued; an email still waiting for its delivery date, such as a capsule, is kept until it is sent. Our hosting providers’ own request logs follow their retention policies.
Preservation keepsake details: the title plate text and postal address are deleted 30 days after the disc is delivered, or 120 days after it was shipped when delivery is never confirmed, and when an order is cancelled. The order’s status history and the disc’s fingerprint remain with your account.
Closed support requests are eligible for deletion after 180 days. Open requests, recorded retention holds and unresolved privacy or legal matters remain until resolved. Account deletion removes ordinary unheld support requests and closed, fulfilled, unheld privacy/legal requests; outstanding, reopened or held matters remain with their sign-in account link removed. Personal details you wrote in those messages are not automatically anonymized. Provider backups follow their separately applicable retention policy.
Contact
Henedo Inc., privacy@henedo.com.