Privacy policy

Re.Food is a food diary: you log what you eat, track calories and activity, and share plates with other people. This policy explains what the app collects to do that, who it is shared with, and what you can ask us to do about it.

Re.Food is operated by the Re.Food team. The controller of your personal data — the one responsible for it under data protection law — is Andrii Zelenchuk. For anything in this policy, write to support@re-food.app.

What we collect

Account details

Your email address and a password (stored only as a hash), or your Google or Apple account if you sign in with one. If you sign in with Apple and choose to hide your email address, we only ever see the address Apple creates for Re.Food, which forwards our emails to you. Your handle, display name, profile picture and bio.

Health and body information

Your gender, date of birth, height, weight, activity level, goal and target rate of change. We use these to calculate your calorie and macro targets — that is the whole purpose of the app, and the app cannot work without them — and those targets also help order the Foods wall for you (see below). Under UK and EU data protection law this is special category data, and we process it only with your explicit consent: before you answer any question about yourself, the app shows you what it collects, why and who handles it, on a screen of its own, and asks you to agree. We record when you did. Because the app is built on this data, you can’t use it without agreeing; you can withdraw your consent at any time by deleting your account. If you are in the United States, our Consumer Health Data Privacy Policy also covers this information and what you log.

What you log

Meals and their nutrition, water, activities, weight history and any custom trackers you create, each with the date and time you recorded it.

Photos and videos

Meal photos, short videos of your meals, and your profile picture. Photos and videos you attach to a post are visible to other people using Re.Food, and to anyone holding the post’s link.

A video keeps the sound it was recorded with, so it can include your voice or anything else that could be heard while it was filmed. Before a video is uploaded, the app compresses it on your device, and makes a still frame from it that is shown wherever the video can’t play — for example when the post is sent in a message.

Camera and microphone

The camera is used only when you scan a barcode, photograph a meal or record a video for a post. The microphone is used only while you record a video for a post, to record its sound. Re.Food never listens otherwise.

What you post and send

Posts, recipes, comments, ratings, likes, saves, who you follow and who you block, and direct messages. Direct messages are not end-to-end encrypted: they are stored on our servers so they can be delivered to the other person.

The Foods wall is ordered for you. It favours posts from people you follow, posts with the tags and cooks you like and save, and posts that fit your calorie and macro targets; posts you have already seen wait until you have caught up with the rest. We work this out on our servers, only from what you do in Re.Food.

Reports you make about other people — about a post, a comment, a review, a profile or a chat, with the reason you pick and anything you write — are seen only by our moderators, and never shown to whoever you reported. When you report a comment or a review, we keep a copy of what it said, so our moderators can still read it if it is deleted. When you report a chat, our moderators can read that conversation — what both of you wrote in it — to look into it. If someone reports one of your posts, our moderators review it and may hide it; you will see why on the post. If someone reports a comment or review of yours, our moderators may delete the comment, or take the writing off the review. If they suspend your account, we record why and for how long; while it lasts you can’t sign in, and what you have posted is hidden from everyone, but nothing is deleted. If one of your posts is taken down because of a copyright notice and you send us a counter-notice, we pass it on, with your name and contact details, to whoever sent the notice, as US copyright law requires (see our terms).

Location

Only when you ask to attach a place to a post. Your device’s coordinates are sent to our server, which queries Google Places for nearby venues and returns the list. We do not track your location in the background, and we store only the venue you choose — never your raw coordinates.

A phone can also save where a photo was taken or a video was filmed inside the file itself. We remove that as a photo or video is uploaded, so none of what you post carries it.

Device and technical information

A push notification token so we can notify you, stored with your device’s language and time zone so that notifications and emails are written in your language and give dates as they fall where you are; your device’s advertising identifier for advertising (see below); and diagnostic data when the app misbehaves — including, on a small sample of sessions, a recording of the screens you interacted with, used to reproduce crashes.

Purchases

If you subscribe to Re.Food Premium or buy AI scans, the purchase is made and paid for in Google Play or the App Store, never in our app — we never see your card or payment details. We receive from them, through RevenueCat, what you bought, when, and when a subscription renews or ends, linked to your account so we can unlock it. We also count the AI meal scans you use. We email you about your purchases at your account’s email address: when a subscription starts, renews, has a payment problem, is cancelled or ends, when you buy scans, and when a purchase is refunded.

How you use the app

Which screens you open and for how long, the actions you take (for example logging a meal, publishing a post or sending a message) and the errors you run into, together with your app version, device model and operating system. These records hold identifiers, counts and durations — never what you wrote in a post, a message or a search. They are linked to your account, so that when something goes wrong for you we can see the steps that led there, and we use them to find problems and improve the app.

Advertising

Re.Food shows ads from Google AdMob between posts on the Food screen. Ads are marked Sponsored.

To choose which ad to show, Google may use your device’s advertising identifier. We also send Google the tags of the posts around the ad and the addresses of those posts, so that the ad is more likely to be about food — except in the United States without your permission (see below). We do not send Google your name, your email, your health or body information, or anything you have logged.

If you are in the United States, you are asked separately, when you first open the Food screen, whether Google may use your device’s advertising identifier and the food posts around each ad to personalize and measure ads — in a food and nutrition app, that can say something about your health. If you don’t allow it, the ads you see are not personalized, Google is asked to apply restricted data processing, and the request carries no tags or addresses of the posts you are reading. The feed is shown either way. You can change your answer at any time in Profile → Settings → Ad sharing.

If you are in the European Economic Area or the UK, you will be asked when you first open the Food screen, and you can refuse. The Food feed is paid for by its advertising, so if you refuse, the feed is not shown; everything else in the app — logging meals, tracking, your profile and your messages — works exactly as before. Re.Food Premium subscribers see no ads, are not asked, and always see the feed. You can change your answer at any time, from the Food screen or in Profile → Settings → Ad privacy options. Google’s own list of ad partners and how they use data is at business.safety.google. You can also reset or delete your advertising identifier in your device settings.

On an iPhone, the advertising identifier is only used if you allow it when iOS asks whether Re.Food may track you. If you don’t, you still see ads, but they aren’t chosen using it. You can change your answer at any time in Settings → Privacy & Security → Tracking.

Who we share it with

We do not sell your data. We share it only with the services that make the app work:

• Google AdMob — advertising, as described above.
• Google Sign-In — if you choose to sign in with Google.
• Sign in with Apple — if you choose to sign in with Apple.
• Google Play, the App Store and RevenueCat — taking payment for subscriptions and scan packs, and telling us what you bought. RevenueCat knows your purchases by your Re.Food account id only.
• Google Places — venue search, when you attach a place to a post.
• Microsoft Azure — hosting, photo and video storage, and an AI vision model that reads a meal photo to suggest what is on the plate. Photos you send to that feature are processed to return a suggestion and are not used to train the model.
• Open Food Facts — looking up a packaged product by barcode or name.
• Sentry — crash and error diagnostics.
• Expo, Firebase Cloud Messaging and the Apple Push Notification service — delivering push notifications.
• Our email provider — confirming your email address when you sign up, password resets, account email, and emails about your subscription and purchases.

Some of these providers are outside your country, so your data may be transferred internationally and protected by the safeguards those providers offer, such as the EU Standard Contractual Clauses.

Why we are allowed to process it

• To provide the app — performing the contract you enter when you create an account.
• Purchases — performing the contract you enter when you buy a subscription or scans.
• Your health and body information — your explicit consent, given on its own screen before onboarding.
• Personalized advertising — your consent, asked for separately and withdrawable. In the United States that includes sharing with Google for advertising at all, beyond non-personalized ads.
• Keeping the app working and secure — our legitimate interest in diagnosing faults, preventing abuse and moderating what is posted.

How long we keep it

We keep your account and what you have logged for as long as your account exists. When you delete your account, your profile, logs, posts, photos, videos, messages, the reports you made and the reports made about you are deleted from our systems; backups are overwritten on their normal cycle. If you signed in with Apple, we also tell Apple to end Re.Food’s access to your Apple ID. A report is kept after our moderators have decided on it, as the record of that decision, until the post it is about is deleted, or the account that made it or that it is about. Diagnostic data is kept for a limited period by Sentry and then deleted. Records of how you use the app are deleted after 90 days, or with your account if that comes first. So is our record of the emails we send you — which email it was, when, and whether our mail server took it, never what it said.

Your rights

You can ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, and to withdraw a consent you have given. If you are in the UK or EEA you can also complain to your data protection authority. If you are in Washington, Nevada or Connecticut, the Consumer Health Data Privacy Policy sets out the rights those states give you over your health data, and how to appeal if we turn a request down.

You can delete your account and everything in it from the app at any time, in Profile → Settings, or by email without the app — see deleting your account for what is removed and what is kept. For anything else, write to support@re-food.app and we will respond within one month.

Children

Re.Food is for adults only: because the app handles weight and calorie goals, you must be 18 or older to use it, and it asks for your date of birth when you set it up. We do not knowingly collect data from anyone under 18. If you believe someone under 18 has given us data, write to us and we will delete it.

Changes

If we change this policy we will update the date at the top, and tell you in the app if the change is a significant one.