Skip to content

Privacy policy

Last updated: September 26, 2026

Fabee is a calorie counter 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

  • Your food log, photos, targets and body details stay on your iPhone, and in your own iCloud if sync is on. We can’t see them.
  • To write a reply, the message you send, and the meal photo if you add one, goes through our server to an AI model that keeps nothing. We don’t store your messages or photos.
  • 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 only.

When iCloud sync is on, a copy of this data is kept in your own iCloud account, in Apple’s private CloudKit database. It is tied to your Apple ID, and we have no access to it. Apple’s privacy policy covers iCloud.

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 we nor the AI model keep it.

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.

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 company that runs the AI model. The model’s reply comes back the same way. Our server passes messages and photos through and does not store them. We only use AI hosts that agree to zero data retention: they don’t store 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. That table holds food names and nutrition values only. Nothing 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. 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.

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. 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. It handles: requests to our server, with short-lived technical logs.
  • Neon hosts our database, in the United States. It handles: accounts, sessions, feedback, the shared food table.
  • OpenRouter connects our server to the AI model. It handles: your chat messages, meal photos and the context a reply needs.
  • The AI model provider (chosen by OpenRouter, only among hosts with zero data retention) writes the reply. It handles: your chat messages, meal photos and the context a reply needs, without keeping them.
  • GitHub tracks feedback as issues. It handles: feedback text, app and device details.
  • Apple runs iCloud sync, App Store payments and TestFlight. It handles: your iCloud data and purchases, under Apple’s own policy.
  • RevenueCat checks your subscription. It handles: purchase receipts and subscription status.
  • Resend keeps the waitlist and sends its emails. It handles: your email address.
  • PostHog (EU) runs the app’s usage analytics and this website’s analytics. It handles: app usage events 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 server and database are in the United States, 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.

How long we keep it

  • Sessions expire 90 days after you last used the app.
  • Your account is kept until you ask us to delete it.
  • 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.
  • The shared food table has no personal data and is kept.
  • Waitlist emails are deleted once you unsubscribe, or when the waitlist closes.

Deleting your data

  • On your iPhone: delete the app. That removes everything stored on the phone.
  • In iCloud: open Settings, tap your name, then iCloud, then Manage Storage, and delete Fabee’s data.
  • On our server: email [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 ask to see the data we hold about you, correct it, delete it, get a copy, or object to how we use it. Email us and we’ll answer within 30 days. You can also complain to your local data protection authority.

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].