Privacy Policy for Nomva

Last updated: October 11, 2026

Overview

Nomva helps you track meals, hydration, activity-based calorie targets, and weight. This policy describes current Nomva data handling. We do not sell personal information or use health data for advertising.

Nomva's web app is available at nomva.nerdquad.com/app. Shared-account features require a mobile version that includes Account & Sync. Older iPhone versions keep their existing local behavior. The Android app is in release preparation and is not yet publicly available on Google Play; Google Play purchases require the replacement developer account and live billing setup.

Information stored on your device

Food logs, water entries, goals, weight history, custom foods, chat history, and related logging records are stored locally. The iPhone app uses iOS data protection, Android uses its app-private storage, and the web app uses your browser's storage. These are not separate password-protected vaults. In local mode, Nomva does not upload this history for account synchronization. Browser data can be lost if you clear site data, use a temporary browsing session, or lose the device.

Optional account and shared history

Creating an account requires your email address, a password, and consent to synchronize personal logging records. We also store an optional display name, account identifiers, password and recovery-key verification hashes, session records, and verified subscription information. Passwords are salted and hashed; recovery keys and session tokens are stored as verification hashes.

When you choose account synchronization, Nomva sends food, water, weight, goals, profile, custom foods, chat history, saved meals, and shared preferences to its service. Weight records may include measurements previously imported from Apple Health or Health Connect, their source identifiers, and notes. Existing local history is imported only when you explicitly choose to import it; signing in alone does not silently upload it. Health permissions, device credentials, and platform-specific Health synchronization controls stay on the device. The browser reads synchronized Nomva records and does not directly access Apple Health or Health Connect.

Account records travel over HTTPS and their stored payloads are encrypted on the server. This is not end-to-end encryption: Nomva's service can decrypt records to provide synchronization and account exports. Separate account storage and authentication restrict access to the signed-in account. Changes made offline remain on that device until they successfully synchronize. Conflicting edits require your choice, and deleted records are retained as synchronization markers so another device does not silently restore them.

You receive a recovery key when creating an account or replacing the key. Keep it in a safe place outside Nomva; it can reset your password and revoke other sessions. Email password recovery is offered only when the service indicates that email delivery is configured. We currently provide recovery-key recovery and do not promise email delivery.

Apple Health, Health Connect, and Garmin

On iPhone, with your permission, Nomva reads active energy and body weight from Apple Health. Activity totals are refreshed on the device to update the selected activity source's calorie target. If you enable Save Nomva Weigh-ins, Nomva writes your Nomva-authored weights and their corrections to Apple Health. Removing one of those weights can also remove Nomva's corresponding Health sample after the undo period. Removing an imported weight in Nomva hides it locally without deleting another app's Health sample.

On Android, with your permission and the matching in-app sync controls enabled, Nomva reads up to 30 days of body weight and active calories from Health Connect. It can write weigh-ins you add in Nomva to Health Connect and delete its corresponding Health Connect records when you delete them in Nomva. Deleting an imported weight from Nomva does not delete another app's Health Connect record. Nomva stores local record identifiers and sync settings to limit duplicate imports and manage its own exports. You can manage Health Connect permissions in Android settings and turn off import, export, or activity reading in Nomva.

On iPhone, Garmin weight synchronization uses Garmin Connect → Apple Health → Nomva. Nomva can save its own weigh-ins to Apple Health; it does not write them to Garmin. Apple's Health synchronization is controlled separately by your Apple Account and Health settings. Nomva retains local sample identifiers, sync progress, and deletion preferences to avoid repeated imports.

A separate optional Garmin activity connection uses Nomva's server to receive daily activity summaries, including active calories and available steps/total calories. The server stores those summaries and the encrypted credentials needed to maintain the connection. Disconnecting Garmin in Nomva removes that connection and its cached activity summaries. The former direct Garmin weight import is retired; legacy body-composition deliveries are discarded.

Automatically imported Apple Health or Health Connect measurements and local weight notes are not attached to cloud AI requests. Supported weight-history questions are answered locally. Information you explicitly include in an AI message or chosen photo may be processed as described below. On iPhone, you can change Health permissions in the Health app and stop import/export in Nomva's Weight Sync settings.

AI processing and food lookup

When you use cloud AI, your request text, limited relevant conversation or food context, and photos you choose to analyze are sent through Nomva's service to OpenAI for processing. Food and restaurant lookup may use online sources. Do not include information you do not want processed by these services. Provider processing is subject to that provider's policies.

The AI processing service does not intentionally retain full conversations or photos after processing, and production diagnostics exclude raw request and response content. If you enable account synchronization, your saved chat messages are separately retained in your account as shared history. Photos chosen for analysis are not stored as synchronized history. The service caches food names, lookup aliases, nutrition estimates, and published nutrition sources to improve future lookups; this cache is separate from your personal diary. Published lookup records normally expire after 180 days and estimates after 30 days.

The bundled food catalog combines USDA FoodData Central and Open Food Facts records, including Open Food Facts fields merged into some USDA rows. The complete combined catalog is available under the Open Database License; see food data sources and license for attribution and a machine-readable download. Barcode lookup first checks that catalog and device cache. If needed, the barcode is sent directly to Open Food Facts without your chat or weight history. Manual logging is available without cloud AI.

Web catalog search sends the search terms or barcode to Nomva's server, including in local mode. It does not send your local diary with the search. Raw catalog queries are excluded from production diagnostics. The web app needs a connection to search the server catalog; cached records and local logging remain available while its open page is offline.

Diagnostics, access, and purchases

Nomva uses limited operational diagnostics such as hashed app identifiers, request route, response status, duration, model, and token counts. These records exclude raw chat text, photos, food names, barcodes, and weight values and are retained for up to 90 days. On iPhone, remove linked diagnostics in Settings → AI & Privacy → Delete Cloud Analytics. On Android, contact support to request deletion of linked service diagnostics.

The service retains authentication, subscription-verification, and request-limit records needed to provide and protect access. Apple handles iPhone subscription payments; Google Play handles Android subscription payments when available. Linking a verified purchase to your Nomva account makes its active Pro access available on other supported clients. A store purchase can belong to only one Nomva account at a time. Nomva receives verified entitlement information and purchase identifiers; it does not receive your payment-card details. The web app does not currently sell a separate subscription. Nomva does not include advertising frameworks or third-party analytics SDKs.

Backups and recovery

Local mobile application history is excluded from automatic device backup. In local mode, export a JSON backup in Settings → Backup & Export before replacing your device or reinstalling Nomva. Exported backups and CSV reports contain personal information and are not password encrypted by Nomva; you choose where to save or share them. Their protection and retention depend on that destination. The Android and iPhone local JSON backup formats are different and cannot be restored across platforms. The iPhone app keeps a protected local recovery copy before restoring an archive. That local copy cannot recover data after the app or device is lost. The Android app merges a selected backup into its local history without making a separate recovery copy.

With account synchronization enabled, successfully synchronized records can be downloaded by signing into the same account on another supported client. Unsynchronized changes cannot be recovered from the server. You can export your account records as versioned JSON; this shared-record export is different from a native app's local restore archive. Nomva makes encrypted database backups on its server and retains up to seven daily snapshots. These backups do not provide an independent off-site recovery guarantee.

Older Nomva versions may have placed copies in your private iCloud account. The current app preserves existing local history and does not automatically delete those older cloud copies; manage them in Apple Settings. Apple Health maintains its own history and synchronization separately.

Deletion and your choices

You can delete entries in Nomva, stop Apple Health or Health Connect sharing, disconnect the Garmin activity connection, request deletion of linked cloud diagnostics, and export your data. Synced record deletions propagate to your other account clients when they reconnect. Account history and change markers remain until you delete the account. Deleting your account requires your password, revokes its sessions, and removes its active server history and account linkage. Deleted information may remain in the encrypted daily backups for up to seven days; limited operational diagnostics follow the retention period described above. Encrypted purchase-verification evidence may remain without its deleted account linkage to prevent purchase replay and process store events; request-limit records expire separately, normally within 24 hours.

Signing out does not delete your cloud account. On iPhone, deleting an account keeps a protected local recovery backup and saved device history, including your original guest history; remove the app to remove its remaining local copies. Use account deletion to remove server history, and separately clear device or browser copies that you no longer want. Removing Nomva or clearing browser storage does not automatically delete cloud history, exported files, Apple Health or Health Connect records, older iCloud copies, or server-side Garmin credentials. Disconnect Garmin before removing the app, or contact support for assistance with remaining service records. Deleting an account or uninstalling Nomva does not cancel a subscription; manage it with the store used for the purchase.

Changes and contact

We update this page when our data practices change. For privacy requests, support, or questions about retained service records, contact jerry@nerdquad.com.