Last updated: August 2026
FitOdds has no sign-up, no login, and no user profiles. Nothing you do in the app is tied to your name, email, or identity — we couldn't link it to you if we wanted to.
Your weight, workouts, meals, and body-scan history live on your iPhone, stored on-device. Where you allow it, your weight is synced with Apple HealthKit (nutrition and workout sync are coming later and will ask permission when they do). On Apple Watch, FitOdds reads your heart rate and resting heart rate during a workout to compute your live training zones on-device — that too stays on your watch and iPhone. Delete the app and its local history is gone (HealthKit data stays in Apple Health, under your control).
When you scan a meal or do a body scan, the image is sent to our server for one purpose: analysis by Anthropic's Claude AI to estimate food content or body measurements. FitOdds processes scan images in memory and does not retain them after the analysis request. Body scans also send your height, weight, and sex alongside the images — that's what makes the measurements possible.
If you choose to save a body scan, FitOdds saves one front progress photo locally on your iPhone. That local progress photo is separate from the transient analysis image: it is not uploaded to or retained by FitOdds servers. Your scan history and any saved progress photo remain in the app on your device.
One honest caveat: the analysis itself is performed by Anthropic's Claude API. Anthropic may retain API inputs and outputs for up to 30 days for trust-and-safety purposes before deletion, per their commercial terms. Anthropic does not train on this data.
If you use the AI coach, what you say is transcribed on your iPhone — the audio never leaves your device. Only the final text is sent to our server and to Anthropic's Claude API to adapt your training plan, under the same retention terms as photo analysis (up to 30 days at Anthropic, nothing kept on FitOdds servers). The accepted transcript and the resulting adjustments are stored on your device with your coach profile, and you can delete them any time from Profile.
The website uses session storage only to avoid counting the same landing view or App Store click more than once in a browser tab session. It does not create or send a cookie or visitor identifier. FitOdds keeps only aggregate daily totals for up to 13 months. An App Store click shows intent — it does not confirm a download or install.
Coaching-effectiveness counters are also retained only as aggregate daily totals for up to 13 months. They tell us whether a category of suggestion is useful overall; they cannot be connected back to a person, device, meal, workout, medication entry, or body measurement.
Requests carry a random device token to enforce fair-use rate limits and keep referral attribution from being counted twice. It is a random ID created on install — never linked to your name, email, or an account. Daily usage counters referencing these tokens are kept for up to 13 months, then deleted.
Referral records use a keyed one-way digest of that random install token; the raw token is not saved in the referral store. Ordinary iOS sharing does not tell FitOdds who received a link, so we cannot see or store a recipient's name, contact details, or a list of people who have not joined. Referral counts are kept while the referral program operates so inviters can see their results.
If someone separately enrolls as an affiliate, an administrator may add the contact details and reconciliation notes they provide to the referral dashboard. Anonymous referral claims are treated as unverified and are not automatic proof that a payment is owed.
If you redeem a promo code, the code you typed is checked against our server's list and the resulting access pass is stored only on your phone. The server counts redemptions in the same anonymous daily totals — it does not record which device redeemed which code.
Email kamatbot@gmail.com and a human will reply.