What we collect:nothing.

On your device

Everything you log is stored on your phone and syncs through your own private iCloud account, so it reaches your other Apple devices and your new phone. That is Apple's private database, not a BiteDeck one: we cannot read it, and we never receive or store a copy. BiteDeck's data is also included in your personal iOS backup automatically. Read more about local-first.

What BiteDeck sends off-device

• Food photos you scan

  Sent through BiteDeck's own proxy to Google Gemini Vision for recognition, then returned as an item list. We do not retain your images. We do not train on them. If you'd rather not scan, skip it — every meal can be logged by search, barcode, label OCR, or freeform.

• Exercise descriptions you paste

  Sent through the same proxy for parsing into duration/intensity/calories. Not retained. Not trained on.

• Ingredient descriptions you add

  Sent through the same proxy for structured parsing. Not retained. Not trained on.

• Coach messages

  On-device context about your day (macros, recent meals, profile basics) accompanies each Coach turn so the reply is relevant. Chat history lives on your device; you can delete it at any time.

No message, photo, or description is ever tied to a BiteDeck account, because there is no account.

Apple Health

HealthKit is the only external integration, and it is opt-in. You choose to connect. Every metric — steps, active energy, workouts, weight, body fat, dietary energy, macros, fiber, sugar, sodium, water — has its own toggle. Turn any one off without disconnecting everything.

The Health connection itself is on-device: readings move between HealthKit and BiteDeck's local store without touching a server. Imported entries then sync through your iCloud like the rest of your log, and if you use the optional AI Coach, your recent totals, weight trend, and body fat — including values imported from Health — are part of the request that generates its answer.

This website

This site uses Google Analytics to count page visits and to see which pages lead people to the App Store. That is ordinary website traffic measurement, and it does set analytics cookies. It tells us that a page was read and roughly where the visitor came from — nothing about who you are.

It has no connection to the app. BiteDeck has no server for the app to report to, so nothing you log, weigh, eat, or photograph can reach this or any other analytics tool. The two systems never touch.

Your controls

• Export

  Settings → Export Data → CSV (weights + meals) or PDF (30-day summary). Share anywhere or keep a local copy.

• Erase

  Settings → Erase All Data → type ERASE to confirm. Nukes SwiftData, progress photos, UserDefaults, and every BiteDeck-authored HealthKit sample. Irreversible on purpose.

• Revoke HealthKit

  Apple Health app → Sharing → BiteDeck → turn off any metric or all of them. BiteDeck detects the change silently and stops writing.

Contact

Questions? support@bitedeck.app. We read every message.