Where your data lives
A plain-English map of every place a piece of your LifeHouse information might be sitting. No jargon, no surprises.
Tier 1
Your device (your computer or phone)
Nothing permanent.
LifeHouse OS does not store your documents, vault items, chats, or any house data on your computer. When you upload a file, the browser holds it just long enough to send it to your account in the cloud, then lets it go.
The only files that ever land on your computer are ones you choose to download — exported CSVs, Vault zips, or individual file downloads. Those live wherever you saved them. We don't reach back into them.
Tier 2
Your browser
A small amount of convenience state.
What we keep in browser storage on this device:
- Your sign-in token, so you stay logged in between visits.
- UI preferences — which intro splash you've seen, your room-readiness flags, dismissed coachmarks, the "you've acknowledged the upload privacy notice" flag.
- The encrypted contents of your Private Password Safe (the password manager tucked inside the Vault) — encrypted with your 4-character safe code before being written, never sent anywhere.
Clearing this browser's site data will sign you out and forget your UI preferences. It will not delete your house — that lives in your account.
Tier 3
Your LifeHouse account (the cloud)
Where everything that matters actually lives.
Documents, room uploads, Vault items, chats with staff, House Facts, contacts, calendars, inventory, health entries, pets, vehicles, students, care recipients, family tree, follow-ups, preferences — all of it lives in your account on Lovable Cloud infrastructure.
Protections we apply by default:
- Per-resident isolation. Every row is scoped to your account via row-level security. Other residents physically cannot read your data.
- Encrypted at rest. Files in your room drawers and Vault are encrypted on the storage layer.
- Admins and testers cannot open your Vault, drawers, or chats. Their access is limited to operational health (counts, error reports) and the things you explicitly submit to admins (suggestions, issue reports).
- AI replies transit the Lovable AI Gateway to Google Gemini or OpenAI to generate a response, and the reply is stored back in your account. The model providers do not retain your prompts for training.
- Outbound messages need your approval. If a staff member drafts an email or external action, it waits in your Front Hall until you sign off.
Your safety net
Beta-tester promise
Upload your real life. Wipe it whenever you want.
You can permanently delete your entire account — and every private trace of yourself — in one click, any time.
Open your profile, scroll to Delete my account, and confirm. When the beta ends — or any time you decide you're done — your Vault, room uploads, chats, House Facts, contacts, calendars, and every other piece of personal data are removed for good. We keep only anonymous, de-identified usage numbers (how many residents finished onboarding, average tokens per chat, which rooms get visited) so we can keep improving the product. Nothing in those numbers can be traced back to you.
Want a backup of your Vault before you go? Open the Vault and use Download my Vault to grab a zip of every file you've stored.
On the roadmap
Keep-on-device & bring-your-own-cloud
Being researched for after beta.
We considered shipping a "keep my Vault on this device only" option for beta and decided against it. The browser can evict locally-stored files under disk pressure, and "I lost my Vault because I cleared site data" is the exact failure mode we won't put a tester through. We're designing it for post-beta with proper key recovery and cloud-sync fallback.
Also on the roadmap: a "bring your own cloud" mode where your files live in your OneDrive, Google Drive, or Dropbox and we only keep pointers. Highest privacy story, highest engineering cost — we'll build it if beta feedback shows real demand.
Common worries
Can LifeHouse staff (Iris, Warden, Clara…) read my Vault?
No. The staff are AI personas; they don't read your Vault unless you hand them a specific file in chat. Even then, passwords stored in the Private Password Safe are encrypted with your safe code and never reach a staff conversation.
Can other residents see my files?
No. Row-level security physically prevents another resident's account from reading any row that isn't theirs.
Can LifeHouse admins read my private data?
No. Admins see operational counts (how many uploads exist, error rates), submitted issue reports and suggestions, and admin-curated content like House Rules. They cannot open your Vault, your room drawers, or your chats.
What happens when I delete my account?
Every row that identifies you is permanently removed: Vault items, uploads, chats, House Facts, contacts, calendars, inventory, health entries, pets, vehicles, students, family entries, follow-ups, notifications, profile fields, tester membership, beta application, and your auth record. Aggregate usage numbers (token counts, room visits, AI usage totals) are kept but de-identified — user_id is set to NULL. There is no soft-delete or 30-day window during beta; when you confirm, it's gone.
Where do AI replies actually go?
Your prompt is sent to the Lovable AI Gateway, which routes it to Google Gemini or OpenAI to generate a reply. The reply comes back and is stored in your account along with the prompt so the staff member can remember the conversation. The model providers do not retain your prompts for training.
Who are the subprocessors?
Hosting, database, storage, and authentication run on Lovable Cloud (Supabase infrastructure). AI inference is routed through the Lovable AI Gateway (Google + OpenAI). Voice (text-to-speech) is provided by ElevenLabs when enabled. Payments — including token top-ups — run through Stripe.