Built Health is a consumer wellness app for nutrition logging, medication and vitamin tracking, reminders, and symptom notes. It is not a medical device, provider portal, payer workflow, or emergency service, and it never provides medical advice, diagnosis, or treatment instructions.
Label OCR, meal-photo identification, meal descriptions, recipe import and generation, medication-label reading, and health-diary reflection run through Built Health's server-side functions. Calls to AI providers are configured not to retain data (store:false) where the provider supports it. API keys stay server-side and are never shipped inside the mobile app.
Diary entries are private to your account. When you save an entry, Built Health processes the text server-side to produce a reflection (patterns from your own words, questions for your own doctor, generic research topics) and to maintain a derived memory summary so the app can remember your history. Reflections are structured and filtered so they never evaluate your medications, doses, or treatment decisions. When you ask a routine question about items you track, a reflection may include general, label-style information (like “commonly taken in the morning, with or without food”) — always deferring to your doctor's or pharmacist's directions, and never dosing amounts or treatment advice. You can delete any entry, or all diary data — deleting removes entries, reflections, and the derived memory.
Meal, medication, symptom, diary, and evidence records are kept until you delete them or delete your account. Photos are processed and discarded, not retained on our servers.
Your data is stored behind row-level security with owner-only access policies. Cost-control and entitlement records are server-owned; the app can read your limits but cannot raise its own tier or reset usage meters.
Privacy requests and account deletion requests: privacy@builthealth.com