Consumer Health Data Privacy Policy

Re.Food is a food diary: you log what you eat, track calories and activity, and share plates with other people. Much of what it holds says something about your health, and Washington’s My Health My Data Act, Nevada’s consumer health data law (SB 370) and Connecticut’s Data Privacy Act each give you rights over that kind of data. This policy covers what those laws call consumer health data. Everything else Re.Food does with your data is in our privacy policy, which this sits alongside.

It applies to anyone in Washington, Nevada or Connecticut, and to anyone whose data is collected in Washington. We apply it to everyone who uses Re.Food in the United States.

Re.Food is operated by the Re.Food team. The person responsible for your consumer health data is Andrii Zelenchuk. For anything in this policy, write to support@re-food.app.

Your consent comes first

Before Re.Food keeps anything about your body, the app shows you what it collects, why and who handles it, and asks you to agree, on a screen of its own. Nothing about your health is saved until you do, and we record when you agreed. Re.Food can’t work without this data, so you can’t use the app without agreeing.

Sharing is a separate question, asked separately: see Who receives it.

What we collect, and why

• Your gender, date of birth, height, weight, activity level, goal and target rate of change — to calculate your daily calorie and nutrition targets.
• The calorie and nutrition targets calculated from them — to show your progress against them, and to put the posts that fit them higher on your Food feed.
• What you log — meals and their nutrition, water, activity and steps, weight history, and any custom trackers you create, each with when you logged it — to keep your diary, show your progress, and send the weekly recap and reminders you have turned on.
• Meal photos you scan with AI — to suggest what is on the plate and its nutrition. An AI model reads the photo to return a suggestion, and isn’t trained on it.
• Posts you publish about a meal — its photos or video, and its nutrition — to show them to other people on Re.Food, which is what publishing does.

We don’t use your health data for anything else, and we don’t infer health conditions from it. Nor do we use photos, videos or the sound in them to recognize anyone’s face or voice.

Where it comes from

• From you — what you enter when you set up the app, and what you log, photograph, film and post afterwards.
• Worked out by us — your calorie and nutrition targets, and your progress against them, calculated from what you entered.

We don’t collect health data about you from anyone else, and we don’t read it from your phone’s sensors or health apps.

Who receives it

We never sell your health data, and we don’t give it to data brokers.

Companies that work for us

These handle it only on our behalf, under contracts that limit them to doing so:

• Microsoft Azure — hosts the app’s servers, database, photos and videos, and runs the AI model that reads meal photos.
• Sentry — crash and error reports, which can include details of the screen in use when something went wrong.
• Expo, Firebase Cloud Messaging and the Apple Push Notification service — deliver notifications, which can mention what you have logged (for example the weekly recap).

Google, for advertising — only if you allow it

The Food feed carries ads from Google AdMob. In a food and nutrition app, even an ad request can say something about your health: Google can see your device’s advertising identifier beside the food posts you are reading. So if you are in the US, the app asks you separately, the first time you open the Food screen, whether to allow it.

• If you allow it, Google receives your device’s advertising identifier together with the tags and links of the posts around each ad, and may use them to choose and measure ads for you. Google can also collect information over time and across other apps that use its advertising, under its own privacy policy.
• If you don’t, you still see ads, but they are not personalized, Google is asked to apply restricted data processing (using the request only to serve and measure that ad), and the request carries nothing about the posts you are reading.

Either way, Google never receives your body measurements, goals or logs. You can change your answer at any time in Profile → Settings → Ad sharing.

Other people on Re.Food

What you publish — a post’s photos or video (with the sound it was filmed with, unless you turn that off), its meal and nutrition, comments and ratings — is seen by other people on Re.Food, and by anyone you send its link to. Nothing in your diary is published unless you post it.

When the law requires it

We may disclose health data when the law requires us to, for example to answer a valid court order. We have no affiliates that receive it.

Your rights

You can ask us:

• To confirm whether we collect, share or sell your health data, and for a copy of it — together with a list of every third party and affiliate we have shared it with, and how to contact them.
• To delete it. You can also do that yourself at any time: Profile → Settings → Delete account removes your account and everything in it (see deleting your account). We delete it from our systems, backups as they are next overwritten, and ask the companies that hold it for us to delete it too. If you allowed sharing for advertising, what Google holds is tied to your advertising identifier, which you can reset or delete in your device settings.
• To withdraw your consent. To withdraw your consent to sharing, change your answer in Profile → Settings → Ad sharing. Since Re.Food can’t work without your health data, withdrawing your consent to its collection means deleting your account.
• To correct it. Most of it you can edit yourself in the app.

Write to support@re-food.app from your account’s email address, so we know the request is yours. We answer within 45 days. If we need longer — up to another 45 days — we’ll tell you why within the first 45. Requests are free, up to twice a year.

Appealing a decision

If we turn down a request, you can appeal: reply to our answer, or write to support@re-food.app with “Appeal” in the subject. We’ll tell you in writing within 45 days what we did and why. If we still say no, you can complain to your state’s attorney general — in Washington, Nevada or Connecticut.

Location

Re.Food doesn’t track where you are. Your location is used only when you ask to attach a place to a post, and then only to find nearby venues. We never use it to tell whether you are at, or near, a place where health care is given.

Changes

If we change this policy we will update the date at the top. If a change affects what you agreed to — what we collect, why, or who receives it — the app asks you to agree again before it applies.