What Knoomi knows about you
Knoomi is a nutrition app, so it holds some of the most personal information there is: what you eat, what you weigh, how you train and how you sleep. This is the honest account of what we collect, why, who else sees it, and how to get rid of it.
Last updated 2026-10-23
We collect what the app needs in order to work: your email address, the food and body data you enter, and the activity data you choose to connect. We do not sell it, we run no advertising and do no cross-app tracking, and you can delete your account and its data from inside the app at any time. When you photograph or describe a meal or import a recipe, that content is sent to an AI provider (OpenAI or Cloudflare) to read it — the app asks you before the first time. Crash reports go to Sentry. Product analytics (PostHog) and AI-quality tracing (Langfuse), both hosted in the EU, run only if you turn on “Help improve Knoomi”.
Who we are
Knoomi is the nutrition app described on this site, together with its servers. It is operated by EpicTech Solutions LLC, 1209 Mountain Road Pl NE, Albuquerque, NM 87110, United States. Where this policy says “we”, it means that company.
For anything about your data — a question, a correction, a copy, or a complaint — write to privacy@knoomi.app. A person reads it.
What you give us directly
Everything in this list exists because you entered it or connected it. None of it is inferred from tracking you elsewhere.
- Your EMAIL ADDRESS, from signing in. Knoomi supports a one-time code by email, Sign in with Apple, and Google. With Apple's private relay, we only ever see the relay address.
- FOOD AND DRINK you log: meals, snacks, portions, barcodes you scan, searches you type, recipes you save or import, meals you teach the app, and your shopping list.
- BODY MEASUREMENTS you record: weight and waist. Progress photos, if you take them, stay on your phone; they are not uploaded.
- TRAINING: sessions, sports, routines and the adjustments you make to them.
- YOUR ANSWERS from onboarding: goal, height, age, work type, movement, wake and sleep times, drinks, and food preferences — the inputs the day's plan is built from.
- PHOTOS you take of food, a nutrition label or a training plan, and the camera roll images you choose to add. A photo sent for an estimate is not stored by our servers; a recipe or shared-meal cover photo you choose is stored.
- WHAT YOU TELL “IMPROVE THIS MEAL”. When you change a meal suggestion in words (“add chicken”, “no rice”) or turn a food down, Knoomi keeps that session so we can make its suggestions better. It holds what you typed, kept exactly as you typed it (so please leave out personal details); how the app read it; the meal's foods and portions; the meal type, the date and the time of day; the meal's calorie and macro target; your diet and allergy settings; the suggestions shown before and after, and which one, if any, you applied; the foods you turned down; whether an AI model or the app's own rules chose the answer; and the app version and the country the app is set to. It holds no name or email from your profile and none of your other meals. It carries your account ID only so that deleting your account deletes it; copies we take out to turn into tests of the app carry no account ID and stay after your account is deleted. A session where you changed nothing (you only applied or closed a suggestion) is never sent. Nothing is sent while “Learn from my choices” is off (Settings → Food preferences), including sessions saved on your phone before you turned it off, which are deleted instead of sent.
What your device provides, with your permission
Each of these is behind a permission prompt on your phone (iOS or Android). Decline it and the app keeps working; the corresponding feature simply has less to go on.
- APPLE HEALTH (iPhone) and HEALTH CONNECT (Android) — read only. Knoomi writes nothing to Apple Health or Health Connect. With your permission it reads exactly six kinds of data: STEPS and FLOORS CLIMBED, to estimate how much you moved, which sets how much food your day carries; and, if you connect a watch or fitness app, last night's SLEEP, so your day and first meal start when you actually woke up, and your finished WORKOUTS with their HEART RATE and ACTIVE CALORIES, so they are logged for you (heart rate is used to judge how hard a session was; active calories are shown with the workout). Knoomi reads it only while the app is open.
- What is kept: only what Knoomi works out from that data — your daily steps and movement, your wake and bed times and how long you slept, and each workout's sport, start, duration, average and peak heart rate and active calories — saved with the rest of your data, after you agree to back up health information, so a reinstall restores your days. Health data is never sold and never used for advertising or marketing; it reaches only the providers listed under “Who else sees it”, for the purposes described there.
- If you choose to send a bug report, its snapshot of your saved Knoomi data can include some of those values: your daily steps and movement, your wake and bed times, and a workout's average heart rate. A report is only ever sent when you tap send.
- Knoomi's use of information received from Health Connect adheres to the Health Connect Permissions policy, including the Limited Use requirements.
- CAMERA — scanning barcodes, photographing meals and nutrition labels, and progress photos.
- PHOTO LIBRARY — only the images you explicitly pick.
- BLUETOOTH — connecting to a smart scale to read a weight.
- NOTIFICATIONS — reminders about your next meal. They are scheduled on your phone; no push token is sent to us.
What we collect automatically
Knoomi ships no advertising SDK and does no cross-app tracking: there is no ad identifier and no profile built for marketing. What it does collect without you tapping anything is listed here.
- A DEVICE IDENTIFIER we generate ourselves, plus the device name and app version, so a change made on your phone and a change made on your iPad can be told apart when they sync.
- SYNC TIMESTAMPS — when a record was last written, so your devices can agree on what is current.
- CRASH AND PERFORMANCE DATA, sent to Sentry: when the app crashes or hits an error, the error, the screen it happened on and the recent app events leading up to it (with anything you typed removed); and performance timings — how long the app took to start and each screen to appear, and slow or frozen frames. Each report carries the device model, the OS and app version, and your account ID — never your email, and never a screenshot or a picture of the screen. Errors in our server functions are reported the same way. This is automatic, because a crash cannot ask first.
- IF YOU SEND A BUG REPORT, and only then (Settings → Help → Report a bug): your description, your email address, an ID for this install, the app version, the crash-report ID of the last error (so we can find it in Sentry), the last few screens and taps, and a snapshot of the app's state at that moment. That snapshot is a copy of your saved Knoomi data — logs, plan, body, training and movement — because that is what makes a bug reproducible. The sheet says so before you send. Sending one is always your choice.
- IF YOU TURN ON “HELP IMPROVE KNOOMI” (off unless you turn it on, in Settings), that one switch sends the following. To PostHog: product analytics events (which screens and features you use), a record of each AI request (which feature called which model, how many tokens it used, what it cost and how long it took — never the content of the request or the answer), screen recordings of the app with every text field, every photo and your body measurements hidden, and your answers to any short in-app survey you choose to fill in. To Langfuse: traces of the app's AI requests — which feature called which model, how long it took, how many tokens it used — together with the content of the request and the answer, after personal details such as email addresses, phone numbers and images have been removed. Each trace is labelled with a salted one-way code rather than your account ID, but the PostHog record of the same request carries both your account ID and the trace's ID, so the traces can be linked back to your account. Turn it off at any time with the same switch, and all of it stops.
Why we process it
Under the GDPR, the legal basis for each of these is the performance of our contract with you — you asked us to run a nutrition service — except where noted.
- To run the product: build your day, estimate portions, predict hunger, suggest meals, and keep your history.
- To sync your data between your devices and restore it if you reinstall.
- To operate your subscription and honour restores.
- To answer support, fix crashes, and fix bugs you report. Crash reporting relies on our legitimate interest in an app that works.
- PRODUCT ANALYTICS AND AI TRACING (PostHog, Langfuse) run only on your CONSENT, given with the “Help improve Knoomi” switch and withdrawn the same way.
- HEALTH-RELATED DATA — food, weight, body measurements, activity — is a special category under GDPR Art. 9. We process it on the basis of your EXPLICIT CONSENT, given when you enter it and when you grant the Health permission. You can withdraw that consent by deleting your account.
Who else sees it
These are the only third parties that receive your data, and each receives only what its job requires. None of them is permitted to use it for their own purposes.
- SUPABASE — our database, authentication, file storage and server functions. Effectively all of your stored data lives here.
- OPENAI — when you photograph a meal, a restaurant plate or a nutrition label, describe a meal in words, search for a food, import a recipe from a link or a training plan from a photo, or ask Knoomi to improve a meal, that content is sent to OpenAI so a model can read it. Product details for a barcode you scan may also be sent, to fill in missing nutrition facts. That means the photo or the text, not your history, your weight or your identity. It is sent from our servers, not from your phone, and OpenAI does not use it to train its models.
- CLOUDFLARE (WORKERS AI) — some meal descriptions you type, and pictures the app generates for a meal, are processed by models hosted by Cloudflare, under the same terms: content only, from our servers, not used for training.
- BEFORE THE FIRST TIME a feature sends your content to one of these AI providers, the app asks you. Photo and voice logging, describing a meal in words, recipe and training-plan import, recipe sharing advice, the wording and suggestions in Improve this meal, grocery search help and barcode details use AI. Knoomi is built around these features, so we ask everyone to agree before they start using the app. Your meal plan itself is worked out without AI. You can withdraw that agreement at any time in Settings › Account; the app then pauses until you agree again, and you can still sign out or delete your account.
- SENTRY (Functional Software, Inc., hosted in the United States) — crash and performance data, as described above, with your account ID so we can find the data a crash happened on. Sentry processes it under its data processing agreement, which includes the EU Standard Contractual Clauses.
- POSTHOG (EU cloud, Frankfurt) — product analytics, feature flags, a usage record of each AI request (model, tokens, cost and timing; no content), masked screen recordings and in-app survey answers, only if you turn on “Help improve Knoomi”. Events are explicit ones the app chooses, with no automatic capture of taps; recordings hide every text field, photo and body measurement; a survey answer is only what you choose to write.
- LANGFUSE (EU cloud) — traces of AI requests, including the redacted request and answer content, only if you turn on “Help improve Knoomi”. Each trace is labelled with a salted one-way code rather than your account ID; because PostHog's record of the same request carries your account ID, we can link the traces back to your account.
- APPLE — in-app subscription purchases. Apple tells us your transaction identifiers and subscription status; Apple never gives us your payment details, and we never see your card.
- STRIPE — if you subscribed on the website rather than in the app. Stripe processes the payment; we store a customer and subscription reference, never card details.
- RESEND — sending you transactional email, such as a sign-in code. If you join the launch list on this website, Resend also keeps that email address and where the signup came from (see “This website”).
- ANTHROPIC — only for bug reports you choose to send. Our team reads them, and so do AI tools from Anthropic that we use to find and fix the problem, as the report screen tells you before you send. That includes whatever health-derived values the report's snapshot holds (see above).
- EXPO — delivering app updates. It sees an update request from a device, not your content.
- ANYONE YOU SHARE A MEAL LINK WITH. A shared meal link is deliberately public to whoever holds it: that is what makes it shareable. It contains the meal you chose to publish — not your name, your email or any other part of your account — and you can revoke it from the app, which kills the link permanently. Recipe photos you add are stored at addresses that are hard to guess but are not access-controlled, in the same way.
Where it is processed
Our infrastructure providers operate internationally, so your data may be processed outside the country you live in, including in the United States. PostHog and Langfuse data is hosted in the European Union. Where data leaves the European Economic Area, the transfer relies on the European Commission's Standard Contractual Clauses in our agreements with those providers.
How long we keep it
Your account data is kept for as long as you have an account. When you delete it, the deletion described below runs immediately.
Two things outlive that, and we would rather say so than let you discover it:
- BACKUPS. Our database provider keeps automated backups on its own rotation. Deleted data can persist in those backups until they age out; it is not restored to the live system, and it is not used for anything.
- PAYMENT RECORDS. Records of transactions are retained where tax and accounting law requires. Deleting your account UNLINKS those records from you — the reference to your account is removed — so what remains no longer identifies you.
- BUG REPORTS you sent are kept until the bug is fixed; one that reproduces a bug can be kept as a test case for as long as that test exists. They are not removed by the in-app deletion — write to privacy@knoomi.app and we will delete them.
- CRASH AND PERFORMANCE DATA is kept by Sentry for at most 90 days. PostHog events are kept for up to 12 months and Langfuse traces for up to 30 days, then deleted.
Deleting your account
In the app: Settings → Account → Delete my account. It asks you to type DELETE, and then it removes your food and drink logs, your recipes, taught meals and shopping list, your weights and waist measurements, your training and calibration, your onboarding answers and preferences, your shared meal links and their images, your recipe photos, your subscription records, and your sign-in itself. Sessions on your other devices are revoked.
Two honest warnings. First, deleting your account does NOT cancel an App Store subscription — only you can do that, in Settings → Apple ID → Subscriptions, and you should do it first if you want the billing to stop. Second, deletion is permanent; we cannot restore it afterwards.
You never have to email us to delete an account. If the in-app flow fails, write to privacy@knoomi.app and we will complete it by hand.
Your rights
If you are in the UK, the EU or a jurisdiction with comparable law, you have the right to access your data, correct it, delete it, take a copy elsewhere, object to or restrict processing, and withdraw consent. Exercise any of them by writing to privacy@knoomi.app.
You also have the right to complain to your data protection authority. We would rather you told us first, but that right is yours regardless.
If you are in California, you have the rights to know, delete, correct and opt out of sale or sharing. We do not sell or share personal information as those terms are defined, and we do not offer financial incentives for it.
Security
Traffic between the app and our servers is encrypted in transit with TLS. Data at rest is encrypted by our hosting provider. Access to your rows is enforced at the database level, so one account cannot read another's data even if the app were compromised. Server credentials never reach the app: everything privileged runs in server functions, and the app has no ability to grant itself access to anything.
We will not claim more than that. No system is immune, and if a breach affects you we will tell you and the relevant authority as the law requires.
Children
Knoomi is not for children. It is not directed at anyone under 16, and we do not knowingly collect data from anyone under 16. If you believe a child has created an account, write to privacy@knoomi.app and we will delete it.
This website
The site uses no advertising cookies. It measures visits with privacy-friendly analytics from PostHog (EU cloud) that run without cookies or any other stored identifier and do not store your IP address, so each visit is anonymous and cannot be linked to the next. It records the pages you view, the buttons and links you click (never what you type), how far you scroll, the campaign tags in the link that brought you (such as an ad's utm_source), the domain of the site that sent you, and your approximate country, which our host works out from the connection without us seeing or storing your IP address. If you join the launch list, we keep your email address with Resend together with the page you signed up on, those campaign tags, that referring domain and that country, so we know which posts and ads bring people; we use it only to tell you when Knoomi launches, and every such email has an unsubscribe link. The only value stored in your browser is your light/dark theme choice, so the page does not flash the wrong colour on load. If you start a checkout, Stripe's own hosted page applies its own cookies under Stripe's policy — none of Stripe's components run on knoomi.app.
Changes
When this policy changes we update the date at the top. If a change materially affects how we handle your data, we will tell you in the app or by email before it takes effect, rather than relying on you to re-read the page.