This policy describes the current NextMeal build. NextMeal does not operate an account or backend service and does not receive meal photos, nutrition history, goals, or model prompts from the app. Optional NextCoach sharing uses only local device transport.
1. Scope and Current Product
This policy applies to the NextMeal iOS and Android apps and this product website. The current app provides camera capture; typed and supported on-device dictated descriptions of meals and grocery foods; on-device analysis; editable nutrition estimates; daily goals; a local meal diary; seven-day logged trends; and optional local nutrition sharing with NextCoach. It does not include accounts, advertising, analytics, cross-app tracking, cloud inference, remote meal analysis or transcription, or active health-data access.
2. Information Handled on Your Device
When you choose to scan or describe food, the app locally handles a camera image or food description, optional live dictation audio and transcript, model prompts and output, estimated nutrition, your corrections, daily goals, and meal records you explicitly save. Dictation audio exists only during the active recognition session and is not saved. These items may be personal information when they relate to you, but the current app does not transmit them to the developer.
For optional NextCoach integration, NextMeal derives only daily calorie, protein, carbohydrate, and fat totals plus your current targets. It excludes photos, meal names and descriptions, ingredients, advice, confidence, fibre, sugar, sodium, prompts, transcripts, and raw model output. NextMeal does not collect precise location, contacts, advertising identifiers, account credentials, payment information, or health records. The website is delivered by a hosting provider and may necessarily process standard request information such as an IP address and browser headers under the host’s own operational practices; NextMeal does not add advertising or analytics scripts.
3. Purposes, Necessity, and Data Minimization
Local information is processed only to perform the feature you request: display the camera, transcribe an actively dictated food description, create an editable estimate, save a diary entry, calculate progress, prepare a minimized local NextCoach snapshot or manual export, or erase local data. Where European or UK data-protection law applies, this processing is limited to providing the app functionality you request and the developer’s legitimate interest in operating a private, safe product. Optional camera, microphone, speech-recognition, and NextCoach-sharing processing begins only after an explanation and your choice to use the related feature. Typing remains available without camera or audio permissions, and NextMeal remains fully useful without NextCoach.
4. Camera Permission and Photos
Before the operating system asks for camera access, NextMeal explains why it is needed. The app requests access only after you choose “Continue to camera.” You may decline and enter a meal manually. If access is denied, you can later change it in system settings.
Captured images are held temporarily for on-device analysis and review, then discarded when you retake, save, or leave the result. Saved diary entries contain nutrition values and text, not the meal photo. The current app does not request photo-library access.
5. Typed Descriptions and Dictation
Typed descriptions are processed locally as model input. Before requesting microphone or speech-recognition access, NextMeal explains that access is used only while you dictate a food description. When supported, the app requires the platform’s on-device speech recognizer, stops the audio session when dictation ends or the screen closes, and does not save audio. If local speech recognition is unavailable, NextMeal does not switch to cloud transcription; you can continue typing.
6. On-Device Models
On supported Apple devices, NextMeal uses Apple Vision to classify images and Apple Foundation Models for structured nutrition reasoning from images or text. On supported Android devices, it uses Gemini Nano through Android AICore and first-party Google APIs. Model inputs and outputs remain on the device in the current implementation.
The operating system or platform vendor controls model availability, downloads, safety systems, and its own device-level services under its terms and privacy settings. NextMeal does not silently use a cloud model when the on-device model is unavailable. Unclear, non-food, or unreliable input is rejected or opened as an incomplete manual entry rather than being saved as a confident result.
7. Storage, Retention, Backups, and Deletion
Saved meals, preferences, and goals remain in app-local storage until you delete them. Typed descriptions and transcripts are temporary working input; only the nutrition entry you explicitly save is retained. When enabled by platform configuration, NextMeal also maintains a minimized local convenience snapshot for NextCoach and refreshes it after successful meal or goal changes. NextCoach checks it only after you connect NextMeal and bring NextCoach to the foreground; neither app synchronizes while terminated.
You can delete individual meals, clear meal history while retaining goals, or use “Delete all local data” in Settings to erase saved meals and reset goals. These actions refresh NextMeal’s source snapshot, but they do not remove nutrition that NextCoach previously imported; use NextCoach’s disconnect or deletion controls for its copy. Manual `.nextmeal` exports use a temporary cache file that NextMeal removes after the native share flow completes. Deleting the app removes app-local data, subject to operating-system backup, restoration, and shared-container behavior.
Depending on your device settings, Apple or Google may include app data in a device backup or device-to-device transfer. Those platform services are controlled through your system or account settings.
8. Collection, Disclosure, Sale, Sharing, and Transfers
NextMeal does not receive the app data described above, disclose it to advertisers or data brokers, sell personal information, or share personal information for cross-context behavioral advertising. If you connect NextMeal in NextCoach or select a recipient from the manual share interface, the minimized nutrition envelope is disclosed locally to that app at your direction. Apple limits the automatic snapshot to the shared App Group. Android limits automatic reads to production apps with the same signing identity through a signature-level, read-only provider. Manual sharing grants temporary read access only to the recipient you choose.
The app contains no third-party analytics, advertising, attribution, account, cloud database, remote meal-analysis, or cloud-transcription SDK. The Android app does not request internet permission. Because the current app does not transmit its meal data to the developer, NextMeal does not transfer that data internationally. NextCoach, Apple, Google, app stores, device backups, and website hosting have their own local data or platform responsibilities governed by their own terms and controls.
9. Your Choices and Privacy Rights
You control camera, microphone, and speech-recognition permissions, every saved estimate, all locally stored app data, whether to connect NextMeal from NextCoach, and every manual export recipient. Typing is available without camera or microphone access. Settings explains the NextCoach snapshot, offers the manual fallback, links to this policy and the Terms of Use, and includes an in-app control to delete all local NextMeal data.
Depending on where you live, you may have rights to know, access, correct, delete, restrict, port, or object to processing of personal information, and to appeal or complain to a regulator. Because NextMeal does not maintain an account or receive your local app data, the developer cannot retrieve or export data it does not possess; use the in-app controls for NextMeal data and NextCoach’s controls for data already imported there. Requests concerning information actually held by the developer may be made through the verified support contact published with the official store listing.
10. Regional Notices
European Economic Area and United Kingdom: NextMeal follows purpose limitation, minimization, local retention, transparency, and privacy-by-design for current app processing. You may complain to your local data-protection authority.
California: NextMeal does not sell personal information or share it for cross-context behavioral advertising, does not offer financial incentives for personal information, and does not use or disclose sensitive personal information outside the feature requested. If the CCPA/CPRA applies to a future version, applicable rights to know, correct, delete, opt out, limit, and receive equal service will be honored.
Australia: NextMeal’s current design supports the Australian Privacy Principles through transparent notice, limited local use, security controls, access through the app, correction before saving, and deletion controls. Complaints may be sent through the verified support contact in the official store listing and, where applicable, escalated to the Office of the Australian Information Commissioner.
11. Children
NextMeal is a general wellness tool and is not directed to children under 13. It does not knowingly collect children’s personal information from the app. A parent or guardian should supervise nutrition decisions for minors and use qualified professional advice where appropriate.
12. Security
NextMeal reduces exposure by avoiding accounts, remote inference and transcription, analytics, and advertising; keeping meal content local; discarding photos and audio; minimizing NextCoach output; using an Apple App Group or Android signature permission for automatic access; and relying on platform sandboxing. Manual exports are readable by the recipient you select and may then be stored under that recipient’s controls. No method of storage is guaranteed to be perfectly secure. Keep your device and operating system protected and up to date.
13. Changes
Material privacy changes will be reflected in the app, App Store privacy details, Google Play Data safety form, store copy, permission prompts, and this page before the related behavior is released. The “Last updated” date identifies the current version.
14. Contact
The verified developer identity, privacy contact, and support address must be published in the official App Store and Google Play listing before public release. Until that listing is live, this repository and policy do not claim a verified legal contact that has not been supplied.