Privacy
Can I Eat? is designed so personal health context can stay inside the user's device. The homepage and API proxy are used for public reference lookups and selected data pack downloads, not for collecting a user's private health profile.
Information such as the user's health notes, allergies, supplements, and current medication list is used by the app to prepare on-device reference explanations. This information is not designed to be uploaded as a personal profile to the website server.
When the app needs public reference data, it may send limited lookup values such as a barcode number, product name, drug name, product code, selected country code, or data pack file path to https://canieat.net. These values are used to request public product, food, drug, or data pack information.
The app should not send a combined personal profile such as disease history, medication list, food item, and AI prompt together to the website. The safer design is to retrieve public reference data first, then let the app interpret it locally with the user's own context.
Camera access is used only when the user opens the barcode scanner. The camera is not used in the background, not used for unrelated purposes, and not used to upload personal photos. Barcode recognition is limited to reading the product code needed for lookup.
The app does not automatically download every data pack. The user selects one country or regional pack, and the app downloads only that ZIP file from the website, extracts it inside app storage, installs the database, and removes the temporary ZIP.
The service is not designed to sell, rent, or trade app users' personal health information. The technical direction is data minimization: keep sensitive context on device and send only the minimum lookup data needed for public information retrieval.
This page explains the intended technical privacy structure for the app. Final privacy policy and Play Store declarations should match the actual released app behavior.
