Your data lives in on-device SQLite
Food logs, weight history, recipes, workouts, and protocol logs are stored in a local SQLite database on your phone. That's not a marketing abstraction — it's a database file on your device, not a row in a vendor's cloud.
No account required for core tracking
You can log food, weight, workouts, and protocols without creating a BodyDex account. A tracker that demands an email before your first entry is building a profile of you; a local-first one doesn't need to know who you are.
No centralized database of your food entries
There is no server-side BodyDex table of what you ate. Your log can't be sold, subpoenaed from us, or leaked from our infrastructure, because it isn't in our infrastructure.
AI features send only the photo or question
When you use AI photo scanning or the coach, only the photo or the question is sent for processing, with no name or account identity attached. Photos aren't saved server-side (unless you explicitly send one with a scan-accuracy report — auto-deleted in 90 days) — the answer comes back and lands in your local database. Our privacy policy details how AI providers may use submitted content.
Zero ad SDKs
BodyDex ships with no advertising SDKs. Nothing in the app is instrumented to build an ad profile from your eating habits, weight, or protocols.
You choose which food databases are used
Profile → Food Databases shows which source powers food search, barcode scans, and AI scans, and has a switch to turn any of them off (one search database always stays on so search keeps working). Foods from the community database, Open Food Facts, are labeled as community data with a note that entries can be inaccurate, and you can flag incorrect data from the food detail screen.
Export and delete are yours
Export your data as JSON or CSV from Profile → Export Data any time. Delete everything from Profile just as easily. Local-first means the data is yours to take or destroy — no support ticket required.