Privacy Policy.

Ness stores the food data you put into it so your kitchen and your tracker follow you between devices. We do not sell your data, we do not run ads, and we do not use it to build advertising profiles. Your camera feed never leaves your device, Ness never reads your Apple Health data, and your pantry is only sent to our recipe and AI services after you allow it. You can delete your account and everything in it at any time from your profile page.

Account. Your email address and a password, handled by our authentication provider. Passwords are hashed by that provider and are never visible to us. Optionally a username.

Food and kitchen data. Pantry items you add or scan (name, barcode, quantity, how much is left, expiry date, nutrition information), meals you log (name, quantity, calories and macros, date, and meal type), recipes you save (title, ingredients, steps, source link, nutrition, notes) and the lists you organise them into.

Recipe photos. Photos you choose to add to your saved recipes. Before upload, Ness shrinks each photo and saves it as a new image, which drops the original's hidden details, such as where it was taken. Each photo is stored at a web address that can't be guessed and isn't listed anywhere, so only someone given that exact address could open it.

Settings. Your daily macro goals and your feature preferences.

Recipe generation counts. To keep recipe generation available to everyone, we count how many times each person generates recipes per day. If you are signed in, the count is tied to your account. If you are not, we store a one-way, keyed hash of your IP address instead of the address itself, which cannot be turned back into your address. These counts are deleted the next day.

Using Ness without an account. Scanning, the pantry and AI recipes work signed out. In that case your pantry is stored only in your own browser or device storage. If you later create an account, those items are uploaded so they are not lost. If you never sign up, they are never stored on our servers — they only pass through them, unsaved, when you ask for recipes.

What we do not collect. We do not ask for your location or contacts, we never read your Apple Health data, and we do not track you across other apps or websites.

The barcode scanner runs entirely on your device. The video feed is never uploaded, recorded, or stored. When a barcode is decoded, the only thing sent from your device is the barcode number itself, so we can look up the product. Camera access is requested only when you start the scanner, and you can decline it and type barcodes by hand instead.

You can also use the camera to take a photo for one of your recipes. That photo is uploaded only when you add it to a recipe, and you can remove it at any time.

The iOS app can save the meals you log to Apple Health. This is off until you turn it on in your profile, and iOS asks for your permission before anything is written.

What is written. For each meal you log while it is on: the food name, calories, protein, carbohydrates and fat, and the date. These are copies of meals already in your Ness tracker.

What is read. Nothing. Ness asks only for permission to write, so it cannot see anything else in Health — not your activity, sleep, heart rate, or anything logged by another app.

Where it goes. Entries saved to Health are stored and protected by the Health app, under your control. Ness never sends Health data to our servers or to any third party, and never uses it for advertising or marketing.

Turning it off. Switch it off in your profile, or in iOS Settings › Health › Data Access & Devices › Ness. Entries already saved stay in Health until you delete them there — Ness does not remove them, including when you delete your Ness account.

The iOS app can remind you before something in your pantry goes off. This is off until you turn it on from your pantry, and iOS asks for your permission first.

The reminders are scheduled by your phone, not sent by us. There is no push service, no device token, and nothing about your pantry leaves the device to make them work — which is also why they only know what was in your pantry the last time the app was open.

Nothing is sent until you allow it. The first time you ask for recipes, Ness explains what will be shared and asks for your permission. Only then does it send your pantry items (names, amounts, how much is left, expiry dates and nutrition), your macro targets and your preferences to Spoonacular, to search for recipes, and to Google Gemini, an AI service, to rank them and to write recipes when search is unavailable. Your name, email address, account and meal history are never sent.

How Google may use it. Ness uses Gemini under Google's terms for its unpaid service tier. Under those terms, Google may use what it receives, and the recipes it returns, to provide and improve its products and AI models, and human reviewers at Google may read it. This is why Ness sends only the food details needed to find recipes, and nothing that identifies you. Gemini is not used for visitors in the European Economic Area, Switzerland or the United Kingdom; there, recipes come from Spoonacular alone.

Stopping. Tap Stop sharing on the recipes page at any time. Ness then sends nothing to Spoonacular or Gemini until you allow it again. This cannot recall what was already sent.

AI-written recipes. Recipes written by AI are labelled as such, and their nutrition is an estimate. Treat it as a guide, not medical or dietary advice — check with a doctor or dietitian before relying on it for a medical condition.

Ness relies on a small number of third-party services. Each receives only what it needs to do its job.

Each service handles what it receives under its own terms and privacy policy. Supabase and Vercel run Ness for us and process your data only to do that. Open Food Facts, USDA and Spoonacular receive only the details listed above, none of which identify you, apart from the IP address that loading a recipe photo from Spoonacular or a recipe website exposes, as any web request does. Google may also use what Gemini receives, as described in Recipes and AI. Your email address and meal history go to Supabase, which stores your account, and to none of the others. Apple Health is not on this list: entries you choose to save there stay in the Health app under your control, as described above.

Meal logs are deleted automatically. Ness keeps only the current calendar month and the month before it. Once a month becomes two months old, those entries are permanently removed. This is a storage limit, not a backup — if you need a long-term record, keep your own copy.

Recipe generation counts are deleted the day after they are recorded.

Everything else — your profile, pantry, saved recipes, recipe photos and lists — is kept until you delete it or delete your account.

You can delete individual pantry items, meals, and recipes at any time from within the app.

To remove everything, open your profile and choose Delete account. This permanently removes your login, profile, pantry, meal logs, saved recipes, recipe photos and lists. It takes effect immediately and cannot be undone — we cannot restore a deleted account.

If you turned on Apple Health sync in the iOS app, meals already saved to Health are not affected by deleting your account. Remove them in the Health app.

Ness sets cookies for one reason: to keep you signed in. They hold your session so the app knows it is you as you move between pages and come back later. Signing out clears them.

There are no advertising cookies, no analytics, and no third-party trackers, which is why you are not asked to accept anything. The app also keeps a little information in your browser’s own storage — the pantry you build before signing up, and whether you have seen the welcome tour. That never leaves your device, and clearing your browser data removes it.

Data is transmitted over encrypted connections. Every table is protected by row-level security, which means the database itself enforces that you can only ever read or write your own rows, not just the app. Keys for the third-party services above are held on the server and are never sent to your device.

No system is perfectly secure, and we cannot guarantee absolute security.

Ness is for people 18 and older and is not directed at anyone under 18. We do not knowingly collect information from them. If you believe a child has given us personal information, contact us and we will remove it.

If this policy changes in a way that materially affects you, we will update the effective date above and, where appropriate, notify you in the app.

Ness is run by Neal Abraham and Ebby Thaliath Bejoy, two individuals rather than a company, who are responsible for the data described here.

Questions about this policy or your data: nessapp.help@gmail.com.