Email is the only support channel, and it's read by a person. Expect a reply within a few days.
If you're reporting something broken, it helps a lot to include your iOS version, the app version (bottom of Settings), which model you had selected, and what you were doing when it went wrong.
No. The app estimates on its own keys, under a daily limit shared between everyone using it. Adding your own key at the bottom of Settings is an override: that provider then talks to your account directly, nothing passes through the app's server, and the shared limit stops applying to it.
That provider isn't funded on the shared keys, so it's only available if you supply a key for it. Pick a different model, or add a key for that provider in Settings. Keys are per provider and held in the iOS Keychain.
The shared allowance resets daily. If you'd rather not wait or you use the app heavily, add your own API key for one provider — that removes the shared limit for it. Keys come from Google AI Studio, Anthropic or OpenAI.
It's an estimate from a photo, and it can be. You can edit it before saving — the model proposes, you decide. After saving, tap the entry on Today or in History to adjust the portion weight; the calories and macros rescale with it. You can also refile it under a different meal or delete it there.
That's deliberate, and only happens when the leading model says it isn't sure. The app asks the one question that would most improve the estimate — "was the chicken grilled or fried?" — and re-runs it on your fallback model with your answer. Confident estimates never trigger it. Set the fallback to None in Settings if you'd rather just see the unsure estimate and correct it yourself.
Nothing is lost. If you were offline, or the provider was busy, the entry is saved on your phone with its photos and estimated in the background. Offline entries go the moment you're back online. A busy model is retried after one minute, then twice more, and if it's still busy the entry switches to your backup model on its own. Today shows what each queued entry is waiting for and when the next attempt lands, with a Retry button if you'd rather not wait.
Meals are assigned from the photo's capture time, so an entry is filed under when you ate, not when you got around to logging it. Typed entries with no photo use the current time. Tap the entry to refile it.
You said no to training during setup, which removes the tab entirely. Turn it on in Settings and it comes back, along with the questions about your equipment and sport.
No. Changing any of it in Settings keeps your place in the session rotation and everything you've logged.
Progression stays quiet until it has two data points: hit the prescribed sets and reps twice in a row and it will suggest adding load, with an increment sensible for that weight range. It won't guess from a single session.
On your iPhone, in the app's own storage. There's no account and no cloud sync — which also means nothing to lose access to. If your iPhone is backed up to iCloud or a computer, the app's data is included in that backup. Deleting the app deletes all of it, permanently.
Delete individual food entries or workout logs inside the app, or delete the app from your iPhone to remove everything at once. See the privacy policy for the small amount of operational data the shared proxy holds and how to have it cleared.
Calorie and macronutrient figures are estimates produced by an AI model from a photo or description. Your daily goal comes from a standard population equation (Mifflin-St Jeor), not from measuring your body — treat it as a starting point and correct it against what the scale actually does over a fortnight. None of it is medical, dietary or fitness advice; talk to a qualified professional before making decisions about your diet or training.
Both are welcome at the address above. Concrete beats general — a photo of the meal that was estimated badly, or the exact steps that produced the wrong screen, is worth more than a description of the feeling.