A calmer way to prepare your household
Put household records, instructions, passwords, and access plans in one organized place. Name trusted recipients, set release rules, and give an AI access to one dedicated vault instead of your whole life.
Create a free account. Add automated release rules when you move to Pro or above.
Private by design. Specific about what is client-encrypted and what is not.
Household readiness is more than a folder
You may know where the insurance policy lives, which account keeps the lights on, what the safe code is, and who to call first. But if you could not explain it, would anyone else know?
Important details live across drawers, devices, inboxes, and memory.
Giving someone every password today creates a new risk.
Strong privacy is not enough if the right person has no plan for when access should change.
LifeVault helps you prepare the information, the people, and the rules together while you are still in control.
A plan you can build one step at a time
Start with the information someone would need to keep your household moving: instructions, notes, passwords, account details, insurance records, property documents, and key contacts. Keep separate vaults for separate parts of life so you do not have to share everything together.
Add the recipients who belong in the plan. A person is not given access just because you name them; your release setup records who the plan is for and when a rule should apply.
Set a future release date or an inactivity window. Preview scheduled and inactivity timing before relying on it. For inactivity rules, LifeVault warns you seven days and three days before the trigger so returning to your account can stop an unintended release.
If you want an AI assistant to organize or work with selected information, put that information in a dedicated Agentic vault. Its key can be read-only or allow create, update, and delete actions. That key does not automatically open your other vaults.
Privacy is a boundary, not a slogan
LifeVault uses different protections for different content and workflows. Here is the plain-language version.
You decide what goes into each vault, who belongs in the plan, which release rules are active, and which Agentic vault an API key can reach.
In client-mode vaults, note bodies, password contents, and structured vault entries are client-side encrypted. LifeVault cannot read those note bodies, password contents, or structured vault entries. Web files uploaded into a client-mode vault are encrypted before upload. LifeVault can still process operational metadata such as file names, types, sizes, checksums, timestamps, and account activity needed to run the service.
Generated legal-template PDFs use server-side AES-256 envelope encryption. LifeVault’s service can decrypt those generated documents when the product workflow requires it.
Naming a recipient does not give them immediate access. For account-wrapped client vaults, a scheduled release can give a recipient access to client-encrypted contents on the web, as long as that person already has a LifeVault account when you set up the release. Inactivity releases use the same key handoff. We have confirmed the recipient side end to end on the scheduled path only. Emergency access grants vault membership but does not hand over the keys to client-encrypted contents. Mobile recipient unlock, passkey-only unlock, and release policies created before recipient-key support are not covered.
Assume a connected AI can read any item it retrieves from the Agentic vault you authorize. The API key is limited to Agentic vault access, and current per-vault keys do not open your other vaults. Choose read-only access when the assistant does not need to change anything, and revoke the key when the work is done. A connected AI provider may retain or process retrieved content under its own terms, so review that provider before connecting it.
Do not group every uploaded file into one promise. On mobile, file upload uses client encryption only for account-wrapped client vaults. An upload to an API-key-wrapped Agentic vault does not use that client-file encryption path.
Choose the level of continuity your household needs
Annual pricing is shown first because each annual plan costs the same as ten monthly payments. Monthly billing remains available.
Start here for one household organizer
$120/year
$12/month if billed monthly · 14-day trial
For a fuller digital-estate plan
$290/year
$29/month if billed monthly · 14-day trial
For a shared household system
$490/year
$49/month if billed monthly · 30-day trial
Prefer to begin smaller? Create a free account with 256 MB, one password vault, and two standard vaults. Upgrade when you are ready to add scheduling or emergency access.
No. LifeVault is an information organizer and access-planning tool. It can help you store the records and instructions your household may need, but it is not legal advice and does not replace a valid will, trust, power of attorney, healthcare directive, or advice from a qualified professional.
No, but the honest answer depends on the content. In client-mode vaults, LifeVault cannot read the contents of your note bodies, password fields, or structured vault entries. Web files uploaded to a client-mode vault are encrypted before upload. Generated legal-template PDFs use server-side AES-256 envelope encryption and are decryptable by the service. File names, types, sizes, checksums, timestamps, and other operational metadata remain service-readable.
Not through a current per-vault Agentic API key. The key is restricted to an Agentic vault and can be configured for read-only or create/update/delete access. The assistant can see anything it retrieves from that authorized vault, so only place information there that you intend the connected AI to use. Your AI provider’s own retention and privacy terms still apply.
LifeVault supports scheduled and inactivity-based rules, recipient membership or invitations, and owner warnings before inactivity execution. Before this page publishes an “automatic family access” promise, the client-encrypted recipient-key handoff must pass an end-to-end test. Until then, use LifeVault to build and maintain the plan, but do not treat the current workflow as a verified substitute for testing access with the people you named.
Household readiness is not a one-time download. The value depends on keeping the account, encrypted storage, access controls, release rules, and service availability maintained over time. If annual billing fits your household, it costs the same as ten monthly payments. If you are not ready for a paid plan, begin with Free and upgrade when automated release features matter.
A binder is easy to understand but hard to update, easy to lose, and usually all-or-nothing. A shared folder solves storage, but it does not separate human access from AI access or let you structure scheduled and inactivity rules. LifeVault is for people who want the information and the access plan in one place.
Web files uploaded to a client-mode vault use client-side encryption. On mobile, file uploads use client encryption only in account-wrapped client vaults; uploads into API-key-wrapped Agentic vaults do not use that client-file path. Generated legal-template PDFs use server-side AES-256 envelope encryption.
Side-by-side comparisons of the two access tools households most often already have.
Build the household map now. Choose the people and rules deliberately. Keep each human and each AI assistant inside the access boundary you intended.
Build My Household PlanStart free. Add automated release rules with Pro, Vault, or Family Legacy.
