Privacy

What doesn't exist can't be breached.

In 2026, a major calorie app's user database — names, emails, height and weight, meal histories — appeared on a breach forum. Health data is exactly the kind of data you don't want in anyone's database. Proba's answer is architectural, not contractual:

• No account. There is nothing to sign up for. Your food log lives on your device (and in your personal iCloud backup, under Apple's encryption — not on our servers).
• Photos are analyzed, not stored. A meal photo is processed to identify foods and portions; we don't keep a server-side copy or build a photo history of your life.
• Voice stays on the phone. Dictation for describe-a-meal uses Apple's on-device speech recognition. Audio never leaves the device.
• No ads, no analytics SDK. There is no third-party tracker watching how you eat.
• Apple Health on your terms. Writing meals to Apple Health is optional and permission-gated — and only ever writes values that were actually measured.

What we do process

Meal analysis requires sending the photo (or your typed description) to our server for the AI + USDA lookup; the result comes back to your device and the processing input isn't retained as your history. Purchases are handled entirely by Apple — we never see payment details.

The honest trade-off: no account also means we can't recover your data if you lose your device without a backup, and there's no web login. We think that's the right trade for health data.

Method details live on the methodology page.