← Built Health

Privacy Policy

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.

Data we handle

• Account identifiers from our authentication provider (Supabase Auth).
• Meal logs, nutrition observations, resolved nutrition estimates, evidence trails, and conflicts.
• Barcode lookups and Open Food Facts source payloads, stored separately from your corrections.
• Nutrition-label photos, meal photos, and medication-bottle photos only while they are being processed for OCR or identification — they are analyzed and discarded, not stored.
• Progress photos stay on your device by default and are never uploaded. If you turn on progress-photo backup, they are stored in your private account so a new phone can restore them — readable only by you under row-level security, never shared, never analyzed by AI, and deleted when you delete the photo. That is private storage, not end-to-end encryption.
• Voice input is transcribed on your device or by your device's operating system; we receive the resulting text, not stored audio recordings.
• Medication, vitamin, dose, injection-site, reminder, refill, and symptom records.
• Health diary entries you write, their AI-generated reflections, and a derived diary memory summary.
• Recipes you save and your food preferences (allergies, dislikes, tolerances).
• Subscription tier and entitlement status.

How data is used

• To resolve meals into nutrition estimates with an audit trail.
• To preserve your daily protein and nutrition history.
• To run medication and vitamin schedules, reminders, refill estimates, and personal symptom notes.
• To organize your diary entries into patterns from your own words, questions to bring to your own doctor, and generic reading topics — never medical advice.
• To meter cost-sensitive AI features and prevent abuse.
• To improve reliability, debug errors, and protect the service.

AI processing

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.

Health diary

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.

What we do not do

Retention and deletion

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.

Security

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.

Contact

Privacy requests and account deletion requests: privacy@builthealth.com