Privacy Policy
EZZY · Last updated 15 October 2026
EZZY (“the app”) is a nutrition tracker for iPhone. This policy explains what the app collects, why, and who processes it. We do not sell your data. The app shows no ads. We advertise the app itself on Facebook and Instagram, and to see whether those ads work, the app includes Meta’s software development kit, which tells Meta when the app is installed and opened and when an account or a free trial is started. It does not access your device’s advertising identifier, and the app never asks for permission to track you. See Advertising measurement below. We also record which of the setup screens you reached, on our own servers, to find where the setup flow fails.
What we collect
| Data | Why |
|---|---|
| Your email address, and the Apple or Google account identifier you signed in with | To create and authenticate your account. If you use Sign in with Apple with “Hide My Email”, we only ever see the private relay address, never your real one. |
| Your name | Only when Apple or Google supplies it as you first sign in, which they do once. Used to address you in the app. |
| Profile: age, height, weight, sex, activity level, goal and target weight | To calculate your daily calorie and macronutrient targets. |
| Food entries: names, ingredients, portion weights, calories, macronutrients, fibre, sugar, sodium, meal type and timestamps | To build your diary, daily totals and streaks. |
| Meal photos and photos you attach in chat | To identify food and estimate nutrition. Held in a private storage bucket and readable only through signed links that expire after one hour. |
| Spoken meal descriptions | Your speech is turned into text by iOS speech recognition. The recording never reaches our servers — we receive only the text, which you can edit before saving. |
| Messages to and from the in-app assistant, including any photo you attach | To answer your questions and keep the day’s conversation on screen. |
| Water and weight entries, and the days counted towards your streak | To display trends alongside your nutrition. |
| App language and time zone | To show the app in your language and to close your day at your own local midnight. |
| A push notification token for each device you sign in on | To send the daily reminder. See Push notifications below. |
| App installs and opens, and the moment you create an account or start a free trial without a card, together with a random identifier Meta’s software creates for this installation of the app, and basic device details (model, iOS and app version, language, time zone) | To measure whether our ads on Facebook and Instagram lead to installs and sign-ups. Sent to Meta; see Advertising measurement below. |
| Subscription events: App Store trial start, purchase, trial conversion and renewal, with product, price and currency, together with Meta’s random installation identifier | To measure whether our ads lead to paying users. Sent to Meta by RevenueCat; see Advertising measurement below. |
| Trial and subscription status | To give you access to paid features. We never see your card details. |
| Setup progress: which of the setup screens you reached, when you reached it, and which sign-in button you tapped — Apple or Google | To find where the setup flow fails, so we can fix it. These notes are kept on your iPhone as you go and sent to us once you have signed in, so they end up attached to your account. They stay on our own servers and are never shared with anyone else. See Retention and deletion below. |
Artificial intelligence
Food recognition, nutrition estimates and assistant replies are produced by OpenAI models, called from our servers. What is sent depends on what you do:
- A meal photo you scan, or a photo you attach in chat, is sent as image data.
- A meal description you type, or that iOS produced from your dictation, is sent as text.
- Your messages to the assistant are sent as text, along with the most recent messages from that day’s conversation.
- Each assistant reply also carries your profile as context — age, height, weight, sex, activity level and goal — together with your daily targets and the day’s running totals. While answering, the assistant can also fetch your diary entries, favourites, water and weight entries.
Your name, your email address and your account identifier are never sent. Every calorie and macronutrient figure the app shows you is calculated on our servers, not by the model. Under OpenAI’s API terms, content sent this way is not used to train their models.
Not medical advice
EZZY is a general nutrition and wellbeing tracker, not a medical device. Its calorie and macronutrient targets are estimates, produced from the details you enter using standard population formulas, and the in-app assistant can be wrong. Nothing in the app is medical advice, diagnosis or treatment. Speak to a doctor or a registered dietitian before making significant changes to how you eat — particularly if you are pregnant or breastfeeding, under 18, or living with a condition such as diabetes or an eating disorder.
Push notifications
If you allow notifications, iOS issues a push token for your device. We store it against your account so we can send a daily reminder to log your food; if you sign in on more than one device, we hold one token per device. Preparing that reminder uses your time zone, your language, whether you have already logged a meal that day, and your current streak, which the reminder may mention. Notifications are handed to Expo, which passes them to Apple’s push service for delivery to your iPhone.
You can switch reminders off in the app under Profile, or switch notifications off entirely in iOS Settings. Some prompts — the one shortly before a free trial ends, for instance — are scheduled by the app on your own device and involve no server at all. Deleting your account deletes the tokens we hold.
Advertising measurement
We promote EZZY with ads on Facebook and Instagram. To learn which ads lead to people installing and using the app, the app includes Meta’s software development kit (Meta Platforms Ireland Ltd. and Meta Platforms, Inc.).
What Meta receives: that the app was installed and opened; that an account was created; that a free trial was started without a card; a random identifier Meta’s software generates for this installation of the app; basic technical details of the device and app, such as model, iOS version, app version, language and time zone; and, as with any connection over the internet, your IP address. If the software itself crashes, Meta receives a report of that crash.
What Meta does not receive: your name, email address or account identifier, your profile, weight, food entries, photos, chat messages or anything from Apple Health. Apart from the subscription events described below, we do not send purchase details to Meta.
No tracking permission, no advertising identifier. The app never asks for permission to track you, and Meta’s software is configured not to collect your device’s advertising identifier (IDFA). Install measurement relies on Apple’s privacy-preserving attribution (SKAdNetwork), which reports ad results to Meta in aggregate. Meta uses what it receives to report on and improve the delivery of our ads, under its own terms and its Privacy Policy.
Subscription events. We store Meta’s random installation identifier with RevenueCat, our subscription provider. When you start a free trial through the App Store, buy a subscription, or a subscription converts from trial or renews, RevenueCat sends Meta that event with the product, its price and currency, and that random identifier, so we can see which ads lead to paying users. RevenueCat does not send your name, email address or EZZY account identifier.
Apple Health
If you grant permission, the app reads workouts, active energy and step count from Apple Health so it can show what you have burned and keep your calorie budget accurate. All of that happens on your iPhone: no value read from Apple Health is ever sent to our servers, to OpenAI, or to anyone else. Those three are the only types the app asks to read.
The app also asks for permission to write to Apple Health, and uses it to save the workouts you record in the app. You can change or withdraw any of this at any time in iOS Settings › Privacy & Security › Health. Health data is never used for advertising and is never shared with third parties for their own purposes.
Who processes your data
We use a small number of providers, each handling only what its function requires:
- Supabase — authentication, database and photo storage. The project is hosted in the EU (Ireland).
- OpenAI — food recognition, nutrition estimation and assistant replies, as described above.
- Expo — delivery of our push notifications. Expo receives your device push token and the text of the notification.
- Apple — the App Store processes all payments and tells us only whether your subscription is active, which product it is, and when it renews or expires; Apple’s push service delivers notifications to your iPhone; and iOS speech recognition converts your dictation to text, which on many devices and languages means the audio is processed by Apple rather than on the phone itself.
- Google — only if you choose Sign in with Google, in which case Google confirms your identity to us and passes on your email address and, where you have set one, your name.
- RevenueCat — subscription and entitlement management. It receives your account identifier and Apple’s purchase records for your subscription, and, for advertising measurement, the random installation identifier created by Meta’s software.
- Meta — measurement of our Facebook and Instagram ads: app installs and opens, account creation, trial starts and subscription events, as described under Advertising measurement.
- Amazon Web Services — hosting for the servers behind the app, and storage of their operational logs.
Retention and deletion
We keep your data for as long as your account exists, with one exception: the setup-progress records described above are deleted automatically 180 days after they are made, whether or not your account is still open. You can delete your account at any time in the app, under Profile. Deletion is immediate and permanent: it removes your sign-in, your profile, your diary entries and their photos, your chat history and chat photos, your water and weight entries, your streaks, your setup-progress records, your notification settings and your stored push tokens, and we ask RevenueCat to delete your subscriber record. It cannot be undone — signing in again creates a new, empty account.
Four things deletion does not do:
- It does not cancel your subscription. Apple handles billing, not us, so cancel it yourself in App Store › Subscriptions, otherwise it keeps renewing.
- It does not reach our servers’ operational logs, which are held apart from the database for security and troubleshooting and expire on our hosting provider’s own schedule.
- It does not remove the anonymous statistics we keep about closed accounts: the sign-up method, the app language, the region of your time zone, whether a trial or a paid subscription ever existed, how many diary entries, assistant messages, weight entries and active days there were, and coarse bands for age, sex, activity level and goal. That record holds no account identifier, no email address, no name, no free text and no exact age, height or weight, and cannot be linked back to you or to anyone else.
- It does not delete what Meta has already received for advertising measurement. Meta never receives your EZZY account identifier, so we have no way to point Meta at your records; Meta holds them under its own retention rules, and you can manage your information with Meta through its own settings.
Your rights
Depending on where you live, you may have the right to access, correct, export or delete your personal data, to object to or restrict processing, to withdraw consent, and to complain to your local data protection authority. In-app deletion covers the most common request. Your profile, targets, diary entries, water and weight entries can all be changed or removed in the app. For anything else, contact us and we will respond within one month.
Children
The app is intended for people aged 13 and over. We do not knowingly collect data from children under 13. If you believe a child has created an account, contact us and we will delete it.
Security
Traffic between the app and our servers is encrypted with HTTPS. Photos live in a private storage bucket that is not publicly listable and is reachable only through signed links that expire after an hour. Every database table denies direct access outright: the app reaches your data only through our API, which checks each request against your signed-in session and returns only rows belonging to you.
The lock-screen, home-screen and Apple Watch displays keep a copy of the day’s calorie totals in a shared container on your own devices, so they can draw themselves without opening the app. That copy stays on your devices.
Changes
If we make material changes to this policy we will update the date at the top of this page and, where required, notify you in the app.
Contact
Questions or requests: [email protected]