The “Ate / Did Not Eat” Feature: How to Maintain Data Accuracy and Exclude Food That You Did Not Consume

The “Ate / Did Not Eat” feature allows users to manage their food logging within the app themselves. This is particularly useful in situations where the goal of interacting with the assistant is not to record an actual meal but to evaluate a product, analyze the composition of a dish, or decide whether to consume it.

For example, you may be in a store considering several products. You want to understand which one is healthier by comparing their calorie content, sugar levels, fat content, and other nutrients. Or you take a photo of a dish in a restaurant to determine whether it fits your dietary plan, but ultimately decide not to order it. It’s also possible that you started eating but did not finish your meal—either by choice or due to circumstances.

In such cases, it is not reasonable to count the food in your diary—since it was not fully consumed or entirely not eaten. To maintain analytical accuracy and avoid skewed reports, you can utilize the “Ate / Did Not Eat” feature.

How It Works:

After you send a photo of the dish to the assistant in the chat and receive its breakdown (calories, macronutrients, vitamins, recommendations), you will be prompted to confirm whether this dish was actually eaten. You will see two buttons—“Ate” and “Did Not Eat.” If you select the second option, the dish will not appear in reports, will not impact calorie calculations, and will not be considered in personalized recommendations.

This way, you gain the ability not only to maintain an accurate food diary but also to use the app as a tool for evaluating, comparing, and analyzing products without needing to factor them into your diet.

This solution is especially relevant for users seeking a mindful approach to nutrition, testing new products, or practicing flexible eating strategies. The “Ate / Did Not Eat” feature helps ensure high reliability of your data and maintain control over what was truly part of your diet and what was not.

Read more