Scope and operator
NAVU is for everyday planning and general wellness. It can help organize meals and practical steps around preferences, allergies, or a limit you supply, including an instruction from your healthcare professional. It must not derive a treatment target from a diagnosis, interpret medical records to decide care, diagnose, prescribe, or change medication. Nutrition figures are estimates. NAVU is not a medical device and does not diagnose, treat, cure, or prevent a medical condition. Consult a healthcare professional for medical advice, diagnosis, or treatment.
NAVU is operated by Joseph Cruz in Connecticut, United States. Contact joseph.devteam@gmail.com. This policy supplements our Privacy Notice for consumer health data under applicable laws, including Washington's My Health My Data Act and Nevada's consumer health data law. The current beta is intended for U.S. adults; a statement on this page does not enforce a geographic limit.
Health-data definitions vary. Washington may cover linked information identifying health status, including health inferences. Nevada's definition concerns linkable information NAVU uses to identify past, present, or future health status. An ordinary favorite cuisine, grocery item, budget, or place is not automatically health data. The details, purpose, and ability to link information to a person matter. A session or device identifier can create linkability without a name.
Categories and sources
You may voluntarily report an AI response in the app. Before sending, you can edit the selected response excerpt (up to 4,000 characters), choose a category, and optionally add details (up to 1,000 characters). We receive only that submitted content, your report-consent version, a random case ID, and creation/expiry times. Reports do not automatically attach conversation history, allergy settings, or pantry photos. The excerpt or details may contain health information if you choose to include it.
When present in a feature you request, the categories collected and processed may include:
- Allergies, intolerances, and exclusions that reveal a physical condition, provided in settings or conversation.
- Health conditions, symptoms, treatment, or health-related dietary needs you choose to include in prompts, relevant conversation history, selected pantry images, or support messages. NAVU does not ask you to provide a medical record.
- Health-related information in generated replies or ingredient interpretations when reasonably linkable to you, such as a reply taking account of an allergy. NAVU does not use these replies to diagnose you or create a health marketing profile.
Sources are you and the device content you deliberately submit, locally stored context you include in a request, and responses or ingredient interpretations generated by the AI services used to fulfill that request. We do not obtain medical records from healthcare providers, connect to banks or health wearables, or purchase health data for this beta. Typed location or image content can reveal a health-related place; this notice does not imply background GPS or health-facility geofencing.
Purposes and permission
Joseph Cruz reviews submitted reports to investigate harmful, offensive, or inaccurate responses and improve safety controls. Reporting requires a separate, explicit choice and remains available after you withdraw AI permission. A report is not a new AI request and is not used for model training, DataWheel, or shared meal learning. This is not an emergency service.
We use relevant information to answer the request you make, preserve allergy and exclusion constraints, recognize selected pantry ingredients, continue your cooking conversation, and support your private saves. If you send health information to support, we use it only as needed to address that message. Access for security, rights handling, and legal duties is limited to what the applicable law permits.
AI request processing and any required sensitive-data permission are separate from accepting Terms. We seek applicable permission before the relevant processing, including health details in free text or photos. Permission for a requested feature does not authorize optional health memory, training, shared-library retention, sale, or advertising. Secondary DataWheel collection remains disabled.
Where a law permits processing necessary to deliver the service you specifically request, that exception is limited to necessary processing. It does not automatically apply in every state or remove another state's consent requirement. NAVU must not use an exception for optional reuse. If processing is prohibited, permission cannot make it lawful.
Recipients and sharing
Provider settings are a separate question. NAVU has not yet verified that the credentials used by its running Gemini connection are linked to the required paid-service and data-sharing settings. We therefore do not promise that every provider excludes all beta content from model improvement. Provider verification is required before personal-data beta use. A request storage setting does not by itself establish zero retention or erase older records.
Submitted reports are stored in a restricted Firebase/Google Cloud collection for review by the operator. The report endpoint does not send report content to OpenAI or Gemini. Separate minimal security processing protects the endpoint from abuse.
Categories transmitted for your request are the relevant health-related prompt/context and settings, selected image content, and related generated replies described above. Google Firebase and Google Cloud provide backend and security infrastructure. OpenAI API services and Google Gemini Developer API services process requests, potentially including fallback processing. A provider can receive health details you include. Support messages travel through Gmail and your chosen email provider.
These are AI, cloud/security, and support-email recipient categories. Their legal role depends on the particular service and governing contract, not simply being called a vendor. Draft gate: NAVU must verify the applicable agreements, processor instructions, confidentiality, deletion assistance, and any provider uses outside its instructions before publication. No specific affiliate is identified in the current operator information; adding an affiliate requires review and updated disclosure.
NAVU does not sell consumer health data, share it for cross-context behavioral advertising, or use it for health-related marketing profiles. No advertising or cross-site health-tracking integration is present in the reviewed beta site. We do not authorize third parties to collect health data through NAVU over time and across unrelated websites or services for advertising or profiling. Provider security processing and its contractual limits must still be verified; this is not a claim about every independent activity of a provider.
Disclosure for a legally permitted safety or legal obligation is assessed against applicable health-data protections. The general Privacy Notice's business-transfer language does not grant permission to disregard these protections.
Retention and deletion
The proposed report record expires 30 days after submission. Database TTL deletion is asynchronous; expiry is not proof of immediate physical deletion. Deployment of TTL, access restrictions, and the operator review/deletion procedure must be verified before launch. Any legally required preservation must have a recorded reason and period.
Private local preferences, history, and meals are separate from server and provider processing. You can edit local settings, delete private recipes, and clear local NAVU data. If you include saved content in another AI request, it is processed for that request. Temporary DataWheel meal checks do not permanently publish candidates or write them into shared storage, shared caches, or candidate-content logs in shadow mode.
The data-category retention table describes local, server, provider, and historical records and identifies unresolved retention entries that block publication of this draft. Non-training commitments do not mean no provider retention. Turning on shadow mode does not erase older records. We must examine any identifiable historical records and follow through with relevant recipients for valid deletion requests. Local deletion alone does not do that.
Requests and withdrawal
Keep your case ID if you want to ask about or delete a report. Contact joseph.devteam@gmail.com; a case ID can help locate the record without resending sensitive content. Clearing local NAVU data or withdrawing AI permission does not delete a previously submitted report. NAVU must assess requests for identifiable external records.
Email joseph.devteam@gmail.com to ask about processing, obtain information, request correction or deletion, withdraw permission, or request that collection and sharing stop. Do not send full medical records or identity documents. You do not need to open an account or supply a legal name, phone number, or bank connection merely to exercise rights. We may ask for proportionate information to authenticate and locate the relevant record. We will explain any inability to link a local record and assist with available controls rather than automatically refusing all requests.
Use the app's privacy controls to withdraw AI or sensitive-data permission for future affected requests, or contact us for help. A personalized feature may be unable to proceed when it requires declined processing. Local features remain available where feasible. We do not silently drop an allergy restriction and recommend food as if it never existed. Withdrawal does not recall information already transmitted; deletion is a separate request that we will process under applicable law.
To appeal a refusal, email the same address, identify the decision, and say you want to appeal. No special form, account, or exact subject wording is required. We will give a written explanation. Exercising rights will not result in unlawful discrimination.
Washington rights
Where Washington law applies, you may confirm processing, access consumer health data, request a list of third parties and affiliates receiving your data with contact information, withdraw consent to collection and sharing, and request deletion. Requests generally receive a response within 45 days of receipt, with one additional 45-day period when legally justified and explained. Appeals receive a written decision within 45 days. You can complain to the Washington Attorney General.
We notify relevant recipients of a valid deletion request as required. A legally permitted delay for archived or backup copies may not exceed six months after authentication. That maximum is not NAVU's general retention schedule.
Nevada supplement
Nevada consumers may ask us to confirm collection, sharing, or sale; list third-party recipients; stop collection, sharing, or sale; and delete covered health data. To review or request changes, use local settings for device information or the contact method above for other identifiable records. We assess corrections available in the particular system.
Nevada generally allows 45 days after authentication to respond, with one justified additional 45-day period and notice. Its deletion rule separately requires deletion and notification to recipients within 30 days after authentication; recipients generally have 30 days after notification. An appeal receives a written response within 45 days. If denied, you may contact the Nevada Attorney General.
Nevada permits a limited backup/archive deletion delay of up to two years after authentication when the statutory conditions apply. We apply any stricter applicable duty, including Washington's shorter limit, and explain any actual exception. These different statutory maxima do not establish that NAVU or its providers keep backups for either period.
Changes and contact
We will publish an approved effective date and preserve version history. For material changes, we will provide a conspicuous notice through the site and applicable in-app channels before the changed processing and obtain any required permission. New categories, recipients, or purposes require review and any legally required notice and affirmative consent before use. A revised policy does not itself change an installed app's permissions.
Privacy requests, appeals, accessibility help, and questions: joseph.devteam@gmail.com. Operator: Joseph Cruz. Website: navu.life.