OFood Calories — Privacy Policy
v1.6 (2026-11: barcodes the app looks up through our server; v1.5 2026-10: the other foods you log from the same photo, and voice entry; v1.4 2026-10: what the app writes to Apple Health, and the backup file you keep; v1.3 2026-10: crash reports say which screen the app was on; v1.2 2026-10: searches that found nothing added; v1.1 2026-09-22: depth maps and crash reports). English is the governing language. Effective upon publication at this URL. Keep consistent with the App Store privacy questionnaire and PrivacyInfo.xcprivacy.
Controller: OFOOD LLC · Contact: info@ofood.org
What we collect, and why
When you use the food-recognition features, we collect:
- Food photos you confirm (each photo is checked on-device for people first);
- the food name you confirm, the names of any other foods you log from the same
photo and, where you provide it, the portion size, together with the app's recognition
results for that photo;
- technical capture data from the camera and motion sensors — never your
location;
- on iPhones with a LiDAR depth camera, a low-resolution depth map of the same
scene as the confirmed photo (distances in metres, no colour) — it helps estimate portion
sizes. It is captured only with the photo you confirm, is subject to the same on-device
people check, and is stored, reviewed and deleted together with that photo;
- crash reports generated by iOS when the app crashes or hangs (technical
stack traces of the app and the device model and OS version), with a short note the app keeps of
the screen it was on and the few screens before it, the phone's language, calendar and text
direction, and whether a daily goal is set. They are sent to our own servers at the next launch,
and never contain your photos, food names or diary contents.
- a random device identifier and basic device information (model, OS,
app version);
- anonymous usage statistics — counts and timings only (for example how fast
recognition ran, or which way you confirmed a food), sent to our own servers.
These never include your photos, food names, or diary contents, and never go
to any third party.
- searches that found nothing — when a food search in the app finds no match,
the words you searched for and, if you then add a food of your own, the name you gave it,
so that we can add that food for everyone. They are sent to our own servers with your random
device identifier, never with your diary, never to any third party, and are deleted after
180 days.
- barcodes the app does not know — when you scan a pack the app has not seen, it asks our server,
which looks the product up in Open Food Facts, a free food database, and keeps their answer about the product. We do
not keep which device asked about which barcode: the request carries your random device identifier only so that we
can limit abuse, and only a daily count is kept. Open Food Facts receives the barcode from our server, never your
device identifier.
We use this to improve food recognition and portion estimation for everyone, to
keep the service reliable, and to prevent abuse. That is what keeps OFood free.
What we deliberately do NOT collect
- Photos containing people. An on-device check runs before any analysis;
if a person is detected, the photo is not analyzed, not stored, not uploaded.
- The packaged products you scan and log: their names, numbers and how much you ate stay on your phone.
- Your food diary and calorie history (on-device only). Settings → Your data can save it, with your goals and
water, to a file you keep or send where you choose; we never receive it.
- Names, emails, phone numbers, contacts, precise or coarse location.
- Embedded photo metadata: uploads are re-encoded pixel data without EXIF/GPS.
- Apple Health data (calories, protein, carbs, fat and water, written to Health locally with your
permission; never read back except our own entries for delete-sync; never uploaded).
- Advertising identifiers. No ads, no tracking, no third-party analytics SDKs.
- Your voice. When you tap the microphone, what you say is turned into text on your iPhone by Apple's
on-device speech recognition; no audio is recorded, kept or sent anywhere. The words go into the search as if
typed, so a search that finds nothing is handled like any other (above).
Storage, review, retention
Uploads land in a quarantine queue in private cloud storage (Wasabi, us-west-1) reviewed by us. Rejected items are deleted. Accepted
items become part of our research datasets permanently (see Terms §3).
Pending (not yet accepted) items are deleted when you use
Settings → Delete my uploads, or on our routine queue cleanup.
Your choices and rights
- Consent regions (EU/EEA, UK, CH): uploads, and searches that found nothing, are sent only
after explicit consent; withdraw anytime in Settings — recognition keeps working on-device.
- Anyone: Settings → Delete my uploads removes pending contributions and saved searches tied to
your device identifier.
- Questions or requests: ofoodllc@gmail.com.
Security
Transport encryption (TLS) for all uploads; hardware-backed app attestation
(Apple App Attest) so only genuine copies of the app can submit; private,
access-controlled storage.
Children
The service is not directed at children under 13 (or the applicable age in your
region).
Changes
Material changes will be shown in the app and reflected at this URL
(https://api.ofood.org/legal/privacy) with a new effective date.