Skip to content
NAVU
HomePrivacy NoticeConsumer Health Data Privacy PolicyTerms

NAVU · 18+ · U.S.

How NAVU handles your information

PRELAUNCH INFORMATION — Proposed app-release notice: DRAFT. Updated September 2026. App-release effective date pending.

NAVU is being prepared for a U.S. beta for adults 18+. There is no public app-store release. The website is informational. The app provisions below describe the proposed coordinated release, except where current behavior is identified. Publishing this information or merging code does not activate app or backend changes.

An easy guide to the proposed app release: what stays private, what goes to providers, and what the recipe library does. Read the linked notices for the full categories, retention details, and rights.

EnglishEspañolPortuguês
On this page
  1. What is available now?
  2. Do I have to give my name?
  3. What is the recipe library?
  4. Does NAVU train AI models with my content?
  5. What happens to my requests and private saves?
  6. Can NAVU make medical decisions?
  7. How will reporting and deletion work?
  8. What does legal review mean?

What is available now?

Current release status: the backend now enforces AI permissions, disables shared feedback learning and shared reuse of generated recipes, and includes medical-decision safeguards and response controls for English, Spanish, and Portuguese. The mobile app is not publicly distributed. Using its updated permissions and reporting screens requires the corresponding app release. Provider verification, report-review and deletion procedures, and remaining launch checks must be completed before public beta use. Historical records and earlier app builds require separate assessment.

Do I have to give my name?

The proposed core app does not require an account or legal name. An optional display name is stored with local preferences and may accompany relevant AI requests. Names or other identifying details can also appear in messages, photos, saved recipes, support mail, or reports you choose to send. Technical identifiers and context may link information to a person. No required name does not mean anonymous use or no personal-data processing.

What is the recipe library?

NAVU has a curated recipe catalog shipped with the service. Curated means selected and structured for the product; it does not mean medically verified. Using that catalog, generating a response, keeping a private recipe, learning from user feedback, and training an AI model are different activities. The deployed backend disables shared user-feedback learning and reuse of generated recipes in the shared catalog. User-supplied context can still guide the answer you request. This is not training the underlying model.

Does NAVU train AI models with my content?

No NAVU model-training, fine-tuning, distillation, or training-export feature is part of the proposed release. This is a statement about NAVU’s use, not proof of every provider’s settings. OpenAI and Gemini process requests under their own applicable service terms. Their retention and optional sharing controls must be verified for the accounts actually used.

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.

What happens to my requests and private saves?

Relevant messages, recent context, preferences, allergy exclusions, an optional display name, and selected pantry photos may go through Firebase/Google Cloud to OpenAI or Gemini when an AI request needs them. Private conversation history, meals, favorites, and lists remain on the device in the reviewed app; content included in a later request can be transmitted again. Local storage and model-provider storage are separate. Clearing the app does not recall a request already sent or erase device backups automatically.

Can NAVU make medical decisions?

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.

How will reporting and deletion work?

The proposed report flow lets you edit an excerpt, choose a category, preview the exact content, and give separate permission for Joseph Cruz to review it through Firebase. It does not send the report to AI providers or enable AI permission. Reports have a proposed 30-day expiry, with asynchronous deletion and access controls still to verify before release. Keep the case ID for follow-up. For privacy requests, email joseph.devteam@gmail.com. A report is not an emergency channel and review is not immediate.

What does legal review mean?

Prelaunch, free access, no required name, and nonmedical branding do not remove privacy duties. Applicability depends on the information, purpose, location, and governing law. NAVU’s notices preserve applicable access, correction, deletion, withdrawal, and appeal rights. These pages are not a legal certification or a claim that every jurisdiction has been cleared. New uses require their own review and any required permission before activation.

Provider and safety sources

These explain provider rules and food safety; they do not verify NAVU’s account settings or certify the app.

  • OpenAI — API data controls
  • Google — Gemini API terms
  • Google — Gemini data logging and sharing
  • FDA — Food allergies
HomePrivacy NoticeConsumer Health Data Privacy PolicyTerms

© 2026 NAVU · Joseph Cruz · joseph.devteam@gmail.com

Back to top