Privacy Policy
Last updated: September 18, 2026
This policy explains what data Fio collects, what it uses it for, and what you can do about it. It is written to be understood, not to hide anything.
1. Who is responsible for your data
Fio ("we") is the controller of the data we collect through the mobile app and this website.
For any privacy question you can write to hola@fio.app.
2. What data we collect
Account data: name, email address and your hashed password, or the identifier Apple or Google gives us if you sign in with them.
Physical profile data: age, sex, height, weight, activity level and goal. We use them to calculate your calories and macros.
Nutrition data: the meals you log, the foods and ingredients, the amounts, and the photos you upload to the scanner.
Training data: routines, exercises, sets, reps, weight lifted, session duration and history.
Third-party health data: if you allow it, steps and activity from Apple Health. We only read what you permit and you can revoke it from your phone's settings.
Technical data: device model, operating system, app version, language and crash reports.
We do not collect precise location and we do not access your contacts.
3. What we use your data for
To make the app work: saving your meals and routines, computing your calorie balance and syncing across your devices.
To analyze the photos you upload to the scanner and identify the foods in them.
To keep your account secure and prevent abuse.
To improve the app using aggregated statistics that do not identify you.
To reply when you write to support.
We do not use your health or nutrition data for advertising, and we do not sell it.
4. Legal basis
We process your data to perform the contract you accept when creating an account (providing the service), for legitimate interest (security and product improvement), and with your consent where health data or Apple Health access is involved.
You can withdraw your consent at any time; that does not affect processing carried out before.
5. Scanner photos
When you scan a plate, the photo is sent to our servers to be analyzed and to estimate the foods and their calories.
For that analysis we use artificial intelligence models from Google (Gemini) and OpenAI, companies based in the United States. The photo, and whatever meal data is needed to identify the foods, is sent to their servers solely to obtain that result.
The photo stays attached to that meal in your history so you can review it. It is deleted when you delete the meal.
We do not use your photos to identify you, nor to train models shared with third parties without your permission.
6. Who we share it with
Infrastructure providers hosting the database and files, under contract and only to provide the service.
Google (Gemini) and OpenAI, in the United States, which analyze meal scanner photos to identify the foods and estimate their calories.
Crash reporting and usage analytics services, with aggregated or pseudonymized data.
Authorities, when a law or court order requires it.
We never sell your data or hand it to advertisers.
7. International transfers
Some providers are outside your country. When that happens we rely on standard contractual clauses or other recognized mechanisms to protect your data.
Specifically, meal scanner photos are processed in the United States, on Google (Gemini) and OpenAI servers.
8. How long we keep it
For as long as your account is active.
If you delete your account, we erase your personal data within 30 days, except what the law requires us to keep.
Crash logs are kept for a maximum of 90 days.
9. Your rights
You can access your data, correct it, delete it, restrict its processing, object to it and request a portable copy.
The fastest way is from the app, under Profile → Settings. You can also write to hola@fio.app.
If you think we haven't handled it properly, you can complain to the data protection authority in your country.
10. Minors
Fio is not directed at children under 16. If we find an account belonging to a minor without parental authorization, we delete it.
11. Security
We encrypt traffic in transit, store passwords using secure key derivation functions and limit internal access to data.
No system is infallible: if a breach affected you, we would tell you.
12. Changes to this policy
If we change something relevant, we update the date above and notify you inside the app before it takes effect.