Heyberry is an app for iPhone and Android that estimates the calories and nutrients in your food from a photo, a barcode or a recipe, keeps a daily food diary and builds a weight plan. This policy explains what personal data the app and our website getheyberry.com process, why, who helps us process it, how long we keep it and what you can do about it. It applies to everyone who uses Heyberry, including people testing it through TestFlight or a Google Play testing track. Where the iPhone and Android apps differ, the policy says so.
Summary
- Your food diary, meal photos and body measurements are health data. We process them only to provide Heyberry, and the current app asks for your explicit consent first (section 3 also covers earlier test versions).
- If you connect Apple Health on iPhone, the app reads your steps, active energy, workouts and weight on your phone to show them in the app. They are never sent to us, except a weight you choose to save as a weigh-in, and never used for advertising or marketing (section 2.7). The Android app doesn’t read health or fitness data from your phone.
- You create an account or sign in before setting up your plan. Your plan and food log are stored on our servers, linked to your user ID.
- Meal photos, notes and recipes are analyzed by Google’s Gemini AI model, a third-party AI. Our server sends them to Google directly and, if Google’s service does not answer, through OpenRouter, a service that passes the request on to Google. The app asks for your separate permission before the first analysis. We keep monitoring records in a service called Langfuse, photos included; deleting your account deletes them. OpenRouter keeps a copy of each request that went through it for at least 3 months; it deletes that copy when we ask.
- We don’t sell your data and we don’t show ads. To learn which parts of Heyberry work, the app and our server count how it is used with PostHog, an analytics service hosted in the European Union. These counts never include your meals, weights, plan, photos or notes, and you can turn them off in the app’s Profile tab (section 2.12). Advertising measurement in the app is optional and uses Google and Meta only after your separate agreement (section 2.16). Our website uses optional Google Analytics 4 cookies only after you agree to Analytics, and Meta Pixel cookies only after you separately agree to Advertising (section 2.11).
- Subscriptions are sold by Apple in the iPhone app, by Google in the Android app through Google Play, and by us on our website, where Stripe processes the payment. RevenueCat, a subscription service in the United States, keeps track of all of them for us: it receives your random user ID, your purchases and, if your account has one, your email address; never your meals, weights or photos. Neither we nor RevenueCat see your full card details (section 2.9).
- We email you a code when you sign in, and emails about your purchase if you buy Heyberry Pro on our website. Offers and news, by notification or by email, come only if you turn on Offers and news in the app, and every such email has an unsubscribe link (sections 2.8 and 2.13).
- You can delete your data in the app, in the Profile tab, or by emailing us.
- We apply the EU General Data Protection Regulation (GDPR) to all of our processing, wherever you live. Our servers and most of our service providers are in the United States.
1. Who we are
Heyberry (“we”, “us”) is the controller of your personal data: we decide why and how it is processed.
Email: support@getheyberry.com. We have not appointed a data protection officer.
You may notice two of our domains: getheyberry.com (this website, hello@getheyberry.com, the sender of our emails, and api.getheyberry.com, the server the app and this website talk to) and jjjlabs.com (cal-tracker-api.jjjlabs.com, the same server's address in older versions of the app).
2. What we collect and why
2.1 Your account
- A random user ID. The first time you open Heyberry, the app creates an anonymous account for you. You don’t need to give a name or an email address. Everything you log is stored on our servers under this ID.
- Your email address, if you save your progress or sign in with email. We send a 6-digit code to confirm it. There is no password.
- Your Apple sign-in, if you use Sign in with Apple on iPhone. We ask Apple only for your email address, which can be an Apple relay address if you choose Hide My Email. We don’t ask for your name.
- Your Google sign-in, if you use Sign in with Google on Android. Google confirms your Google Account’s email address, and the sign-in it sends also includes your name and the address of your profile picture. Our sign-in provider, Supabase, keeps them with your sign-in account. Heyberry uses only the email address.
- Moving guest data. If you sign into an account you already have, the app asks whether to bring what you logged as a guest into it. If you choose not to, we delete it from our servers at that moment, together with the guest ID, and the question tells you so. When you do bring it over, the empty guest ID is deleted too. If the question is left open for more than an hour, the guest data stays on our servers under the guest ID.
2.2 Your profile (health data)
To build your plan, the app asks for your goal (lose, maintain or gain weight), your sex (female or male, because the calorie formula needs it), your date of birth, height, weight, goal weight, how fast you want to reach it, your activity level and your preferred units. It also sends your phone’s time zone. It optionally asks where you heard about Heyberry.
We use these answers to calculate your daily targets for calories, protein, carbohydrates and fat and the date you could reach your goal. We calculate the targets whenever you open the app and don’t store them. The app also shows your BMI, calculated from your height and weight. Your starting weight and every weight you log later are stored as weigh-ins, one per day. If you have connected Apple Health, the weigh-in can start at today’s latest weight from Apple Health (for example from a smart scale); it is stored only when you save it, like a weight you type.
2.3 Your food diary (health data)
- Meals: what you log from a photo, a barcode, a recipe, the list of common foods or a quick calorie entry; when you ate; the foods, amounts and nutrient estimates; your answers to the app’s follow-up questions; your changes; dishes made of several parts; and meals you log again. Drafts you haven’t logged yet are stored too.
- Meal photos. Before uploading, the app shrinks each photo to at most 1024 pixels and saves it as a new JPEG file, which doesn’t carry the location or camera details of the original. We keep photos in a private cloud storage bucket, and the app shows them through links that expire after one hour.
- Notes you add to a photo, up to 500 characters (for example “2 tablespoons of olive oil”).
- Analysis records: for each AI analysis, the model and prompt version, the model’s answer, your note, and technical details such as timing and cost. We use them to show and correct estimates and to find errors.
- Saved recipes. When you import a recipe from a link or pasted text, we save its title, an English name for the dish, the number of servings, the ingredient lines with amounts and nutrient values, the link (without tracking parameters) and the address of the recipe’s picture. We don’t save the web page itself. We also save a numeric representation (an “embedding”) of the dish name, so we can suggest your recipe when you later photograph a similar dish.
2.4 Recipe search
When you search for recipes, we receive the words you type, your phone’s language and region setting, and the country of your IP address, which Google’s load balancer adds to the request. We send the words, the country and its language to our search providers (section 5) without your user ID. Identical searches are kept in our server’s memory for 60 seconds so we don’t pay for them twice. We don’t store your search words with your account, and your recent searches are saved only on your phone.
The current app sends the words in the body of the request, so they don’t appear in our server’s request logs. Earlier versions of the app send them in the request address, and our request logs keep that address for 30 days.
2.5 Barcodes, and pictures from other websites
- Barcodes. Our server looks up the barcode in Open Food Facts, a public food database. Open Food Facts receives only the barcode from our server, not who you are. We keep the product data in a cache shared by all users.
- Pictures and pages from other sites. Product pictures load on your phone directly from Open Food Facts, and recipe pictures load directly from the recipe websites. Recipe pages open in an in-app browser. These sites see your IP address, as with any website you visit, and their own privacy policies apply.
2.6 Technical data
- Requests to our server. They reach it through Cloudflare's network (api.getheyberry.com), which does not keep their content. Our cloud provider, Google Cloud, logs your IP address, your device and app version (the user agent), the time and the address requested, which can include a date, your time zone, a barcode or, from earlier versions of the app, search words. These request logs are kept for 30 days. Our own logs record errors and short technical notes, never your photos.
- Error diagnostics. Sentry receives technical error and crash reports: error codes, stack locations, app version and build, operating-system and device information, and random request identifiers. These reports help us distinguish app, connection and server failures. We exclude account identifiers, email addresses, session tokens, request bodies, meal descriptions, photos and health readings from our diagnostic payloads. We disable screenshots, screen recordings and session replay, and configure Sentry to remove IP addresses. Error events are kept for 30 days.
- Sign-in. The app talks directly to our sign-in provider, Supabase, which logs your IP address and device information for security.
- App updates. The app checks Expo’s servers for updates. These requests include your phone’s operating system, the app version, a random installation ID and your IP address.
We use this data to run Heyberry, keep it secure and fix problems.
2.7 Data stored on your phone
The app stores on your phone only what it needs to work: your sign-in session, your setup answers until you finish setup (then they are cleared), a copy of the app’s texts, your recent recipe searches, a few settings (for example whether we already asked you to save your progress), cached pictures, and a copy of your subscription status and of the offers, which RevenueCat’s code in the app keeps. Deleting the app removes them. The app uses no cookies. With your advertising measurement agreement, Google and Meta store app and device identifiers (section 2.16). Your choice and any withdrawal waiting for an internet connection are kept on your phone.
- Camera and photos. The app uses the camera only to photograph meals and scan barcodes. When you pick a photo from your library, the photo picker of iOS or Android gives the app only the photo you choose.
- Clipboard. To offer “Paste link” on iPhone, the app checks whether your clipboard holds a link without reading it. On iPhone and Android alike, it reads the clipboard only when you tap Paste.
- Apple Health (iPhone). If you connect Apple Health in the app, iOS asks whether Heyberry may read your steps, active energy, workouts and weight; you choose, and you can change it anytime in the Health app. The app reads them on your phone to show the calories you burn, your steps and the day’s workouts on Today (a workout’s type, time, duration, distance, calories and, for one recorded by a Garmin watch, the watch’s name) and to offer today’s weight when you log a weigh-in. None of it is ever added to your calorie budget. They are not sent to our server or to any of our service providers, and they are not included in our analytics. A weight reaches our server only when you save it as a weigh-in (section 2.2). Heyberry never writes to Apple Health, never uses Apple Health data for advertising or marketing, never sells it and never gives it to third parties. Devices such as Garmin watches reach Heyberry only through Apple Health, if you let their apps share with it.
- Android. The Android app doesn’t connect to Health Connect and doesn’t read any health or fitness data from your phone.
2.8 Emails from us and to us
- Sign-in codes. When you save your progress or sign in with email, we send you a 6-digit code.
- Your purchase on our website. If you buy Heyberry Pro on getheyberry.com, we send a welcome email with a one-time sign-in link, and a reminder before a free trial is charged.
- Notices about Heyberry. If your account has an email address, we may email you about Heyberry itself, such as an update to this policy or a change to the service.
- Offers and news. Only if you turn on Offers and news in the app (Profile tab, Notifications): one switch for offers and news by notification and by email (section 2.13). We keep when you turned it on and the words the switch showed. Every such email has an unsubscribe link; it, or the same switch, stops both at once. After an unsubscribe we keep a fingerprint of your email address (a one-way hash, not the address) so we don’t email it offers or news again, also after you delete your account.
- How we send them. Resend sends these emails for us (section 5). To write them in your language and to choose who an email is for, our server uses your account’s email address, read from your account when an email is queued, and what the app last told our server: its language, time zone and version, and your country. We keep a record of each email (which email it was, its language, when it was sent, whether it was delivered or why not) until you delete your account; the address itself leaves the record once the email is sent.
- Your emails to us. If you email support@getheyberry.com, we receive your email address and your message. Cloudflare forwards these emails to our mailbox, which is hosted by Google (Gmail).
2.9 Subscriptions and payments
Bought in the app. Heyberry Pro is an auto-renewing subscription. In the iPhone app Apple sells and bills it through In-App Purchase, and in the Android app Google sells and bills it through Google Play, so we never see your payment card details. Apple’s or Google’s privacy policy applies to the purchase itself, and you manage or cancel the subscription in your Apple Account settings or in Google Play (Payments & subscriptions).
To show you the right offer, know whether your subscription is active and let you restore it on another phone, the app and our server use RevenueCat, Inc. (RevenueCat), a subscription service:
- What RevenueCat receives: your random user ID (the same one as in Heyberry) and your purchases as the App Store or Google Play reports them: the product, its price and currency, when a trial or subscription starts, renews, is cancelled, refunded or ends, and the store’s transaction records. From the app it also receives the paywall screens you see, what you tap on them and whether you buy; the app’s version and the kind of build (the version from the App Store, TestFlight or Google Play, a review build or a development build); your phone’s model, operating system and its version, your language settings and store country; on iPhone, the identifier iOS gives each app maker for your phone (the identifier for vendors, not an advertising identifier) and whether you allowed apps to track you (iOS reports this to RevenueCat; Heyberry asks only after your separate advertising measurement agreement); and the IP address the app connects from. If your account has an email address (you signed in with email, Apple or Google, or bought Heyberry Pro on our website), the app’s subscription SDK gives RevenueCat that address, and RevenueCat Billing receives it at web checkout, so we can find your subscription when you write to us. We update it when your address changes, and it is deleted with your record at RevenueCat.
- When in the app: the app starts talking to RevenueCat only after your consent (section 3): when your plan is ready, or when you open the subscription in the Profile tab.
- What it never receives: your meals, weights, photos or notes, or your payment card details. The paywall can show your plan’s goal, but the app puts that text together on your phone and doesn’t send it.
- On our server we keep what we need to give you what you paid for: whether you have Heyberry Pro, whether it’s a trial, when it renews or ends, whether it will renew, the product and the store. RevenueCat tells our server about every change, and our server then asks RevenueCat for your current state. Purchases in a TestFlight version, and the test purchases Google Play allows for testers, are free; they reach RevenueCat and our server like real ones, and we keep them apart.
- In our usage analytics (section 2.12) we count trials, purchases, renewals, cancellations and refunds, without prices.
Bought on our website. On getheyberry.com we sell Heyberry Pro in countries supported by our payment providers through RevenueCat Billing:
- Checkout. RevenueCat opens checkout over our page. Your card or wallet details go to Stripe, our payment processor, which also processes payment data to prevent fraud under its privacy policy. RevenueCat receives your email address, your random user ID, your country and any billing address the payment method requires, the plan and price, trial and renewal dates, the payment result, and technical details such as your IP address and browser. It provides receipts and a link to manage or cancel the subscription. Your meals, weights, photos, notes and other health data never go to Stripe or RevenueCat.
- On our server we keep the subscription state described above. The website keeps your sign-in session in browser storage while checkout is open so the purchase belongs to the same Heyberry account you later open in the app. It signs out when you finish.
- Trial reminder. For a web trial we email you before it ends, around 36 hours ahead, during daytime in your profile’s time zone when available. The email states the charge date and links to subscription support; RevenueCat’s receipts provide your billing portal link. Resend sends our reminder from hello@getheyberry.com. We cancel the scheduled reminder when the trial changes, is cancelled or your account is deleted.
RevenueCat keeps this data while we use RevenueCat. When you delete your account (section 10), we delete your record at RevenueCat too, with your purchase history. That doesn’t cancel an Apple or Google Play subscription. Deleting the RevenueCat customer cancels a RevenueCat Billing web subscription. Apple, Google and Stripe keep their own payment records under their policies and applicable law.
2.10 Testing, and crash reports from the stores
If you test Heyberry through Apple’s TestFlight, Apple shares with us the crash reports and feedback you choose to send and, if we invited you by email, your name and email address. If you test it through a Google Play testing track, we have the email address we invited you with, and Google shares with us the feedback you choose to send through Google Play. Apple’s privacy policy applies to TestFlight and Google’s to Google Play. Everything else in this policy applies to testers in the same way.
Apple and Google can also give us crash and performance reports about the app from phones whose owners allow sharing diagnostics with app developers (iPhone) or with Google (Android). These reports describe the phone and the error, not who you are.
2.11 Our website
When you visit getheyberry.com, our hosting provider, Vercel, processes your IP address and browser details to deliver the pages and keep the site secure. Its fonts and pictures are served from the site itself; the links to the App Store and to Google Play take you to Apple and to Google. The sign-in session used for a web purchase stays in your browser only while you use checkout.
Cookies
We keep a strictly necessary first-party cookie, hb_consent, to remember your cookie choice for six months. Optional cookies and tags stay off until you choose a category. Reject all leaves them off. You can change your choice with Cookie settings at the bottom of the page. Withdrawing a choice reloads the page without those tags and removes their cookies on our domain.
- Analytics, with your agreement: Google Analytics counts site visits and completed web subscriptions or trial starts. It receives a browser identifier, the page path, product, currency, the paid price reported by the matching purchase receipt and a transaction identifier. A free trial has zero value; we do not use a plan's advertised future price as money paid today. Automatic form, search, scroll and outbound-click measurement and advertising personalization are off.
- Advertising, with your separate agreement: Meta Pixel counts page visits and completed web subscriptions or trial starts. It receives a browser identifier, technical browser and connection details, the product, receipt-reported paid price and currency, and a transaction identifier. Automatic event logging and advanced email/phone matching are off. Google's advertising consent signals remain denied without this choice; when permitted, Google may use the linked Analytics conversion to measure our ads. Google and Meta may process these identifiers under their privacy policy and privacy policy.
- What we keep out: the quiz pages never load these tags. We do not include your email, card details, meals, photos, weight, goals or onboarding answers in conversion payloads. A tag may observe the page and the browser connection that loads it.
- Global Privacy Control: an opt-out signal keeps advertising off, including after an earlier choice; only an explicit Advertising switch in Cookie settings can override it for this site. Do Not Sell or Share My Personal Information at the bottom of the page withdraws advertising without disabling checkout. Some US state laws describe advertising identifier sharing as selling or sharing personal information; we do not sell it for money.
Google's first-party _ga cookies normally last up to two years; Meta's _fbp and _fbc cookies normally last up to three months. Browser controls can shorten these periods. A completed checkout keeps a deduplication marker in this tab's session storage so refreshing its success view does not repeat the same conversion; it ends with the tab session.
2.12 Usage analytics
To see where people get stuck and which features they use, the app and our server send PostHog, Inc. (PostHog), an analytics service, short records of what happens in Heyberry: for example that the app was opened; that a setup step, the plan, the paywall or a sign-in screen was shown; that a paywall button or Log again was tapped; that a meal was analyzed or logged and how (from a photo, a description, a barcode, a recipe, the common foods or a quick calorie entry); whether an analysis worked, how long it took and how many foods it found; that a weigh-in was saved; that a meal became a favorite; that you agreed to the consent, with the versions you saw; that a trial or subscription started, renewed, was cancelled or refunded (the product and the store, never the price); and which answer you picked when setup asked where you heard about Heyberry.
Each record carries your random user ID, the time, the app’s version and update, your phone’s operating system and its version, and the kind of build that sent it (the version from the App Store, TestFlight or Google Play, a review build or a development build). When you sign into an account you already have, we tell PostHog that your guest ID and your account ID belong to the same person.
PostHog never receives your meals or their names, amounts or calories, your photos or notes, what you type or say, your weights, your goal or your other answers from setup (only where you heard about Heyberry), your email address or your location. PostHog’s session recording and automatic data collection are turned off, every record asks PostHog not to look up a location from the IP address it arrives from, and PostHog is set to discard IP addresses. Nothing is stored on your phone for analytics.
Your choice. Usage analytics is on unless you turn it off: in the app, open the Profile tab and switch off Share usage analytics under Privacy, or email us. The app and our server then stop sending these records right away. If you agreed to an earlier version of this policy, the app first tells you about this change on Today, and no record about you is sent to PostHog before that.
PostHog keeps these records for 1 year on our plan and then deletes them. When you delete your account, we also ask PostHog to delete your person record and its linked usage records. PostHog processes this request in the background, so those records may remain while it completes. You can also ask us to have them deleted sooner (section 9).
2.13 Notifications
If you allow notifications for Heyberry on your phone, the app registers your phone with our server so we can send you notifications:
- What we send: Reminders, for example a nudge to log a meal or to weigh in, and tips that keep your plan on track, are on unless you turn them off. Offers and news, for example a discount on Heyberry Pro, come only if you turn them on; the same switch covers our emails about offers and news (section 2.8). You also get a notification you asked for, such as a test. Notifications show on your lock screen, so they never include your meals, weights or other numbers about you.
- Your choice: both switches are in the app, in the Profile tab under Notifications. They belong to your account, so they are the same on all your phones. You can also turn off notifications for Heyberry in your phone’s settings. We send only what your phone allows.
- When: tips, reminders, offers and news arrive between 9 a.m. and 9 p.m. your time, at most one a day and three in a week.
- What our server keeps: your phone’s push token (the address that Expo, with Apple on iPhone or Google on Android, gives your phone for notifications), whether notifications are allowed, your account’s two choices (with when you turned Offers and news on and the words the switch showed), your phone’s language, country and time zone (to pick the words and the time), the app’s version, and the notifications we sent you, with when you opened them. We delete a phone’s token when you sign out on it, stop using it when Apple, Google or Expo report that it no longer works, and delete all of this with your account.
- Who delivers them: our server gives each notification, its title, text, the screen it opens and its ID, with your push token to Expo’s push service (650 Industries). Expo hands it, to deliver to your phone, to Apple Push Notification service on iPhone or to Google’s Firebase Cloud Messaging on Android.
2.14 What we don’t collect
We don’t collect your precise location, contacts or microphone input. Advertising identifiers are used only with your separate agreement (section 2.16). Apple Health data stays on your phone, except a weight you save as a weigh-in (section 2.7). Google and Meta may match advertising measurement data with data from other apps or websites after your agreement (section 2.16). Our usage analytics (section 2.12) never includes your health data.
2.15 Legal bases under the GDPR
| Purpose | Data | Legal basis |
|---|---|---|
| Create and run your account, sign you in, move guest data into your account | user ID, email address, Apple or Google sign-in | Performing our contract with you (art. 6(1)(b)) |
| Your plan, targets, weigh-ins and food diary, including the AI analysis of photos, notes and recipes | profile, weigh-ins, meals, photos, notes, recipes | Contract (art. 6(1)(b)) and, because this is health data, your explicit consent (art. 9(2)(a)) |
| Checking the quality of AI estimates and fixing errors (analysis records, monitoring records) | the data above and technical data | Our legitimate interest in an accurate, working service (art. 6(1)(f)); for health data, your explicit consent (art. 9(2)(a)) |
| Recipe search and barcode lookup | search words, country, language, barcode | Contract (art. 6(1)(b)) |
| Security, preventing abuse, server logs | IP address, device data, request logs, IDs sent to our AI provider | Legitimate interest in a secure service (art. 6(1)(f)) |
| Where you heard about Heyberry (optional question) | your answer | Legitimate interest in knowing which channels work (art. 6(1)(f)) |
| Usage analytics: which screens and features are used, where setup stops, how well analyses work (section 2.12) | user ID, the usage records in section 2.12, app version and build, operating system | Legitimate interest in improving Heyberry and knowing which channels work (art. 6(1)(f)); you can turn it off in the Profile tab (section 2.12) or object (section 9) |
| Selling and managing your subscription, restoring it on another phone (section 2.9) | user ID, email address (if your account has one), purchases, the app and phone data RevenueCat receives, your subscription state on our server | Performing our contract with you (art. 6(1)(b)) |
| Selling and managing a web subscription, receipts and trial reminders (section 2.9) | user ID, email address, country, billing address when required, plan, price, dates and payment result | Performing our contract with you (art. 6(1)(b)); keeping sales records required by law (art. 6(1)(c)); Stripe’s fraud prevention under its own policy |
| Optional advertising measurement (section 2.16) | identifiers and events described in section 2.16 | Your separate consent (art. 6(1)(a)), withdrawn in Profile |
| Knowing how subscriptions do: trials, purchases, renewals, cancellations and refunds (RevenueCat’s reports and our usage analytics) | user ID, purchases, paywall views and taps | Legitimate interest in running a paid app (art. 6(1)(f)) |
| App updates | installation ID, app version, IP address | Legitimate interest (art. 6(1)(f)) |
| Notifications (section 2.13): reminders and tips | push token, whether notifications are allowed, your choices, language, country and time zone, app version, the notifications sent and opened | Legitimate interest in helping you keep your diary (art. 6(1)(f)); you can turn them off at any time (section 2.13) |
| Offers and news, by notification and by email (sections 2.8 and 2.13) | the notification data above; for emails your email address, the app’s language, version and time zone, your country, the email’s content | Your consent (art. 6(1)(a)), given when you turn on Offers and news and withdrawn when you turn it off or unsubscribe |
| Sign-in codes, purchase emails and trial reminders (section 2.8) | email address, the email’s content | Performing our contract with you (art. 6(1)(b)) |
| Notices about Heyberry by email (section 2.8) | email address, the app’s language, the email’s content | Legitimate interest in telling you about the service you use (art. 6(1)(f)) |
| Keeping an unsubscribe in force (section 2.8) | a one-way hash of the email address | Legitimate interest in respecting your choice (art. 6(1)(f)) |
| Delivering this website | IP address, browser details | Legitimate interest (art. 6(1)(f)) |
| Feedback and crash reports from TestFlight, Google Play testing and the stores (section 2.10) | what you choose to send, name and email address if we invited you, the stores’ crash and performance reports | Legitimate interest in improving the app (art. 6(1)(f)) |
| Answering your emails | email address, message | Contract or legitimate interest (art. 6(1)(b) or (f)) |
| Establishing or defending legal claims | the data needed | Legitimate interest (art. 6(1)(f)); for health data, art. 9(2)(f) |
Giving us data is voluntary, but without your health data and your consent we can’t provide the plan or the food diary.
2.16 Optional advertising measurement
We advertise Heyberry on Google and Meta. A separate, optional choice before the paywall and in Profile under Privacy lets you agree to advertising measurement. Refusing does not affect your access or subscription. Health-data processing, usage analytics and Offers and news do not grant this permission.
- Data shared: Google Analytics for Firebase and the Meta SDK receive app and device identifiers, installation and app-activation events, app/device version, language and technical network information including IP address. RevenueCat receives matching Firebase app-instance and Meta anonymous IDs and, when allowed, your phone’s advertising identifier (on iPhone only if you also allow tracking; on Android, Google’s advertising ID). It forwards subscription lifecycle events, including trial start, purchase, renewal, cancellation and refund where supported, with product, store, transaction identifier, price and currency. A random account ID may accompany these events. We do not share your email address for advertising matching.
- Data excluded: meals, calories, weight, goals, health measurements, Apple Health data, photos, notes, recipe searches and what you type. Advertising SDK screen reporting and automatic Meta purchase logging are disabled. RevenueCat supplies subscription events.
- Choice: measurement is off before agreement. On iPhone, iOS then asks whether Heyberry may track you; refusing keeps advertising measurement off. Android asks no such question, so your agreement in the app is the only switch; Android’s settings also let you delete your phone’s advertising ID. Withdraw in Profile at any time or change tracking permission in iOS Settings. The app stops collection immediately. If offline, it keeps the withdrawal and sends it when connected; server-side forwarding stops when the withdrawal reaches our server. You can also contact support.
- Recipients: Google and Meta may match these identifiers and events with their own data from services, apps or websites to attribute and measure ads. They may process data in the United States. This choice does not enable Google ads personalization or health-data audiences. Their processing is described in Google’s privacy policy and Meta’s privacy policy.
- Retention: your agreement, purpose wording and withdrawal remain with your account as a record of your choice. Withdrawal stops future measurement and removes matching advertising identifiers from RevenueCat. It does not automatically erase events already received by Google or Meta. Contact us to request deletion of identifiable measurement records. Aggregated campaign reports may remain without identifying you.
Our legal basis for optional measurement, including storing or accessing identifiers on your phone, is your consent (GDPR art. 6(1)(a)). Withdrawal does not affect processing already performed before it.
3. Health data and your consent
We treat the following as health data: your height, weight and weigh-ins, goal weight and pace, activity level, the targets and BMI we calculate from them, and your food diary (meals, photos, notes, the recipes you log and their nutrition estimates). Your sex and date of birth are not health data on their own, but we protect them the same way because we use them together with your measurements.
Your explicit consent. Before the first question about your body, the app asks you to agree that we process your health data as described in this policy, including the AI analysis in section 4 and processing in the United States, and to confirm that you’re 18 or older. If you log meals without going through setup, the app asks the same question before your first meal. We record when you agreed and which version of this policy you saw. Your separate agreement to the AI analysis is asked and recorded apart (section 4).
Earlier test versions. Versions of the app released before 28 September 2026, which some TestFlight testers still use, didn’t ask for this consent. When your app updates, it asks before you log anything new. Until then, and at any time, you can have your data deleted (section 10).
Withdrawing consent. You can withdraw your consent at any time in the Profile tab: Withdraw consent and erase my data, or Delete account (Erase my data if you use Heyberry as a guest). Every feature of Heyberry uses health data, so withdrawing consent means we delete your data (section 10). Withdrawal doesn’t affect processing that took place before it.
Consumer health data
Some US state laws, such as Washington’s My Health My Data Act and a similar law in Nevada, give extra protection to consumer health data. For those laws, this section is our consumer health data privacy policy.
- What we collect: the health data listed above. It comes from you: what you enter, the photos and notes you send and the recipes you import, and the estimates our AI provider makes from them. If you connect Apple Health on iPhone, the app also reads your steps, active energy, workouts and weight on your phone; only a weight you save as a weigh-in reaches us.
- Why: only to provide Heyberry, as described in sections 2 to 4, and only with your consent.
- Who receives it: the service providers in section 5, which process it for us, and nobody else. We don’t sell it and we don’t use it for advertising.
- Your rights: you can access it, delete it, withdraw your consent and ask us which of our providers received it, in the app or by email (sections 9 and 10).
Not medical advice. Heyberry gives estimates for general wellness. It isn’t a medical device and doesn’t give medical advice.
4. AI processing of your photos, notes and recipes
Your permission. Before the first photo, typed meal or recipe is analyzed, the app asks you separately to agree to sending it to a third-party AI. It names Google’s Gemini, OpenRouter and Langfuse and says what is and is not sent. Without your agreement Heyberry does not send any meal to the AI; you can still add a meal by its calories. You can take your agreement back at any time in Profile (AI meal analysis). The words you agreed to are recorded with the date (ai-2026-10-30).
How a photo becomes an estimate:
- The app shrinks the photo and sends it, with your note, to our server.
- Our server stores the photo in our private storage bucket and sends the photo and your note to Google’s Gemini model (currently Gemini 3.8 Flash) through the Gemini API, on our own Google Cloud account. If that request fails, our server sends it through OpenRouter, which passes it to the same model at Google (Google AI Studio or Vertex AI).
- The model returns the foods it sees, estimated amounts, nutrient values, a title, the assumptions it made and, when something is unclear, questions for you. We store the result with your meal.
Recipes you import are read the same way: the text of the recipe page, or the text you pasted, goes to the model. To suggest your saved recipes for later photos, we also send English dish names, without your user ID, to Google’s Gemini embedding service.
- Identifiers. With each request that goes through OpenRouter we send it your random user ID and the meal’s ID; it uses them for abuse monitoring and its activity log. A request sent to Google directly carries no identifier of yours. We never send your weight, goals, plan or Apple Health data to the AI.
- No training. We tell OpenRouter to route our requests only to providers that don’t collect data for training, and Google’s terms for paid services say it doesn’t use such requests to improve its products. We don’t use your photos, notes or corrections to train AI models, and we won’t without asking for your separate consent. The direct route uses Google’s paid Gemini API under the same terms.
- Abuse monitoring. Google may keep copies of requests for a limited time to detect abuse: up to 55 days for the Gemini API, and up to 90 days for requests that Vertex AI’s safety systems flag.
- Where. Google may process requests in any of its data centers, because we haven’t limited the AI to one region. When a request goes through OpenRouter, OpenRouter processes it on servers in the United States.
- OpenRouter’s log. When a request goes through OpenRouter, it keeps a copy of the request and answer, including the photo, notes, recipe text and your user ID, for at least 3 months and possibly longer. OpenRouter offers no way for us to delete one user’s copies from our server, so deleting your account doesn’t delete them; email us and we ask OpenRouter to delete them.
- Monitoring records. To check the quality of estimates and fix errors, we record each AI action in Langfuse, a monitoring service: your user ID, the meal’s ID, your note, the photo, what we sent to the model and what it returned. For recipe searches we record the length of the search, your language setting and your country, not the words. When you delete your account we delete your records at Langfuse; Langfuse completes the deletion in the background, usually within 15 minutes. Otherwise they are kept until we delete them.
- Estimates can be wrong. You can change amounts, answer the app’s questions, add a note and run the analysis again, or delete the meal. The analysis doesn’t make decisions about you that have legal or similarly significant effects.
- Photograph food only. Photos can show more than food. Please keep people, documents and screens out of the picture. We don’t use photos to identify anyone.
5. Who processes your data
These providers process data for us, to run the parts of Heyberry listed next to them.
| Provider | What they do for us | Data involved | Where the data is |
|---|---|---|---|
| Supabase | Database and sign-in | all account, profile and diary data; email address; with Sign in with Google also your name and profile picture address; sign-in logs | Amazon Web Services us-east-1 (Virginia, USA) |
| Google Cloud | Servers (Cloud Run), photo storage (Cloud Storage), secrets, server logs | requests, photos, IP addresses in logs | us-east4 (Virginia) and us-east1 (South Carolina), USA; logs in Google Cloud’s global logging storage |
| Google (Gemini API and Vertex AI) | AI analysis, receiving the request directly from our server; dish-name embeddings | photos, notes, recipe text, dish names | Not limited to one region |
| OpenRouter, Inc. | Fallback route for AI requests when Google’s API does not answer; keeps a log of the requests it carries (section 4) | photos, notes, recipe text, user ID, meal ID | USA |
| Functional Software, Inc. (Sentry) | Technical errors and crashes | error codes, stack locations, request identifiers, app/build version and device/operating-system information; diagnostic payloads exclude account and health data | Sentry’s US cloud region, USA |
| Langfuse | Monitoring AI quality and errors. Deleted with your account. | user ID, meal ID, photos, notes, AI inputs and outputs, recipe links (without query), search country and language | Langfuse’s US cloud region, USA |
| TinyFish | Pictures and backup results for recipe search; reading recipe pages that block our server | search words, country and language; recipe links | Not stated by the provider |
| Treg (treg.to), which passes searches to Serper (serper.dev) | Google search results for recipe search | search words, country and language | Not stated by the providers |
| Resend | Sends our emails: sign-in codes, purchase emails and trial reminders, notices about Heyberry and, if you turned them on, offers and news | email address, the email’s content, its delivery status | Amazon Web Services us-east-1, USA |
| Cloudflare | Domain name service; forwards emails sent to getheyberry.com; carries the app's and this website's requests to our server at api.getheyberry.com, encrypted on both legs | emails you send us; the requests as they pass (what the app sends and our server answers), IP address and device details | Global network |
| Google (Gmail) | Our support mailbox | your emails to us | Google’s data centers |
| Vercel | Hosts this website | IP address and browser details of visitors | Global network |
| Expo (650 Industries) | Delivers app updates and notifications (section 2.13) | IP address, device platform, app version, installation ID; for notifications your push token and each notification’s title, text, the screen it opens and its ID | USA-based service |
| Apple Inc. (Apple Push Notification service) | Delivers notifications to your iPhone (section 2.13) | your push token and each notification’s title, text, the screen it opens and its ID | Apple’s servers |
| Google (Firebase Cloud Messaging) | Delivers notifications to your Android phone (section 2.13) | your push token and each notification’s title, text, the screen it opens and its ID | Google’s data centers |
| PostHog, Inc. | Usage analytics (section 2.12) | user ID, the usage records in section 2.12, app version and build, operating system | PostHog’s EU cloud, Frankfurt, Germany |
| Google (Google Analytics for Firebase) | Optional advertising measurement (section 2.16) | app-instance and device identifiers, install, activation and subscription events, app/device information and IP address; never health data | Google’s data centers, including the USA |
| Meta | Optional advertising measurement (section 2.16) | Meta anonymous and advertising identifiers, install, activation and subscription events, app/device information and IP address; never health data | Meta’s data centers, including the USA |
| Stripe | Processes web payments and prevents payment fraud under its own policy | card or wallet details, email address, billing details, IP address and payment records; never health data | Stripe’s global infrastructure and providers |
| RevenueCat, Inc. | Subscriptions bought through Apple, through Google Play and on our website (section 2.9): checks purchases, tells the app and our server whether Heyberry Pro is active, shows the paywall, runs web checkout, receipts and renewals | user ID, email address (if your account has one), purchases and the store’s transaction records, paywall views and taps, app version and build, phone model, operating system, language and store country, on iPhone the identifier for vendors and tracking permission status, IP address; for web purchases, billing country and address when required, plan, price, renewal dates and payment result | USA (Amazon Web Services and Google Cloud) |
Stripe also processes payment information for fraud prevention and legal obligations under its own policy. Companies that process data under their own policies, and not as our processors: Apple (App Store, TestFlight, Sign in with Apple, In-App Purchase, its crash reports); Google (Google Play, its billing and testing tracks, Sign in with Google, its crash reports); Open Food Facts (it receives barcodes from our server and serves product pictures to your phone); and the websites whose pictures or pages you open.
We don’t sell personal data or give it to data brokers. Optional advertising measurement shares only the identifiers and events in section 2.16, after your separate agreement. We disclose data to authorities only when the law requires it.
6. Transfers outside the EU
Most of our providers store or process data in the United States or don’t limit processing to one region, so your data is transferred outside the European Economic Area. Where a provider is certified under the EU-U.S. Data Privacy Framework, the transfer relies on it; otherwise we rely on the European Commission’s standard contractual clauses where the provider’s terms include them. Usage analytics records are stored in PostHog’s EU cloud. RevenueCat’s data processing terms include the standard contractual clauses, so the transfer of subscription data to RevenueCat relies on them. You can ask us which safeguard applies to a provider.
7. Security
- The app talks to our server and to Supabase only over encrypted HTTPS connections, and our server calls its AI and search providers over HTTPS.
- Our database (Supabase), our photo storage (Google Cloud Storage) and OpenRouter’s log are encrypted at rest by those providers.
- Photos are kept in a private bucket with public access blocked, and the app receives links to them that expire after one hour.
- Every request is checked against your sign-in, and our server returns only your own data.
- Server keys and passwords are kept in Google Secret Manager, not in the app.
- Recipe links you paste are checked before our server fetches them, so they can’t reach private networks.
- Your sign-in session is stored in the app’s storage on your phone, so keep your phone locked.
If a data breach puts your rights at risk, we will notify the competent data protection authority within 72 hours and tell you when the law requires it.
8. How long we keep data
| Data | How long |
|---|---|
| Web trial reminder schedule | Until the trial ends, is cancelled or your account is deleted; email delivery records as described below |
| Web invoices and required sales records | As long as applicable tax and accounting law requires, including after account deletion |
| Payment records at Stripe | Under Stripe’s own policy and applicable law |
| Account, profile, weigh-ins, food diary, photos, saved recipes, analysis records | Until you delete them or your account. We don’t delete inactive accounts automatically, including guest accounts. |
| A meal you delete | Deleted at once with its photo, items and analysis records. A deleted photo stays recoverable in our storage for 7 days, then it’s gone. |
| Guest data you choose not to bring into your account | Deleted when you choose, together with the guest ID (section 2.1). |
| Monitoring records (Langfuse) | Until you delete your account; we then delete them (usually within 15 minutes). Otherwise until we delete them. |
| OpenRouter’s log of AI requests | For requests that went through OpenRouter: at least 3 months, possibly longer. Not deleted with your account; OpenRouter deletes it when we ask. |
| Google’s abuse-monitoring copies of AI requests | Up to 55 days (Gemini API); up to 90 days for requests Vertex AI flags |
| Technical error and crash events (Sentry) | 30 days; not linked to your account |
| Server request logs (Google Cloud) | 30 days |
| Usage analytics (PostHog) | 1 year, or until PostHog processes our deletion request. Deleting your account asks PostHog to delete your person record and linked usage records; it completes this in the background. |
| Subscription data at RevenueCat | While we use RevenueCat, or until you delete your account; RevenueCat may keep backups for a limited time under its own practices |
| Your subscription state on our server | Until you delete your account; updated whenever RevenueCat reports a change |
| Push tokens | Until you sign out on that phone or delete your account; a token Apple, Google or Expo reports as no longer working is never used again |
| Your Reminders and Offers and news choices, and the record of turning offers on (when, the words shown) | Until you delete your account |
| Notifications we sent you | Until you delete your account |
| Record of the emails we sent you | Until you delete your account; the address itself only until the email is sent |
| Fingerprint (one-way hash) of an unsubscribed email address | Until you ask us to remove it, so your unsubscribe holds |
| Your app’s language, time zone, version and your country at its last start | Until you delete your account |
| Sign-in logs (Supabase) | Kept by Supabase for a short period under its own policies; on our plan we can see them for 1 day |
| Database backups (Supabase) | Supabase may keep daily backups of our database for up to 7 days |
| Our emails at Resend (its own record of each email) | 30 days |
| Website request data (Vercel) | Kept by Vercel for a short period under its own policies |
| Your emails to support | Until we delete them; ask us and we will |
| Recipe search memory on our server | 60 seconds |
| Data on your phone | Until you delete the app; setup answers until you finish setup |
9. Your rights
Under the GDPR you have the right to:
- access your data and get a copy of it;
- have it corrected;
- have it deleted;
- restrict how we use it;
- receive it in a portable format (we send you a JSON file, which today we prepare by hand);
- object to processing based on our legitimate interests;
- withdraw your consent at any time (section 3);
- complain to a data protection authority, in particular the one where you live or work or where you believe your rights were infringed.
US residents. Depending on your state, you may have the right to know about and access your data, correct it, delete it, get a portable copy, and opt out of its sale, targeted advertising and certain profiling; for consumer health data, also to withdraw consent and to learn which third parties receive it. Some of these laws apply only to businesses above a certain size; we honor these requests from everyone. We don’t sell personal data or profile you in ways that have legal or similarly significant effects. You can refuse or withdraw optional advertising measurement in Profile under Privacy (section 2.16), or contact us about your rights. You can use an authorized agent; we’ll confirm the request with you. We won’t treat you differently for using your rights. If we decline a request, you can appeal by replying to our answer, and if you disagree with the outcome of the appeal, you can contact your state attorney general.
How to use your rights. In the app you can view and edit your meals and delete meals, your data or your account. For anything else, email support@getheyberry.com. We answer within one month under the GDPR, or 45 days under US state laws, and tell you if we need more time where the law allows it. We may ask you to confirm a request from the email address of your account. If you use Heyberry as a guest, we can’t tell from an email alone which data is yours, so please use the options in the app; if your version of the app doesn’t have them yet, email us and we’ll help you find your data.
10. Deleting your account
- In the app: the Profile tab → Delete account, or Erase my data if you use Heyberry as a guest. Withdraw consent and erase my data, under Privacy, does the same. Earlier test versions of the app don’t have these buttons; they come with the next update, or you can email us instead.
- Deleted at once: your meals with their photos, items and analysis records, your saved recipes, weigh-ins and profile, your subscription state on our server and your record at RevenueCat with your purchase history (RevenueCat completes that deletion shortly after), your phones’ push tokens and the notifications we sent you, your monitoring records at Langfuse (the deletion is completed there in the background), and your sign-in account (email address, Apple or Google sign-in).
- Usage analytics: we ask PostHog to delete your person record and its linked usage records (section 2.12). PostHog processes this request in the background, so those records may remain while it completes.
- Not deleted by it: OpenRouter’s log of requests that went through it (section 4), which you can ask us to have deleted; Google’s abuse-monitoring copies, server and sign-in logs and backups, which expire on their own (section 8); deleted photos, which stay recoverable in our storage for 7 days; and your emails to support (ask us to delete them).
- Subscriptions: deleting your account won’t cancel an Apple or Google Play subscription. Cancel it in your Apple Account settings or in Google Play. For a RevenueCat Billing subscription bought on our website, deletion of your RevenueCat customer cancels the subscription. Apple, Google and Stripe retain their own payment records, and required web invoices and sales records remain for as long as applicable law requires. Uninstalling the app does not cancel either kind of subscription.
- Sign in with Apple: deleting your account doesn’t remove Heyberry from the apps that use your Apple Account. You can do that in your Apple Account settings, under Sign in with Apple.
- Sign in with Google: deleting your account doesn’t remove Heyberry from your Google Account’s connections either. You can do that in your Google Account, under Security, Your connections to third-party apps & services.
- Uninstalling the app doesn’t delete your data on our servers, and signing out doesn’t delete anything.
You can also ask us by email to delete your data.
11. Children
Heyberry is for adults. The current version of the app asks you to confirm that you’re 18 or older before you give it health data, and its setup accepts only ages 18 to 100. We don’t knowingly collect personal data from anyone under 18. If you believe a child has given us personal data, contact us and we will delete it.
12. Changes to this policy
We will publish any new version on this page with a new date. If a change affects how we use your health data or adds a new kind of recipient, we will tell you in the app before the change applies and ask for your consent again where it’s needed.
13. Contact
Email: support@getheyberry.com