Privacy Policy.
This is the plain-English version. Lawyers will tell you to read every word. We'd rather you actually understand it.
What Bo collects
Account data
When you sign in with Apple, we receive your email and a stable user identifier from Apple. We never see your Apple ID password. If you give us your name during onboarding, we store that too — it's used to greet you in the app.
Health & food data you log
Everything you log in Bo — meals, weights, photos, restaurants, follow-up answers, voice transcripts — is stored on your device and synced to our backend (Supabase, hosted in the US) so you can pick up where you left off on a fresh phone. We do not sell this data. We do not share this data with third parties for advertising. Ever.
Apple Health
If you connect Apple Health, Bo reads your active energy, basal energy, workouts, steps, and weight to give you accurate burn / surplus-deficit numbers. Bo writes your meals back as dietary energy and macros so the Health app has the full picture. Reading and writing happens entirely on your device — Apple Health raw data never leaves your phone.
AI processing
When you scan a meal photo or speak a voice log, the photo and your text are sent to Google's Gemini API for analysis. Per Google's API terms, this data is not used to train their models. We do not store the photos or transcripts on Google's side beyond what's needed to display your meal in the app.
What we don't collect
- Your contacts, location, calendar, or device identifiers beyond what Apple gives us
- Tracking cookies, third-party analytics, or advertising pixels
- Browsing history outside of Bo
Why we collect what we do
We collect just enough data to make Bo work. Account data unlocks cloud sync. Meal data is the product itself. Apple Health and Gemini access is what lets Bo give you accurate numbers instead of guesses. That's the whole list.
How long we keep it
For as long as your account exists. When you delete your profile from the app's Settings, we wipe your meals, weights, profile, photos, and notification preferences from our servers. Apple's auth records take a little longer to clear — typically 30 days — and that part is governed by Apple, not us.
Your rights
- Export: email hello@bo.appfrom the address tied to your account and we'll send you a JSON dump of your data within seven days.
- Delete: Settings → Account → Delete profile in the app. One tap and a confirm. If anything goes wrong, email us and we'll wipe it manually.
- Correct: every piece of data Bo collects is editable inside the app. You don't need to ask us to change it.
- Stop syncing: sign out from the Settings tab. Your local data stays put; cloud data stays as-is until you delete it.
Children
Bo is not designed for anyone under 13 and we don't knowingly collect data from them. If you believe a child has signed up, email us and we'll delete the account.
Subprocessors we trust
- Apple — auth, in-app subscriptions, push delivery, HealthKit (entirely on-device).
- Supabase — auth, Postgres, file storage. US-region. Encrypted at rest.
- Google Cloud (Gemini API) — meal-photo and voice-text analysis. Per-request, not retained.
- Open Food Facts — public barcode lookup. Anonymous; no user data is sent.
Changes to this policy
If we change anything material, we'll let you know in the app before it takes effect — not buried in an email you won't read. The "last updated" date at the top of this page is our commitment to that.
Contact
Email hello@bo.app. A real person reads every message.