NomivoKnow where your data goes.
Nomivo is operated by Global Tech Stream LLC, New Mexico, United States. This page explains the current website and app data flows. The app is in pre-release testing.
There are no advertising pixels, analytics scripts, newsletter forms or website accounts on this site. Opening it does not give us access to your phone’s food diary, camera or Apple Health records.
Your local food diary.
Nomivo stores your profile, food entries, water entries and weight history on your iPhone. Its widget accesses a shared on-device store. The app stores meal photos locally; those photo files are not uploaded by account sync.
If you connect Apple Health, Nomivo can read the weight and active energy categories you allow and write logged nutrition. Health-derived values used in your profile or history can be included in the account snapshot if you enable sync.
When you sign in.
Sign in with Apple provides an account identifier and, when supplied, an email address that may be an Apple relay address. Nomivo uses these to identify your account. Your session credential is kept in the iOS Keychain.
Signed-in profile and log snapshots are stored in a private database on our Vultr server in Frankfurt, Germany. Connections use HTTPS. Recovery copies are encrypted and stored separately on our backup storage. This is server-side storage, not end-to-end encrypted sync.
Signing out stops authenticated access on that installation; it does not delete an existing server account.
When you scan or search.
For a food or menu scan, the image you submit travels through our API to OpenAI for recognition. Our recognition route does not save the submitted image as a server photo file. The provider has its own processing and retention rules; this is not a zero-retention service.
OpenAI states that API data is not used to train its models by default, and that default abuse-monitoring logs may be retained for up to 30 days, with exceptions. Read OpenAI’s API data controls.
Product searches and barcodes are sent to Open Food Facts. That service receives the search request and connection information. Product data is community-contributed and can be incomplete. Read Open Food Facts terms and attribution information.
The services behind Nomivo.
- Vultr hosts our API and account database.
- Cloudflare provides DNS, website/API delivery and traffic protection. Network requests disclose technical information such as IP address, browser information and requested URL.
- Apple provides Sign in with Apple, Health permissions and App Store purchase processing when purchases become available.
- RevenueCat checks subscription status using the Nomivo account identifier and purchase information. We do not receive your full payment-card details. RevenueCat privacy information.
- OpenAI and Open Food Facts process the recognition and product-lookup requests described above.
Storage is not the same as forever.
Account records are currently retained while the account exists. Our operational server journal is configured with a 14-day retention limit and a size limit. We record recognition usage counts to understand service costs, rather than deliberately logging meal photos or prompt contents in those usage events.
Encrypted recovery storage rotates up to 14 daily and 8 weekly copies. Removing information from a live database does not immediately remove it from older backups. Recovery copies are restricted to recovery purposes.
The final account-deletion workflow and detailed retention policy are being completed before the public App Store release. This overview does not promise an automated deletion feature that is not yet available.
Controls that stay with you.
You can decline camera, notification or Health permissions, change them in iPhone Settings, use manual logging, review AI suggestions before saving, and export your food log. Camera and Health access are not requested by this website.
Deleting local logs, uninstalling the app, deleting an account and canceling a subscription are different actions. The help guide explains the current options.
Questions about your information.
We are completing the public privacy-request contact before launch. Invited testers should use their existing invitation contact. This is a pre-launch data overview, not the final app privacy policy.