Data
Privacy
FitBuddy is designed so your food log and API keys live on your phone. Network calls only happen for features you use. There is no FitBuddy account.
Who is responsible
FitBuddy is developed by Anant (open source, GPL-3.0). For privacy questions or remote data-deletion requests, email fitbuddy31@proton.me and include your Support ID (Settings → Backup) when relevant.
Stored on your device
- Profile, body readings, daily targets
- Food and exercise logs, meal presets, saved foods
- AI provider choice, API keys / OpenRouter token, model preferences
- Reminder schedule
- Optional local JSON backups (optionally password-encrypted)
- Anonymous Support ID (not your name or email)
Uninstalling removes local data unless you kept an export or cloud backup under your Support ID. FitBuddy does not use Android Auto Backup (Google’s automatic app-data backup). Supported backups are local JSON export and optional MongoDB cloud backup only.
Sent to your AI provider
When you analyze a meal photo or text, estimate workout calories, use Progress Coach, or request optional AI-assisted target selection, FitBuddy sends only the content needed for that feature to the provider you configured. This can include meal photos or descriptions, relevant profile details, and compressed progress metrics.
A target-selection request can include age, sex, height, current weight, selected activity, goal, current calorie and protein targets, aggregated workout/body/nutrition evidence, and each complete locally calculated candidate (ID, calories, macros, target weight, recommended activity, and adjustment). Raw body-reading rows and full food-log history are not included in that request.
Target arithmetic, safety bounds, and candidate numbers are always calculated on-device. A configured provider may select only one exact local candidate ID and add a short coaching note; it cannot supply or edit target numbers. See the calculation and AI boundary.
Choose a provider you trust — their retention rules apply. Prefer local Ollama if you want analysis on your network. FitBuddy does not upload your full history to a FitBuddy app server — there isn’t one.
Optional personal cloud backup
When enabled, FitBuddy can upload gzip-compressed, AES-256-GCM encrypted backups keyed by your Support ID. Encryption happens on-device before upload. A custom password is optional (blank uses Support ID–based protection for convenience). Off by default. Details: Encryption.
To request deletion of a cloud backup you no longer control from the app, email fitbuddy31@proton.me with your Support ID.
Other network use
- OpenRouter OAuth — browser sign-in when you choose it
- Open Food Facts — barcode product lookup (decode is on-device); optional contribution when you add a missing product
- Exercise catalog / demo GIFs — catalog JSON and GIFs via CDN (cached on disk after first fetch)
- GitHub — release / update checks on GitHub builds; APK opens in your browser
- F-Droid — F-Droid builds may check for a newer package listing
- Donations — Razorpay, payment apps, or GitHub Sponsors open only when you choose them
Optional crash reports (Sentry)
If crash reporting is enabled, anonymous crash/ANR data may be sent to help fix bugs. Traffic goes through FitBuddy’s cloud ingest to Sentry. Your name is not sent. Not sent: meals, photos, API keys, freeform food text.
Opt out anytime in Settings. Share your Support ID when asking for help. To request deletion of Sentry events tied to your Support ID, email fitbuddy31@proton.me.
Your rights & deletion
- Local data — delete entries in-app, export/import JSON, or uninstall.
- Cloud backup / Sentry — email fitbuddy31@proton.me with your Support ID and what you want removed.
- AI providers — contact the provider you configured; FitBuddy does not control their retention.
Permissions (typical)
- Camera — food photos and barcodes
- Photos / media — gallery pick
- Notifications & alarms — optional daily reminder
- Internet — AI, barcode lookup, updates, optional cloud / crash reports
FitBuddy is GPL-3.0 — inspect the code.