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.
In the newest testing build, optional Apple Health access shows steps, active energy, walking and running distance, workouts and weight in Activity and Body. These readings are held in memory on your device and are not included in account sync, Nomivo widgets or exports. They do not automatically change your food target. Nutrition writing is off by default; you can enable it separately for subsequently logged or edited meals. Apple controls its own Health storage and sync separately.
Earlier testing builds could copy Health-derived weight or active energy into the profile or account snapshot. This update stops those automatic copies but does not erase existing weight history. Profile and weight history already saved in your log can still sync with your account.
Meal plans and grocery checkmarks stay in protected account-specific files on this device, excluded from device backups. They are not cloud-synced. Deleting the account clears its local meal plans. CSV import is reviewed before saving and follows the normal food-log sync rules; imported rows are not written to Apple Health.
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. You can also sign in using a one-time code sent to your email address through Resend. Codes expire after 10 minutes, can be used once, and are protected by attempt and delivery limits. The backend stores digests of the code and device challenge rather than plaintext codes. Your session credential is kept in the iOS Keychain.
Saved-meal templates are associated with your account separately from diary snapshots. 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.
An optional Fitbit connection.
Where available, you can connect Google Health to view daily steps, active energy and distance from compatible Fitbit and Pixel Watch devices. Nomivo requests read-only activity and fitness access after showing an in-app explanation. It does not fetch heart rate, sleep, location routes or nutrition through this connection.
Google supplies the readings to our Vultr-hosted API, which sends them over HTTPS through Cloudflare to your phone. Readings remain in memory for display; we do not save them in the account database, meal log, server logs or backups, and do not send them to AI providers. They are not added to Apple Health totals or food targets.
Our database stores encrypted connection credentials, a protected provider-account identifier and connection timestamps. Incomplete linking requests expire after ten minutes and are removed by a five-minute cleanup task. Disconnecting in Health connections removes live credentials and clears displayed readings; we also request Google revocation. If Google cannot confirm revocation, the app provides a link to finish it in your Google account. Account deletion removes the connection and attempts revocation. Restricted backups can retain encrypted credentials until they rotate out, as explained below. Google keeps its own original records.
Nomivo follows the Google Health API Developer and User Data Policy and its Limited Use requirements. Google Health information is used only for the activity features you choose, never sold or used for advertising, credit decisions or AI training. Human access is limited to your explicit consent or permitted security and legal needs.
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.
- Google supplies optional Google Health readings and manages the permissions for that connection.
- 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.
- Resend delivers sign-in codes and operational alerts. Login delivery involves your email address and the message contents.
- Spacemail by Spaceship hosts [email protected]. When you contact support, it processes your address, message, attachments and our replies. Please avoid sending passwords or unnecessary health 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 retain aggregate recognition token/outcome counters for up to 62 days to monitor reliability and costs. These aggregate counters contain no account IDs, meal names, photos or prompts. Abuse protection uses expiring account/network rate buckets; network bucket keys are hashed with a server secret. Expired login challenges and rate buckets are cleaned up during subsequent requests.
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. Rotation depends on successful backup runs, so it is not a guaranteed time-to-erasure deadline.
Account deletion is available in Me → Your account. Deletion removes the account, synced diary and saved-meal library from the live service. A minimal internal deletion receipt is kept so an old backup is not used to restore a deleted account. It contains an internal identifier and deletion status, not your profile or meal records. Apple and other providers handle their own records separately.
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.
For access, correction or deletion requests, contact Global Tech Stream LLC at [email protected]. We may need to verify your account before acting on a request. Do not send passwords or identity documents unless we have explained a necessary verification process.