Nyamly

Privacy Policy

Last updated 11 October 2026

What's stored on your device

Your meal log, water log, weight history, scan history and meal photos are stored on your device. Your weight history, Apple Health data and the meal photos you attach to a log entry stay on your phone and are never synced to iCloud. The rest can sync through your private iCloud database — see "iCloud sync" below. If you turn on photo estimates, the photo you take for an estimate is sent to Google — see "Photo estimates" below.

iCloud sync

When you are signed in to iCloud and iCloud sync is on in Settings (it is on by default), Nyamly keeps your meal log, scan history, My foods, saved meals, goals and preferences in your private iCloud database, so they come back after a reinstall or on a new device. That copy lives in your own iCloud account, under Apple's terms. Nyamly cannot read it, and it is not sent to Nyamly's servers. The contents of these records are encrypted on your device before upload (CloudKit encryption); with Advanced Data Protection for iCloud turned on, only you hold the keys.

Your weight (your weigh-ins and weight history), your Apple Health data and your meal photos are never synced. The target weight you enter is a goal and syncs with your other goals.

Your choice: turn iCloud sync off in Settings › iCloud sync. To delete the copy in iCloud, tap "Delete iCloud copy" there, or go to iOS Settings › your name › iCloud › Manage Storage › Nyamly. Data on your device is not affected.

Photo estimates (optional, on your consent)

Photo estimates let you photograph a meal and get an estimated dish name, weight, calories and macros back. This feature is off until you say yes on a dedicated screen the first time you use it, and it never runs without that consent.

What is sent: the photo you just took, reduced in size, with location and camera details removed — and, if you choose to type one, a short optional hint about the photo (up to 200 characters), sent to Google exactly as you typed it. Nothing else — not your name, your diary, your goals, your weight or anything that identifies your device, unless the photo or hint itself shows something identifying.

Who receives it: Google LLC, as a processor, through the Gemini API. Google may process it on servers in any country where Google or its agents operate.

How long it's kept: Nyamly does not store the photo on its own servers beyond the moment needed to process the request and return your estimate. Google does not use your photos to improve its general products. Google keeps the prompt and its response for up to 55 days for abuse monitoring; during that window, authorized Google staff may review flagged content, and Google may use retained prompts and responses to train or fine-tune models built specifically for detecting and preventing abuse of its services. There is no way to shorten or opt out of that 55-day window.

What Nyamly's own server keeps: to enforce the free and paid scan limits and prevent abuse, Nyamly's server also keeps a small record for each user: a salted, scrambled version of an identifier — a random secret that your device generates and keeps in its Keychain (iCloud Keychain can sync it across your own devices) — used as the key for your scan counters; how many estimates you've requested today and this month, how many of your free onboarding estimates remain, and the timestamps needed to enforce those limits; the version and date of the consent you gave; and a salted, scrambled version of a code identifying your device's App Attest key, used to stop one device from claiming more than one free allowance. This record never contains the photo itself or the estimate it produced — those aren't stored on Nyamly's server at all. Legal basis: performing the service you asked for, and Nyamly's legitimate interest in preventing abuse.

How long Nyamly keeps it: Nyamly deletes this record automatically. Your daily estimate counts are deleted after 35 days and your monthly counts after 14 months. The record itself — the scrambled identifier, your remaining free estimates, the version and date of your consent, and the scrambled App Attest key code linked to it — is deleted once you have gone a full year (365 days) without requesting a photo estimate. You can also ask us to delete it sooner, at any time, by emailing support@nyamly.fit. Because Nyamly stores only scrambled values, Settings → Legal & data sources lets you copy the identifier behind your record so you can include it in that request. Nyamly also keeps a record of your device's App Attest key itself, used to verify your device is genuine; it is deleted automatically 13 months after your device was last seen.

Your choice: you can decline or turn photo estimates off at any time in Settings › Photo estimates, as easily as you turned it on. Declining or withdrawing costs you nothing else in the app — barcode scanning, search and manual logging keep working exactly as before. Withdrawing stops future photos from being sent; it can't recall photos already sent before you withdrew.

Apple Health

If you enable it, Nyamly writes your logged weight, and the calories, protein, fat and carbohydrates from your meal log (including the food's name, attached to the calorie entry), and the water you log, to Apple Health (HealthKit), and reads your weight and your recent workouts (with their active energy, the calories burned), your step count, and nutrition (dietary energy, protein, fat and carbohydrates) logged by other apps back from Health so the app can stay consistent with what you already track there. Health data stays on your device and inside Apple's Health system — Nyamly never copies it to iCloud, Nyamly's servers never see it, but any other app you've granted Health access to can see what Nyamly writes there. You can revoke this permission at any time in iOS Settings → Privacy → Health.

Typed-text estimates

If you type a dish description instead of taking a photo, only that typed text is sent to Google's Gemini API to get an estimate back — no photo is sent, since none was taken. Everything under "Photo estimates" above about who receives it, how long it is kept, and your rights applies the same way to a typed description. If you dictate a meal, speech is turned into text on your iPhone; the audio never leaves the device. The food names you confirm are looked up in Nyamly's own food database through Nyamly's server on every device — that lookup happens whether or not Google Gemini was involved. When your iPhone can extract the foods from your dictation itself, nothing about it goes to Google Gemini at all. When it cannot, the confirmed text is sent to Nyamly's server, which forwards it to Google Gemini to extract the foods you named (never a nutrition estimate) — Gemini never receives it directly from your device.

Analytics, crash reporting and subscriptions

Firebase Analytics and Crashlytics (Google LLC): once you consent on the in-app analytics prompt, the app sends Google Analytics usage events (such as which screens you open and which features you use) and, if the app crashes or hits a handled error, a crash or error report, so Nyamly can see what's working and fix bugs. Collection is off by default and only turns on after you say yes. You can turn analytics off at any time in Settings, as easily as you turned it on — that stops future events and reports from being sent; it can't recall ones already sent. No advertising identifiers or ad-personalization data are collected.

RevenueCat: if you purchase Nyamly Pro, RevenueCat processes and validates the subscription with the App Store on Nyamly's behalf, so the app can tell whether your account is subscribed. It receives a pseudonymous identifier that Nyamly's server derives for your account (not tied to a single device) and your purchase/subscription status — not your name, email or payment details, which Apple handles directly.

What leaves your device

Barcode lookups and food search queries are sent to Nyamly's backend to retrieve product data (from Open Food Facts and the other sources listed on the homepage). The app authenticates these requests using Apple's App Attest, not an account or personal profile — Nyamly does not require you to create an account or sign in.

IP address: like any web service, Nyamly's server sees the IP address your device connects from. It is written to the server's access logs for security and troubleshooting. In addition, when your device proves to Nyamly's server that it is a genuine copy of the app (Apple App Attest — normally once per install), a salted, scrambled version of that address is counted for up to 30 days, to stop automated abuse of the free photo estimates. The address itself is never stored by that check. Access logs are kept for 14 days.

Data deletion

Deleting the app removes all locally stored data (meal log, water, weight history, scan history, photos). Data synced to iCloud stays in your iCloud account until you delete it, as described under "iCloud sync" above. To request deletion of any data Nyamly's backend may hold associated with your device, email support@nyamly.fit.

You also have the right to: access the data Nyamly's backend holds about you; have inaccurate data corrected; request restriction of, or object to, processing based on Nyamly's legitimate interest; and receive, in a portable format, the data you provided. Email support@nyamly.fit to exercise any of these. You also have the right to lodge a complaint with your local data protection authority.

Children's privacy

Nyamly is not directed at children and does not knowingly collect data from children.

Changes to this policy

If this policy changes, the "last updated" date above will change and the new version will be posted at this URL.

Contact

Privacy officer, and questions about this policy: support@nyamly.fit

← Back to Nyamly