NouriMe privacy policy

Effective: 20 October 2026. NouriMe is operated by Vũ Việt Anh. For support, privacy questions or data requests, contact contact.vuvietanhblog@gmail.com. This policy covers the NouriMe app and nourime.net.

What the app does

NouriMe provides informational nutrition and wellness support for adults aged 18 and over. It is not a medical device, diagnosis or treatment service. AI recognition and portion estimates can be wrong. Do not rely on an image to exclude allergens or replace advice from a qualified health professional.

Data on your device

Your profile, diary, logged meals, saved decisions, learning memory and settings are stored on your device. The profile can include age, sex, measurements, goals, conditions, allergies and nutrition targets. Local app storage is not encrypted by NouriMe. Protect access to your device.

A sign-in is not a full diary backup. The optional cloud backup described below backs up your profile, not your diary, photos or complete meal history.

Accounts and service operation

Google Firebase Authentication handles sign-in. The app supports email/password and configured Google sign-in; a temporary anonymous identity can also exist. Passwords are handled by Firebase, not exposed in our administration tools.

Our backend stores your account identifier, email where supplied, account status, creation/activity dates, app version and platform. Account onboarding can also store completion dates, locale, app/platform, and the acquisition answer you choose to provide. These records support account operation, troubleshooting and understanding registration sources. They are separate from your health profile.

Our API and hosting services receive the network information necessary to serve requests, such as IP addresses and request timing. Operational logs use bounded request/error codes rather than deliberately recording photos, full health profiles, passwords or provider credentials. Authorized staff can access account and operational records according to their roles; administrative actions are audited. The admin console has no screen for browsing your cloud health profile.

Optional remote food and menu analysis

Remote food and menu analysis require separate, default-off permissions. The app shows a disclosure before uploading. You can refuse and enter meals manually.

Food analysis sends the photo, barcode or description you choose, a limited profile and the day’s aggregate nutrition context to the NouriMe API. Profile fields include age, sex, goals, self-reported conditions/allergies, food preferences/restrictions, nutrition constraints, language and daily targets. Display name, weight, height, free-text health notes and recent meal names/times are excluded from this analysis request. The external explanation stage uses limited profile fields and governed condition summaries rather than raw free-text condition history.

Menu analysis sends your selected menu image and meal slot, without your health profile or day totals. Avoid including faces, documents or unrelated personal information in images. NouriMe’s API processes uploaded images in memory and does not intentionally archive the input image. Downstream processing has its own retention practices described next.

The configured AI route is our gateway at v-router.vuvietanh.com, forwarding to Qwen.ai. Qwen’s policy identifies NTH POWER GLOBAL TECH SINGAPORE PTE. LTD. as its operator and Alibaba Cloud (Singapore) Private Limited as an AI processor. It describes processing in Singapore, retention for service/security and legal purposes, and possible use of de-identified content for model improvement. We do not promise zero retention or no downstream training. Read Qwen’s privacy policy before sharing.

Turning off remote permission blocks future uploads; it cannot recall a request already processed. Contact us for help with a downstream data request. NouriMe does not itself use your health profile or meal content to train models, sell that data or target advertising. Scoring, simulation and ranking remain implemented by deterministic code; the model recognizes and explains.

Optional cloud profile backup

Cloud backup is a separate, default-off account permission. If enabled, a copy of your profile is stored using Google Cloud Firestore and can be restored on a signed-in device. This copy can contain health conditions and allergies, so Google’s cloud infrastructure does process health information when you choose backup. Withdrawal deletes the stored profile before disabling backup. You can also remove the synced copy or delete the account. App staff cannot browse this profile through the admin console. A profile backup is not end-to-end encrypted by NouriMe; the server stores the profile payload.

Measurement and Google Analytics

Optional first-party measurement requires the deployment to enable it and your separate consent. It uses an installation identifier and a limited set of coded usage events; it does not upload meal content, health answers or free-text notes. Withdrawing that permission requests deletion of that installation’s data. Measurement is currently disabled in this release’s production configuration.

Our admin connection to Google Analytics reads aggregate reports from a separate GA4 property. Connecting reports does not install an analytics SDK, upload app events to Google, or turn first-party consent into third-party tracking consent. The current app does not automatically forward its measurement events to GA4.

Notifications, email and payments

Notification permission, service updates, product news and marketing email categories are separate choices. If you enable a supported notification category and device registration succeeds, we store an Expo push token plus device, platform, locale and consent metadata. Delivery uses Expo and the relevant Google FCM or Apple APNs service. Tokens are not shown in normal admin listings.

If you opt into an enabled marketing email category, we use your verified email, category choices and delivery records to send those messages through the configured email transport. You can unsubscribe by category. Signing in, joining a waitlist or purchasing does not subscribe you to marketing.

The Google Play build does not open external digital-goods checkout or offer QR purchase/gift redemption. Existing entitlements can be checked. If you purchase through a separately offered website, transaction references, account/email, amount, plan, dates and payment status are processed for fulfillment and support; we do not collect your bank-login password in the app.

Reports, support and retention

When you report AI output, we retain the selected reason, a bounded output excerpt, optional comment and relevant app/request metadata for moderation. Do not put health records or credentials in a report or support message. Report records are not a backup of your analysis history and have no automatic age-based deletion schedule in the current implementation.

Account metadata remains while the account exists. A cloud profile remains until removed, backup is withdrawn, or the account is deleted. Local history remains until cleared or removed with the app. Optional measurement has a configured retention window of up to 30 days; its receipts have a 14-day window. Logical expiry applies even if background physical cleanup runs later. Operational rollups use a 90-day read window. Audit, deletion-protection, communication and transaction records may remain for security, fulfillment, disputes or legal obligations; they are not an unlimited backup of your health profile. Contact us about retention or erasure of a particular record. Third parties, including Qwen, apply their own published retention rules.

Your controls and data requests

Use the app’s privacy controls to change remote analysis, local learning, measurement and profile backup independently. You can export your account data, edit your local profile, clear learning memory or reset local data.

To delete an account, use Profile > Settings > Account > Delete account, or visit account deletion. The web form supports an email/password account. For Google-only or inaccessible accounts, use the app or email us; we verify control of the account before acting. Never send us your password or a provider token.

Account deletion removes the sign-in identity, account and synced profile and clears local data on the initiating app after server deletion succeeds. It does not erase another device’s local files, unrelated installation measurement or unlinked report records. Measurement has its own withdrawal/deletion control. Security/audit and legally required records can be retained as described above.

Depending on your location, you may have rights to access, correct, export, restrict or erase personal data, withdraw consent or complain to the appropriate authority. Contact contact.vuvietanhblog@gmail.com to exercise a right. We may need to verify your identity without asking for your password.

Hosting, transfers and changes

We use Google Firebase/Firestore for identity and cloud storage, Vercel for the API, and Cloudflare for site/network delivery, alongside the optional delivery and AI services described above. Data can be processed outside your country; Qwen identifies Singapore for its service. These providers’ privacy policies also describe their handling of service data. Network transport uses HTTPS; this is not a guarantee of absolute security or end-to-end encryption.

NouriMe is not intended for children or people under 18. If a minor’s data has been provided, contact us to request review and deletion. Privacy controls remain available when a profile does not meet the minimum age.

We publish updates at this URL with a new effective date. A material change to the remote-analysis disclosure requires a new in-app permission; an earlier permission does not automatically carry over. Contact us with any question.