Privacy policy
Nomzo used to be called Ballpark. It's the same app from the same company, and nothing about how it handles your data changed with the name.
Nomzo is a photo-first calorie app. This policy explains what data the app handles, where it goes, and what never leaves your phone. It is short because the app is simple: there are no accounts and no ads, and we do not sell data.
The short version
- Your food log (photos, notes, meals, calorie numbers) lives in a database on your phone. We do not have a copy.
- What you tell us during setup (your weight, goal weight, height, birth year, sex and goals) stays on your phone. It isn't sent to our server, our analytics or the AI providers.
- When you ask for an estimate, the photo and your note are sent to an AI provider to produce it. We never store them. The provider holds the request briefly to check for abuse of their service, then deletes it.
- We collect anonymous usage statistics (which screens get used, not what you eat). You can turn this off in Settings.
- Deleting the app deletes your data.
What stays on your phone
Everything you log: meal photos, dish names, notes, calorie estimates, your daily target, your history and streak. Everything you answer during setup, too (see the next section). All of it is stored locally on your device. There is no account and no cloud copy of ours, so we cannot see it, restore it, or hand it to anyone.
Your phone's own backup (iCloud or Google) can include the app's data, under your account with them. We can't see it.
What you tell us during setup
When you first open Nomzo, it asks a few questions to work out a rough daily calorie target and a rough date for your goal: your sex, birth year, height, weight, goal weight, how fast you'd like to go, how often you work out, what's got in the way before, and when you usually have dinner. You can change most of these answers, and your daily target, in Your plan whenever you like. The daily target can also be changed in Settings.
- These answers are stored only in the app's database on your phone and used only there, to calculate your target and the date.
- They are never sent to our server, never included in an estimate request, never sent to the AI providers, never sent to our analytics and never attached to your purchase record at RevenueCat.
- We don't keep a history of your weight and don't draw a chart of it. There's one current weight and one goal weight, and changing them overwrites the old ones.
- Delete the app and they're gone, along with the rest of your log.
Two setup answers are counted anonymously in our analytics, as a choice from a fixed list and nothing else: where you heard about Nomzo (if you answer), and whether you'd tried a food diary before. See "Anonymous usage statistics".
What is sent when you ask for an estimate
To produce an estimate, the app sends your meal photo (if you took one) and your note (if you wrote or spoke one) to our server, which passes them to an AI provider, currently OpenAI or Google, to identify the food and guess the calories. To make the reply feel less robotic, the request also includes a little context: the local time and weekday, the names of your last few logged dishes, your streak length, and your rough total for the day.
- The photo and note are used only to produce the estimate. Our server does not store them and does not write them to logs.
- Our server logs one technical line per request: an anonymous device ID, which AI model answered, token counts, response time, the confidence level, and whether a photo was included. Never the photo, the note, or what the food was.
- The AI providers process the request to return the estimate. We use paid API access, where providers state they do not use the data to train their models. They do keep the request for a short period to detect abuse of their service, up to 30 days in OpenAI's case, and then delete it. Their own privacy terms apply to that processing (OpenAI and Google publish theirs).
Voice notes
If you say what you ate instead of typing it, the microphone is on only while you are speaking, and the audio is turned into text by the phone's speech recognition service. On devices that support offline recognition, that happens entirely on your phone; on others the operating system may send the audio to Apple or Google to transcribe it under their privacy terms. Either way we never receive or save the recording, and only the resulting text travels with your estimate request, exactly as if you had typed it.
Anonymous usage statistics
The app sends anonymous product analytics to PostHog, hosted in the EU. Events cover things like: the app was opened, which setup screens people reach and complete, onboarding was completed, where you heard about Nomzo and whether you'd tried a food diary before (each picked from a fixed list, and only if you answer), an estimate was requested or saved or undone, the paywall was viewed or closed, a purchase was started, finished or backed out of, a lower-priced offer was shown, taken or declined, a camera or notification permission was answered, Your plan was opened or an edit was saved there (which setting changed, never the new value), a consistency badge was earned, a streak moment was shown or a milestone was shared, and a streak reminder was scheduled. Events are tied to a random device ID, not to you, and they never contain dish names, notes, calorie values, photos, your weight, goal weight, height, age, sex, calorie target or any free text. The streak events carry your streak's day count, a small whole number, and the badge events carry which badge it was. What you eat and your body measurements stay on your phone.
The same service tells the app which version of a screen to show, for example which layout of the subscription screen. That request carries the same random device ID and nothing else about you.
You can turn analytics off in Settings. The switch takes effect the next time the app launches. It covers everything the app itself sends, but not the subscription events RevenueCat sends from its own servers (see "Purchases").
Purchases
Subscriptions are processed by Apple or Google, depending on where you downloaded Nomzo, and managed through RevenueCat. RevenueCat links your purchase to the same anonymous device ID so Pro works without an account. We never see your payment details; the app store handles those. Apple, Google and RevenueCat keep purchase records under their own policies. RevenueCat also passes subscription events (a trial started, a subscription renewed or was cancelled) to our PostHog analytics under the same random device ID, so we can tell whether a change to the app helped. Those events come from RevenueCat, not from the app, so the analytics switch in the app doesn't stop them. They carry only that random ID and what happened to the subscription. We never send RevenueCat anything about you beyond that ID: no name, no email and none of your setup answers.
Free trials, renewal and cancellation are covered in the terms of use.
Notifications
The optional daily reminder is a local notification, scheduled on your phone. Nomzo asks whether you want it during setup, and again after your first log if you said not now. It comes shortly after the dinner time you picked, only on days you haven't logged anything. Nothing about it is sent anywhere, including your dinner time. It only exists if you say yes to the permission prompt, and you can turn it off in Nomzo or your phone's system settings at any time.
What we never do
- No accounts and no sign-up. We never ask for an email address.
- No ads and no ad tracking.
- No selling or sharing data with data brokers.
- No health data used for advertising, ever.
Your identity in all this
The only identifier is a random UUID generated on your device. It is used for three things: rate-limiting estimate requests, linking your Pro purchase, and anonymous analytics. It is not your name, email, Apple ID, or Google account, and we cannot connect it to you.
Deleting your data
Delete the app. That deletes your entire food log, because your phone is the only place it exists. The anonymous device ID and the technical logs on our side contain nothing about your food and expire from our systems in the normal course of operation. If you want anything checked or removed, email info@nomzo.app.
Legal basis (GDPR)
We are based in Lithuania and follow the GDPR. Processing your estimate request (sending the photo and note to the AI provider) is done under legitimate interest: it is the one thing the app exists to do, you initiate each request yourself, and nothing is kept beyond the provider's short abuse-detection window. Notifications are sent only with your consent. Anonymous analytics rest on legitimate interest in understanding whether the app works, and you can switch them off. Your setup answers, including your weight, height, birth year and sex, are processed only on your phone and never reach us.
You have the usual GDPR rights (access, correction, erasure, objection). Since your data lives on your device, most of these you can exercise directly, but you can always email us. You can also complain to the Lithuanian State Data Protection Inspectorate (vdai.lrv.lt) or your local supervisory authority.
Age
Nomzo is for people aged 13 and up. Calorie estimates are rough guesses, not medical or dietary advice.
Changes
If this policy changes in a way that matters, we will say so in the app's release notes and update the date at the top.