Effective: 29 October 2026
Onebite is a private food diary for iPhone. It has no advertising or analytics SDK, does not track people across apps or websites, and does not sell personal data.
Onebite stores your food diary, nutrition targets, weight history (including weights imported from Apple Health), recipes, pantry, shopping list, meal plans, saved meals, dietary preferences, settings, and imported color themes locally in the app and its App Group container. Progress photos you add are saved as files in the app's Application Support folder on the iPhone (see Photos below). API keys and the app's App Attest key id are stored in the iOS Keychain, set to stay on this iPhone. The widget reads a small current-day summary and theme choice from the App Group.
The personal diary is not uploaded to Onebite or synced through iCloud. You can export a backup or CSV through the iOS share sheet; Onebite only writes that file to the destination you choose.
Device and iCloud backups. Because the diary holds weights from Apple Health, Onebite marks its personal files so iOS leaves them out of iCloud Backup and computer backups: the diary database, the safety copies Onebite saves before a restore, your progress photos, and the widget's queue of water you added. Files you export are yours and are not marked; where they go depends on the destination you choose. The consequence: if you restore an iPhone from an iCloud or computer backup, or move to a new one, your diary and progress photos do not come back with it. Export a backup file first. A few small items, such as settings and the widget's current-day summary, are ordinary app preferences that iOS can include in a device backup. Your cloud consent choices (below) are also kept in app preferences, outside Onebite's own backup file.
Health access is optional. With your permission, Onebite can:
Weights, waist and body-fat readings read from Health are saved in your local diary so Progress can show them. Onebite uses Health data only to show and update your own diary and progress. It is not used for advertising, marketing, profiling, or data mining. Onebite does not send Health data to food databases or iCloud. Steps, waist and body fat never leave the iPhone. Two Health-derived figures can reach an AI service: your latest weight (which can come from Apple Health) and today's active calories burned. They go only with an Ask Onebite question you agreed to send to the cloud (see below).
Onebite uses the system photo picker, so it receives only the image you choose. A camera photo taken to recognize food remains in app memory unless you enable Keep photos I take, in which case iOS saves it to your photo library.
Progress photos are different. A photo you add on the Progress screen is saved on the iPhone, resized to at most 1600 pixels on the long side, in Onebite's Application Support folder with iOS file protection, and stays until you delete it in the app or delete the app. Progress photos are not sent to any AI service or other server, and are left out of iCloud and computer backups (see above). Only a photo you choose to have read, as described next, is ever sent.
When you explicitly ask Onebite to recognize a plate, nutrition label, meal, spoken or typed meal description, or recipe, the selected image or text is processed by the reader shown in the app:
The first photo that would go to OpenRouter, DeepSeek or Onebite AI waits for your yes: Onebite names the services that would receive it, and nothing is sent until you tap Send. Each service (and each OpenRouter model) asks once; after that, photos to it go without a question unless you turn on Settings → AI → Ask before sending a photo, which asks every time. Your yes is kept only on this iPhone and is not part of an exported Onebite backup.
On an iPhone with a LiDAR camera, with Settings → AI → Measure plates with LiDAR turned on (it is off unless you turn it on), a plate photographed in Onebite's camera is also measured on the iPhone from the camera's depth map. The depth map never leaves the iPhone; only the measured sizes (the plate's width and the food's area, height and volume) go with the photo to the reader.
The proxy does not log or store what you send or what comes back. To keep it for Onebite users only, the app proves it is genuine with Apple's App Attest: your iPhone makes a key that Apple vouches for. It is a per-install device identifier, with the private half kept on the iPhone. The proxy keeps a record for that key: its public half, a counter and today's request count, so it can apply a daily limit. The record has no automatic expiry. The key is not linked to your name, Apple ID or diary, so Onebite cannot match a record to you, and a new key is made if you reinstall. Cloudflare receives ordinary connection information such as an IP address; OpenRouter, Google and OpenAI receive the request from the proxy, not from your iPhone.
Onebite does not attach your name, diary, weight history, Health data, or advertising identifier to those photo, label, meal and recipe requests. A provider account may associate requests with an API key you supplied. The provider’s terms and retention policy apply to content sent to it. You can remove your keys at any time in Onebite Settings.
Voice logging is optional and starts only when you tap Start listening. It asks for microphone and speech recognition permission. Onebite sends the microphone audio to iOS speech recognition, which turns it into text you can edit. Onebite does not require recognition to happen on the iPhone, so Apple may process the audio on its servers; whether it does depends on your language and device. Apple's speech recognition terms and privacy policy apply to that processing. Onebite does not save the audio. The text is kept only if you log it. If you then tap Find foods, the text is sent to the reader shown in the app, as described above under AI providers.
Ask Onebite answers a question about your diary. On an iPhone with Apple's on-device model, it is answered on the iPhone and nothing leaves it. Otherwise it falls back to the same cloud service your photos use (Onebite AI, which currently means Onebite's proxy, OpenRouter and Google's Gemini 3.8 Flash, with OpenAI's GPT-6.1 Sol as the fallback; or OpenRouter or DeepSeek with your own key), together with figures the app worked out: today's calories and protein (targets, eaten and left) and how many entries there are, the week's averages and how many days hit the protein target, average water, your latest weight (which can be a weight imported from Apple Health), goal weight and weekly weight trend, today's calories burned (Apple Health active energy and logged exercise, if you allowed Health access), your diet setting, the names of the foods in your pantry, and a few suggested foods that fit. It never includes photos or a list of what you ate.
Because the weight and burned-calorie figures are personal health information, nothing is sent until you agree: the first question to each cloud service shows what goes and who receives it, and waits for Send. This consent is separate from the one for photos, and is asked again for another service. Cancel sends nothing, and an answer from the iPhone's own model is never retried in the cloud. Your yes is kept only on this iPhone and is not part of an exported Onebite backup. The proxy does not store the question or the answer.
Settings → Send feedback sends your message and the kind you picked (problem, idea, other) to Onebite's AI proxy, which keeps it for up to 400 days so Onebite's developer can read it, and may forward it to the developer's own chat workspace. The app version, iPhone model and app language are included unless you turn that off, and a reply address only if you type one. If you provide an address, it is stored with that feedback record. Feedback is not linked to your App Attest key, name, Apple ID or diary, and is not used for tracking.
If enabled in Settings, food search text and scanned barcodes are sent to Open Food Facts, FoodRepo (when configured in the build), USDA FoodData Central and Onebite's public CloudKit database of shared foods to return nutrition matches. The Swiss, ANSES Ciqual and USDA food tables are bundled and work offline. When you import a recipe URL, Onebite contacts that website to retrieve the page. Those services can receive the requested terms or URL and ordinary connection information such as an IP address. Onebite does not use these requests for advertising.
Sharing a food with other Onebite users is off unless you turn on "Share with other Onebite users" for that food. Then its name, barcode, nutrition figures and allergens are saved to Onebite's public database in Apple CloudKit, where any Onebite user can find them in search. Apple attaches an anonymous, app-specific id to the record so only you can change or delete it; your name, Apple ID, diary, weight and Health data are never part of it. Turning sharing off for the food deletes the record. If you report a shared food, the report holds the food and the reason you picked, and the food is hidden on your device. Onebite's developer reviews reports and removes foods that are wrong, not food, or abusive.
If you create or join a household, household membership and shared grocery-list data are stored in your iCloud account with Apple CloudKit and shared with the people you invite. This is separate from the personal food diary. You can remove shared rows or leave the household in the app. Apple’s iCloud terms and privacy policy also apply.
Camera, selected Photos access, photo-library additions, microphone, speech recognition, notifications, Health access, and iCloud household sharing are optional. Onebite remains usable for manual local logging without them. You can change system permissions in iOS Settings. Reminder notifications are scheduled on the device.
Local data, including progress photos, remains until you delete individual content or delete the app. Files you export remain wherever you save them. Health samples remain under your control in Apple Health. Shared household data remains in iCloud until it is removed or the share is deleted. Third-party services may retain a request according to their own policies.
Onebite does not operate a user-account database, so there is no separate Onebite account to delete. To stop cloud AI, set Settings → AI to Off and remove any API keys you saved, or simply do not ask for recognition. With AI off, Apple's cloud model still reads a photo when you tap Use Apple's cloud model. To confirm each photo before it is sent, turn on Ask before sending a photo. To revoke Health, Camera, Photos, Microphone, Speech Recognition, or notification access, use iOS Settings.
For privacy questions or deletion help, email support@h1.lol. Please do not include health information, photographs, API keys, or other sensitive personal data in your message.