Your food is your business.

The short version: no account, no ads, no tracking. Your health profile and food log stay on your phone.

What stays on your device

Your profile: allergies, health goals, eating style, avoid list, preferred store, energy target.
Your scan history, including small thumbnails of label photos.
Your food log.
Whether you have Food.FM Plus, copied from Google Play so it works offline.

These are kept in your browser’s local storage. We never receive them. Delete them any time under Profile → Delete all my data, or by clearing your browser data.

What leaves your phone, and why

Food.FM has no accounts and stores no record of what you scan on any server. Your phone contacts these services only when you use the feature:

Open Food Facts receives the barcodes you scan, directly from your phone, to return product data. Like any website, it sees your device’s IP address.
Food.FM’s server, which runs on Google Cloud Run, receives a product’s barcode and your country setting when you view its swaps, and searches Open Food Facts for better options. When a product’s data gives its serving in grams only, the server also looks up the printed cup size by barcode in USDA FoodData Central; USDA sees only the barcode, not you. It keeps search results in memory briefly to speed things up and does not save which products you looked at. Google Cloud keeps standard request logs, including IP addresses, for up to 30 days. If Open Food Facts or the FDA can’t be reached from your phone, a lookup or recall check may go through this service instead.
U.S. FDA (openFDA) receives the barcode of US products, to check for recalls.
Google Firebase AI Logic receives the label photos you choose to analyse, resized on your phone, and passes them to Google’s Gemini model to read the label. Food.FM does not store them. Food.FM uses Google’s paid Gemini API service, so under Google’s terms your photos are not used to improve Google’s products. Google may keep them for a limited time only to detect misuse or meet legal requirements. Avoid including people or personal information in label photos.
Google Play handles payment if you subscribe to Food.FM Plus in the Android app; Food.FM never sees your card details. The app then sends Google Play’s purchase token to Food.FM’s server, which checks it with Google to confirm the subscription. Food.FM doesn’t keep a copy of the token or learn who you are.
Google Firebase App Check uses reCAPTCHA Enterprise to confirm requests come from the genuine Food.FM app, which involves sending device and browser signals to Google. The Google Privacy Policy and Terms of Service apply.
Google Firebase Remote Config downloads app settings, such as which AI model to use. It uses a random installation ID, not your identity.
Firebase Hosting serves the website and app. Like any web host, it handles standard request data such as IP addresses.
Google Fonts serves the typefaces on this website, and product photos load from Open Food Facts’ image servers.

Your profile is never sent anywhere: scores are personalised on your phone.

What we never do

Sell or share personal data.
Run advertising or ad tracking.
Accept payment to change a product’s score or appear in swaps.

Health information

Food.FM provides general nutrition information and is not a medical device. Because your health profile stays on your device and is never transmitted to us or anyone else, we do not hold health records about you.

Children

Food.FM is not directed at children under 13 and does not knowingly collect their information.

Contact

Questions about privacy: support@coework.com.

Last updated: October 2026.