Privacy policy

Fabee is an AI nutrition coach for iPhone that you use by chatting. It is made by Nicolas Demanez, trading as NICODMZ Company in Belgium (“we”). This page explains what data Fabee uses, where it goes, and what you can do about it.

Consumer health data: see our Consumer Health Data Privacy Policy.

The short version

If you turn on sync, your food log, photos, weight, profile and recent chat are saved to your Fabee account on our servers in the EU, so a new iPhone gets them back. If sync is off, they stay on your iPhone only.
To write a reply, the message you send, and the meal photo if you add one, goes through our server to an AI model. We only use AI providers based in the US or the EU that keep nothing and don’t train on your messages and photos.
If you connect Apple Health, Fabee only reads it, and your readings stay on your iPhone: never in analytics, and not on our servers, except the daily activity summary (active energy and workouts) while you share with a personal coach. While “Coach reads my Health” is on, Fabee’s AI coach reads a short daily summary through the AI model, which keeps nothing. Weigh-ins you choose to bring in, the setup answers it fills in, what the AI coach remembers in words and its replies in your chat are saved like the rest of your data.
If you join a personal coach with their link, they see what the coaching page lists, from that day on, never your chats.
We keep a small anonymous account, your feedback if you send any, and usage numbers that you can turn off.
No ads. We don’t sell your data or track you across other apps and websites.

What stays on your iPhone

Everything you log lives on your iPhone: meals, foods and amounts, meal photos, your calorie and macro targets, and what you tell Fabee about yourself (such as goal, sex, age, height, weight and activity). Your recent chat is kept on your iPhone too.

Sync is off until you turn it on. If you leave it off, nothing you log leaves your iPhone except what the chat needs to answer you (see below), and deleting the app deletes your data.

When you add a meal photo to a message, it is sent once, with that message, to be read by the AI model (see below). Neither our server nor the AI model keeps that copy. If sync is on, the photo is also saved to your account, like your other synced data.

Apple Health

Connecting Apple Health is optional. Fabee works the same without it.

What Fabee reads. Only what you allow in Apple’s Health permission sheet:

Body: weight, body fat percentage, height, date of birth and sex.
Activity: steps and workouts.
Sleep: your sleep analysis.
Glucose: blood glucose readings, for example from a CGM that shares with Apple Health.
Period days: the days you log in Health. This is a separate question, offered only to women. Fabee never predicts periods or fertile days.

Fabee doesn’t read heart rate, heart rate variability, blood pressure, medications or any other type. It reads up to 400 days back, when you open the app and while it’s open, never in the background.

Read-only. Fabee never writes anything to Apple Health.

It stays on your iPhone. What Fabee reads from Apple Health, and anything it works out from it (such as a meal’s glucose rise or your average sleep), stays on your iPhone. These readings are never put in iCloud and never used for usage analytics. They are not stored on our servers either, except the daily activity summary (active energy and workouts) while you share with a personal coach (see Sharing with your own coach). Analytics only record whether Apple Health is connected (yes or no) and the setup steps you went through, never a value. The exceptions are under “What does get saved” below.

Fabee’s AI coach and the AI model. In this section, “the coach” is Fabee’s AI coach, never a personal coach. When you connect, Fabee tells you that its AI coach reads a short daily summary of this data through the AI model the chat uses: for example how you slept, your steps and workouts so far, your latest weight, a period day and your glucose rise after a meal. When you ask about a longer period, the coach can also look up the day-by-day details it needs, and averages the app works out. These go with your messages to the AI model, the same way as the rest of the context a reply needs, only while “Coach reads my Health” is on, and the AI model keeps nothing. Connecting is your consent to this, and Fabee records the date and the version of the wording you agreed to, on your iPhone. You can withdraw it at any time with “Coach reads my Health” in Settings, under Apple Health: the coach then never sees your Health data, and Trends still shows it.

If you tell the coach about a low glucose reading, it records only that a safety case happened (its category), never your words or the reading, like its other safety flags. Safety flags record a category only and aren’t linked to you in analytics. A serious one also opens a private issue for us to look at, with the category, the time and a short one-way code instead of your account ID.

What does get saved. Four things become normal Fabee data:

Weigh-ins you bring in. The first time Health has a new weigh-in, Fabee asks whether to bring your scale’s weigh-ins in. If you say yes, each new one (with the body fat percentage measured the same day) is added to your weight entries, like a weight you type. If sync is on, it syncs like any weight entry. You can change this with “Weigh-ins from Health” in Settings.
Setup answers. If Health fills in your sex, age, height and weight during setup, and the activity level it suggested, they become your profile answers, the same as if you typed them.
What the coach remembers. The coach may remember a habit in words, for example the days you train, never a reading. Like the rest of what Fabee remembers about you, it is saved to your account only if you turned on sync.
The coach’s replies. What the coach writes is part of your chat, even when it mentions your sleep or your steps. Like the rest of your chat, it is saved to your account only if you turned on sync.

Your control. Apple’s Health settings decide what Fabee may read: in the Health app, or in your iPhone’s Settings, under Privacy & Security, then Health. “Choose what Fabee reads” in Fabee’s Settings opens them. We never use Apple Health data for ads or marketing, and never sell it.

What sync saves on our servers

Sync is optional. Fabee asks during setup, or in a short message after an update. If you say “Not now”, it asks once more a week later. You can change your answer in Settings, under Sync.

If you turn it on, we save a copy of this to your Fabee account:

Your meals: the foods, amounts, calories, protein, carbs and fat.
Your meal photos.
Your weight entries.
Your profile: first name, age, sex, height, weight, activity, goal and targets.
Your saved foods.
What Fabee remembers about you, such as allergies, food preferences, your goals, symptoms like reflux, and injuries, conditions or medications you tell it about.
Your check-in answers, such as energy, sleep and hunger.
Food estimates Fabee has learned from you.
Your chat from the last 3 days.

Only while you share with a personal coach, we also save your body photos and measurements, and a daily summary of your activity from Apple Health (active energy and workouts).

Why: so your data is safe if you lose or change your iPhone, and so it is the same on each device signed in to your account. We don’t use it for anything else. We don’t read it, sell it, use it for ads, or train AI on it.

This data is about your health, so we only save it with your consent: the “Turn on sync” tap. We record the date and time you said yes.

Where it is: the records are in a Neon database in Frankfurt, Germany, and the photos in Cloudflare R2 storage held in the EU.

Your account has no email, name or password. It is a random ID. Its sign-in key is kept in your iCloud Keychain, so your other Apple devices can use the same account. Anyone who can open your iCloud Keychain can reach your Fabee data, so keep your Apple Account secure.

If you join a personal coach with their link, they can see your meals, photos, weight, body photos and measurements, daily activity summary and profile, from the day you agree. They never see your chats with Fabee. Read Sharing with your own coach for the full list and how to stop.

What we receive

An anonymous account. On first launch Fabee creates an account on our server so the app can talk to it. It has a random ID and no name, email or password. When the app signs in, we store a session token with the IP address and device type it came from. If you answer the sync question, we also keep your answer and when you gave it.

Your chat messages and meal photos. Each message you send, with the context a reply needs (for example the meals you logged today and your targets) and a meal photo if you added one, goes from our server to OpenRouter, which passes it to the AI provider. The model’s reply comes back the same way. Our server passes messages and photos through and does not store them (only sync saves your recent chat, if you turn it on). We choose the AI models ourselves, and we only use AI providers based in the US or the EU, with zero data retention: they don’t keep your messages or photos, and don’t train on them.

Food names. When Fabee logs a food, it sends the food’s name and its nutrition values to a shared food table on our server, so the same food gets the same numbers for everyone. For each time a food is seen, the table also keeps the day (not the time) and a one-way code made from your account ID with a secret key that only our server has. It can’t be turned back into your account ID without that key. We use it only to count how many different people agree on a portion size, for example how much “a slice” weighs. The table never holds your messages, and nothing else in it is linked to you.

Feedback you send. If you use Feedback in the app, we store your message, its type (bug, request or general), the app version and build, your device model and iOS version, linked to your account ID. Each report also opens an issue in our private GitHub repository, with the same details and a short one-way code instead of your account ID.

Usage analytics. Fabee counts how the app is used so we can make it better: for example app opens, meals logged, whether a meal was typed or came with a photo, how far people get through setup, and which screens they use. These events are linked to your anonymous account ID, never to your name, messages, photos or food log, and are stored by PostHog in the EU. When you finish setup, we also add a few broad details to that anonymous profile: your goal, activity level, sex and an age range (for example 25 to 34), your units, language and region, so we can see how Fabee works for different people. Never your first name, exact age, height or weight. No Apple Health value is used for analytics: if Health filled in your sex or age, or suggested your activity level, those are left out. Safety flags record a category only and aren’t linked to you in analytics. If you installed Fabee from an Apple Search Ads ad, Apple tells the app which campaign, ad group, keyword and ad it was (ID numbers only, not when you saw or tapped it), and we add those to the same anonymous profile and to RevenueCat. Our server also counts AI usage (number of requests, speed, errors and cost), again without any message content. Usage analytics are on by default, and you can turn them off in Settings.

Subscriptions. Apple handles payment through the App Store. We never see your card. We use RevenueCat to check your subscription, and we keep its status (plan, renewal date, trial) with your account ID. We also record subscription events (a trial starting or ending, a purchase, a renewal, a cancellation, a billing issue) with your anonymous account ID, to run and measure subscriptions. RevenueCat sends these to PostHog directly, so the analytics setting in the app doesn’t turn them off. They never include your name, email, messages or food log.

This website. heyfabee.app uses PostHog, hosted in the EU, in cookieless mode: no cookies, and PostHog stores nothing on your device. It counts page views and clicks on the waitlist, TestFlight and App Store buttons, with the site or campaign that sent you (for example a utm_source tag). The site keeps that source in your browser for the current tab only. Our calculators can also be shown inside other websites; there, PostHog counts the view the same way, without cookies, along with the address of the page showing it. If you join the waitlist, we keep your email address only to tell you when you can try Fabee. You can unsubscribe from any email we send.

Who helps us run Fabee

Cloudflare runs our server and this website, and stores synced meal photos in the EU (R2). It handles: requests to our server, with short-lived technical logs, and your synced photos.
Neon hosts our databases, all in Frankfurt (Germany): synced data, and accounts, sessions, your sync answer, feedback and the shared food table. It handles: your synced records, accounts and sessions.
OpenRouter connects our server to the AI model. It handles: your chat messages, meal photos and the context a reply needs.
The AI provider (chosen by us, only providers based in the US or the EU with zero data retention) writes the reply. It handles: your chat messages, meal photos and the context a reply needs (with your Apple Health summary if you allow it), without keeping them or training on them.
GitHub tracks feedback and serious safety flags as issues. It handles: feedback text, app and device details, and a safety flag’s category and time with a one-way code instead of your account ID.
Apple runs App Store payments and TestFlight. It handles: your purchases, under Apple’s own policy.
RevenueCat checks your subscription. It handles: purchase receipts and subscription status, and the Apple Search Ads campaign IDs if an ad brought you.
Resend keeps the waitlist and sends its emails. It handles: your email address.
PostHog (EU) runs the app’s usage analytics and error reports, and this website’s analytics. It handles: app usage events and error reports (no messages, meals or photos) linked to your anonymous account ID, AI usage counts, subscription events from RevenueCat, and page views and button clicks on heyfabee.app without cookies.

Each of these handles data under its own terms and privacy policy. Our databases and synced photos are stored in the EU. Some services listed above may process data in the United States (for example AI providers based in the US, Apple, GitHub and RevenueCat), and our server runs on Cloudflare’s network, which may handle a request in the data center closest to you. So your data may be processed outside your country.

What we don’t do

No ads, in the app or around it.
We don’t sell or rent your data.
We don’t use your data to track you across other companies’ apps or websites.
We don’t train AI models on your data.
We don’t use Apple Health data for ads or marketing, and we don’t keep it in iCloud or on our servers, except the daily activity summary (active energy and workouts) while you share with a personal coach.

How long we keep it

Sessions expire 400 days after you last used the app. Each time you use it, the clock restarts.
Your account is kept until you delete it.
Synced data is kept until you delete it. When you delete something in the app, we keep a small “deleted” marker for 180 days, so your other devices also delete it. Then the marker is erased.
Synced chat is deleted from our servers 4 days after it was last written.
Body photos, measurements and activity summaries are saved only while you share with a personal coach, and are deleted when coaching ends.
If you turn sync off, we stop saving new data, and the copy already on our servers stays in your account so you can get it back later. To erase it, use “Delete everywhere” (below).
Feedback is kept as long as we need it to fix or answer it, and is deleted with your account.
Raw usage events are kept for up to 12 months. After that we keep only totals that can’t be linked to anyone, unless the law requires us to keep them longer (for example to answer a legal claim or a request from an authority).
The shared food table is kept. Its one-way codes can’t identify you without our server’s secret key.
Waitlist emails are deleted once you unsubscribe, or when the waitlist closes.

Deleting your data

In the app: Settings, then “Delete my data”. You get two choices:
- Delete everywhere deletes everything on your iPhone and your Fabee account on our servers, with your synced records, your photos, your sync answer, your sessions and your feedback. If you’re offline, Fabee deletes the iPhone copy now and sends the account deletion the next time it opens with a connection.
- Delete from this iPhone only deletes everything on your iPhone, turns sync off, and keeps the copy in your account. Turning sync on later brings it back.
Stopping sharing with a personal coach (Settings, then Your coach, then “Stop sharing”) deletes your body photos, measurements and activity summaries from our servers.

Your Apple subscription stays with Apple: cancel it in your Apple Account settings.
On your iPhone: deleting the app also removes everything stored on the phone. It doesn’t delete your account or its synced copy.
By email: write to [email protected], or send a request through Feedback in the app so we can find your account. We delete your account and everything linked to it within 30 days.

Your rights

Depending on where you live (for example in the EU, the UK or California), you can see, correct, delete or get a copy of your data, object to how we use it, and withdraw your consent. Most of this works in the app:

Get a copy: Settings, then “Download my data”. Fabee builds a zip file on your iPhone, with your data in a JSON file and your meal photos, that you can open without the app.
Correct it: edit or delete any meal, weight, saved food or profile detail in the app. With sync on, the change reaches your account too.
Delete it: Settings, then “Delete my data” (see above).
Withdraw your consent to Fabee’s AI coach reading Apple Health: Settings, then Apple Health, then “Coach reads my Health” off. To stop Fabee reading Health at all, change it in Apple’s Health settings.
Withdraw your consent to sync: Settings, then Sync, then off. From then on, nothing new is saved to our servers. To also erase what is already saved, use “Delete my data”, then “Delete everywhere”.

For anything else, email us and we’ll answer within 30 days. You can also complain to your data protection authority. In Belgium, where we are based, that is the Autorité de protection des données / Gegevensbeschermingsautoriteit (dataprotectionauthority.be).

Children

Fabee is not meant for children under 16, and we don’t knowingly collect data from them.

Changes

If this policy changes, we’ll update this page and the date at the top. For big changes, we’ll also tell you in the app.

Contact

Questions about privacy: [email protected].