Dzmitry Barysevich built the EatFit app as a Freemium app. This SERVICE is provided by Dzmitry Barysevich at no cost and is intended for use as is. This page is used to inform visitors regarding the policies on collection, use, and disclosure of Personal Information when using the Service. By choosing to use the Service, you agree to the collection and use of information in relation to this policy. Personal Information collected is used for providing and improving the Service. Information will not be used or shared with anyone except as described in this Privacy Policy. The terms used in this Privacy Policy have the same meanings as in the Terms and Conditions, which is accessible at EatFit unless otherwise defined in this Privacy Policy.
The app can be used without an account. In that case the food diary, weight history, profile (age, sex, height, weight, activity level and goal) and settings are stored only on the device, unless the user has a subscription.
If the user signs in with email, Google or Apple, this data and the email address of the account are also stored in the user's EatFit account on Google Firebase, so that they are backed up and available on the user's other devices. For a subscriber who has not signed in, this data is stored in the same way under an anonymous account. The account and its data can be deleted at any time, as described on the account and data deletion page.
When food is recognized from a photo, the photo and the optional description are uploaded to Google Firebase and sent to OpenAI to recognize the food and estimate its nutritional value. See Photos.
The app uses third party services that may collect information used to identify you:
The user can add a photo to a meal or a recipe by taking it or choosing it from the gallery. A photo used for food recognition is also added to the meal automatically.
Before a photo is added, a smaller copy of it is sent through Google Firebase to OpenAI to check that it does not show sexual, violent or dangerous content. This applies to every photo and every user, with or without an account. EatFit does not store the copy; only the result of the check is recorded in the service logs. A photo that does not pass the check, or cannot be checked, is not added.
The photo is stored on the device. For signed-in users and subscribers it is also uploaded to their EatFit account on Google Firebase, so that it is backed up and available on their other devices. Photos added before signing in are uploaded after the user signs in. Before saving, the app scales the photo down and re-encodes it, which removes metadata such as the location where it was taken.
A meal photo is available only to its owner. When the user shares a recipe, its photo is shared along with it, and anyone who receives the recipe in EatFit can see the photo. The user can also send a meal photo to other apps; it then goes only where the user chooses.
Removing a photo deletes it from the device and from Firebase, unless it is still used in another meal or recipe. When the account is deleted, its meal and recipe photos are deleted from Firebase. Deleted files can remain recoverable in Firebase for up to 7 days.
A photo uploaded for food recognition is kept separately and is deleted from Firebase automatically after 2 days. A selection of these photos may be kept longer and used to test and improve food recognition, including with other AI models.
Whenever the Service is used, in a case of an error in the app, data and information (through third party products) on your phone called Log Data may be collected. This Log Data may include information such as your device Internet Protocol (“IP”) address, device name, operating system version, the configuration of the app when utilizing the Service, the time and date of your use of the Service, and other statistics.
Cookies are files with a small amount of data that are commonly used as anonymous unique identifiers. These are sent to your browser from the websites that you visit and are stored on your device's internal memory. This Service does not use these “cookies” explicitly. However, the app may use third party code and libraries that use “cookies” to collect information and improve their services. You have the option to either accept or refuse these cookies and know when a cookie is being sent to your device. If you choose to refuse our cookies, you may not be able to use some portions of this Service.
Third-party companies and individuals may be employed for the following reasons:
Third parties may have access to Personal Information in order to perform their assigned tasks. However, they are obligated not to disclose or use the information for any other purpose.
Personal Information is handled with care and commercially acceptable means are used to protect it. However, no method of transmission over the internet, or method of electronic storage is 100% secure and reliable, and absolute security cannot be guaranteed.
This Service may contain links to other sites. If you click on a third-party link, you will be directed to that site. Note that these external sites are not operated by EatFit. Therefore, reviewing the Privacy Policy of these websites is strongly advised. EatFit has no control over and assumes no responsibility for the content, privacy policies, or practices of any third-party sites or services.
These Services do not address anyone under the age of 13. The app does not knowingly collect personally identifiable information from children under 13. In the case it is discovered that a child under 13 has provided personal information, it is immediately deleted from the servers. If you are a parent or guardian and your child has provided personal information, please contact EatFit so that necessary actions can be taken.
The Privacy Policy may be updated from time to time. Reviewing this page periodically for any changes is advised. Changes will be communicated by posting the new Privacy Policy on this page. This policy is effective as of 2026-11-01
The app may collect and process health-related data, including but not limited to nutritional information (such as calories, macronutrients, and micronutrients), dietary intake, and physical activity.
This data may be provided directly by the user, collected via features such as barcode scanning or AI-based food recognition, or, if enabled by the user, accessed from health platforms such as Health Connect or Apple Health, as described in the next section.
This data is used solely to provide and improve app functionality, including tracking nutrition, analyzing dietary habits, and delivering personalized insights.
Health data is not sold, rented, or shared with third parties for marketing or advertising purposes.
Health data is stored securely and is only accessible to the user. Appropriate measures are taken to protect this data from unauthorized access, disclosure, or misuse.
Users can request deletion of their data at any time.
On Android, EatFit can exchange data with Health Connect. On iOS, it can read data from Apple Health. Each connection stays off until the user turns it on in the app and grants access on the system permission screen. Access can be withdrawn at any time in the Health Connect or Apple Health settings.
Data EatFit reads
Data EatFit writes (Health Connect only)
Data received from Health Connect and Apple Health is used only to provide these features. It is not used for advertising, is not sold, is not shared with third parties, is not sent to analytics or crash reporting services, and is not used to determine creditworthiness or for lending purposes.
The use of information received from Health Connect adheres to the Health Connect Permissions policy, including the Limited Use requirements.
For any questions or suggestions about this Privacy Policy, please contact: eatfitcaloriecounter@gmail.com.