Legal

Privacy Policy

Effective Date: March 15, 2026Last Updated: March 15, 2026

FRNTR, LLC | hello.food | privacy@frntr.ai

Return to hello.food

Introduction

hello.food is a product of FRNTR, LLC, a California limited liability company ("FRNTR," "Company," "we," "our," or "us"). hello.food operates a voice-first restaurant intelligence platform that provides structured, contextual menu information to consumers and restaurant owners, and distributes that information to AI systems and other digital platforms.

This Privacy Policy describes how we collect, use, store, protect, and share information about:

  • Consumers who use the hello.food mobile application (iOS) and associated services;
  • Restaurant owners and operators who use the hello.food Owner Portal and menu management system; and
  • Visitors to our websites, including hello.food and frntr.ai.

By using our Services, you acknowledge that you have read and understood this Privacy Policy. If you do not agree to the terms of this Privacy Policy, please do not use our Services.

For our general company privacy policy covering the FRNTR, LLC corporate website, please visit frntr.ai/privacy.

Definitions

Services
The hello.food mobile application, the hello.food Owner Portal, our websites, our AI distribution infrastructure including MCP server integrations, and all associated features and functionality.
Consumer or User
Any individual who downloads or uses the hello.food mobile application for personal dietary guidance, restaurant discovery, or food decision support.
Restaurant Owner or Owner
Any restaurant operator, manager, or their authorized representative who uses the hello.food Owner Portal to manage menu data.
Dietary Graph
The structured representation of a User's dietary profile, including preferences, restrictions, allergies, aversions, health conditions relevant to diet, and related context, as established and maintained by the User within the app.
Menu Data
Structured information about a restaurant's menu items, ingredients, preparation methods, pricing, and related kitchen context.
Agentic Channels
Third-party AI platforms and services, including but not limited to ChatGPT, Google Gemini, and Claude by Anthropic, to which hello.food distributes structured restaurant and dietary context through MCP server infrastructure and related integrations.

Who This Policy Covers

A. Consumer Users

This policy governs data we collect from individuals who use the hello.food iOS application to receive dietary guidance, discover restaurants, evaluate menu items, plan meals, and interact with their dietary profile. This includes use of voice input, food vision scanning, Apple Health integration, Apple Watch companion, Oura Ring integration, Function Health integration, meal planning, recipe optimization, and AI-powered dietary evaluation.

B. Restaurant Owners and Operators

This policy governs data we collect from restaurants and their representatives who use the hello.food Owner Portal to submit, verify, and manage menu data. This includes email-based menu submissions, web portal uploads, and participation in our tiered KYC verification program.

Information We Collect

A. From Consumers

1. Account and Profile Information

When you create a hello.food account, we may collect:

  • Email address and account credentials;
  • Name, if you choose to provide it;
  • General location or region for restaurant discovery; and
  • Age or date of birth to verify minimum age requirements.

2. Dietary Profile and Dietary Graph

Your Dietary Graph is the core of the hello.food experience. This is sensitive personal information and we treat it accordingly. Your Dietary Graph may include:

  • Dietary restrictions, allergies, and intolerances such as gluten-free, nut allergies, or shellfish allergies;
  • Religious or ethical dietary practices such as halal, kosher, or vegan;
  • Personal preferences, aversions, and taste preferences;
  • Health-related dietary context such as low-sodium or diabetic-friendly needs;
  • Macronutrient goals and caloric targets; and
  • Meal history and dietary patterns tracked within the app.

Storage of Your Dietary Graph: By default, your Dietary Graph is stored exclusively on your device using encrypted local storage with Hive local storage and flutter_secure_storage. We do not transfer your raw Dietary Graph to our servers unless you explicitly opt into cloud sync. Even when cloud sync is enabled, your data is transmitted over encrypted connections.

3. Health and Wearable Device Data

With your explicit permission, hello.food may access health and fitness data from connected services and devices:

  • Apple Health (HealthKit): We may request access to relevant HealthKit data types you authorize, including activity data, nutritional information, body measurements, and sleep data. HealthKit data is governed by Apple's terms and privacy policy. We do not use HealthKit data for advertising and we do not share it with third parties for marketing purposes. You may revoke HealthKit access at any time through iPhone Settings > Health > Data Access & Devices.
  • Apple Watch: The hello.food Apple Watch companion app may display dietary context and receive voice input. Data exchanged with the Apple Watch is governed by the same protections as the iOS app.
  • Oura Ring: If you connect your Oura Ring, we may receive sleep, activity, and recovery data you authorize through the Oura API. Your use of Oura services is also governed by Oura's privacy policy.
  • Function Health: If you connect your Function Health account, we may receive biomarker and health data you authorize. Your use of Function services is also governed by Function's privacy policy.

You are never required to connect any third-party health service. All integrations require your explicit consent and can be disconnected at any time from within the app.

4. Food Vision and Camera Data

With your permission, the app uses your device camera for food recognition features. Images captured for food recognition are processed on-device or transmitted to our backend for analysis and are not stored or used for any purpose other than the immediate food identification request. We do not maintain a database of user food images.

5. Voice Data

hello.food is a voice-first application. Voice input is converted to text for processing. Audio recordings are not retained after transcription. Transcribed text may be used to fulfill your request and improve voice recognition accuracy.

6. Usage and Technical Data

We collect standard technical information to operate and improve the Services:

  • Device type, operating system version, and app version;
  • IP address and approximate location at the city or region level;
  • Feature usage patterns and session data;
  • Crash reports and performance diagnostics; and
  • Feature flag states and A/B test participation.

B. From Restaurant Owners

1. Business and Contact Information

When you register as a restaurant owner, we collect:

  • Restaurant name, address, and contact information;
  • Authorized representative name and email address; and
  • Business documentation submitted for KYC verification in Tier 1 and Tier 2.

2. Menu Data and Submitted Documents

We collect Menu Data you submit through our Owner Portal, including:

  • Menu items, descriptions, pricing, and ingredient information;
  • Documents submitted via email or web portal upload, including PDF, DOCX, images, plain text, and CSV; and
  • Kitchen context, preparation methods, and allergen information.

All submitted documents are scanned for malware using ClamAV prior to processing. Documents are parsed in sandboxed, network-isolated environments. File type and integrity are validated before processing. We treat submitted menus as your confidential business information.

3. Portal Usage Data

We collect standard web analytics associated with your use of the Owner Portal, including login timestamps, upload activity, and verification status.

C. System-Collected Restaurant Data

In addition to owner-submitted data, we operate an automated Menu Hunter system that discovers and collects publicly available menu information from restaurant websites, third-party platforms, and publicly accessible documents. This system operates within applicable legal frameworks governing publicly available web data. We do not scrape data from password-protected or access-restricted systems.

How We Use Your Information

A. Consumer Data

  • To operate the hello.food app and deliver personalized dietary guidance and restaurant recommendations;
  • To evaluate menu items and restaurants against your Dietary Graph and produce safety verdicts;
  • To power voice-first interaction, food recognition, and meal planning features;
  • To sync data with connected health services you have authorized;
  • To improve the accuracy of our dietary evaluation models;
  • To communicate with you about your account, features, and service updates;
  • To detect and prevent fraud, abuse, and security incidents; and
  • To comply with applicable law.

B. Restaurant Owner Data

  • To operate and manage the Owner Portal and menu management system;
  • To publish your Menu Data to the hello.food platform and to authorized AI distribution channels;
  • To verify your identity and business through our KYC process;
  • To communicate with you about your portal account and menu status;
  • To provide audit trails for all menu publication operations; and
  • To comply with applicable law.

AI Distribution, MCP Integration, and the Claims Gateway

hello.food distributes structured restaurant data to Agentic Channels, including ChatGPT, Google Gemini, Claude, Perplexity, and others, through our Model Context Protocol server infrastructure and related API integrations.

A. What We Share with Agentic Channels

When you use hello.food through an Agentic Channel, we may share:

  • Structured restaurant and menu data relevant to your query; and
  • Privacy-preserving dietary attestations.

We do not share your raw Dietary Graph with any Agentic Channel. We do not share your Apple Health data, Oura Ring data, Function Health data, or other raw health data with Agentic Channels.

B. Privacy-Preserving Claims Gateway

To enable personalized dietary guidance through Agentic Channels without exposing your sensitive dietary data, hello.food uses a Claims Gateway. The Claims Gateway generates signed attestations, cryptographic statements that confirm relevant dietary facts such as "this user avoids gluten" without disclosing the underlying data or your full Dietary Graph.

These attestations are derived from your on-device Dietary Graph and are transmitted as signed claims. Your raw dietary data never leaves our trusted backend infrastructure in an identifiable form in connection with Agentic Channel requests.

C. Zero-Knowledge Proof Methods (Planned)

hello.food intends to implement zero-knowledge proof cryptographic methods for sharing dietary context with foundation model partners. This will provide mathematical guarantees that dietary context can be verified without revealing the underlying data. We will update this Privacy Policy when this capability is deployed.

D. OAuth 2.0 Account Linking

When you link your hello.food account to an Agentic Channel such as ChatGPT or Claude, we use OAuth 2.0 to establish a secure, revocable authorization. You may disconnect any Agentic Channel at any time from within your hello.food account settings.

How We Share Your Information

We do not sell your personal information. We do not rent your personal information. We do not share your Dietary Graph or health data with advertisers.

A. Service Providers

We may share information with trusted third-party service providers who assist us in operating our Services, subject to contractual data protection obligations. These include:

  • Cloud infrastructure providers such as Render;
  • Database and caching infrastructure;
  • Email service providers such as Resend for transactional communications;
  • LLM providers including OpenAI, Anthropic, and Google for dietary evaluation and menu extraction processing, acting on our behalf under their respective data processing agreements; and
  • Menu extraction and web crawling service providers such as Firecrawl.

B. Agentic Channel Partners

As described in the AI Distribution section above, we share structured restaurant data and privacy-preserving dietary attestations with Agentic Channels you connect to. We do not share raw personal data.

C. Legal and Compliance

We may disclose information when required by law, legal process, or government request; to protect the rights, property, or safety of hello.food, our users, or the public; or to enforce our Terms and Conditions.

D. Business Transfers

If FRNTR, LLC is involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will notify you of any such change in ownership or control of your personal information.

Data Retention

We retain your information for as long as your account is active or as needed to provide Services, comply with legal obligations, resolve disputes, and enforce agreements. Specific retention periods include:

  • On-device Dietary Graph is retained on your device until you delete the app or clear app data. If cloud sync is enabled, we retain your Dietary Graph until you delete your account;
  • Consumer account data is retained until you request deletion;
  • Restaurant Owner data and menu snapshots are retained for the duration of your portal account plus a reasonable period for audit trail purposes;
  • Voice transcriptions are not retained after request fulfillment;
  • Food images are not retained after food recognition processing; and
  • Audit logs are retained for a minimum of 12 months for compliance purposes.

You may request deletion of your data at any time by contacting privacy@frntr.ai or through the account deletion feature within the app.

Your Rights

A. California Residents (CCPA/CPRA)

California residents have the right to:

  • Know what personal information we collect, use, disclose, and sell;
  • Delete personal information we hold about you, subject to certain exceptions;
  • Opt out of the sale or sharing of personal information. We do not sell personal information;
  • Correct inaccurate personal information;
  • Limit use of sensitive personal information; and
  • Non-discrimination for exercising your privacy rights.

As a California-based company conducting our launch in the Fresno and Central Valley markets, we are committed to full CCPA and CPRA compliance. To exercise your rights, contact privacy@frntr.ai.

B. All Users

Regardless of location, all hello.food users may:

  • Access or update your account information through the app;
  • Disconnect third-party health integrations at any time;
  • Revoke Agentic Channel connections at any time;
  • Request a copy of your personal information; and
  • Request deletion of your account and associated data.

C. Apple HealthKit Rights

HealthKit data permissions are managed by Apple. You may view and revoke app permissions at any time through Settings > Health > Data Access & Devices on your iPhone. Revoking HealthKit permissions does not affect data stored locally on your device by the Health app.

Security

We take the security of your information seriously and implement multiple layers of protection:

  • On-device dietary profile encryption using flutter_secure_storage;
  • Encrypted transmission of all data between the app and our backend using TLS;
  • Sandboxed document parsing with complete network isolation for owner-submitted menus;
  • ClamAV malware scanning of all owner-submitted documents prior to parsing;
  • Magic-byte file validation and file type allowlists for uploaded documents;
  • Redacted audit logs that capture evaluation metadata without exposing raw dietary data;
  • Feature flag infrastructure for rapid response to security incidents; and
  • Multi-provider LLM abstraction with automatic fallback to maintain service integrity.

No method of transmission over the Internet or electronic storage is 100 percent secure. While we strive to use commercially acceptable means to protect your personal information, we cannot guarantee absolute security.

Children's Privacy

hello.food is not directed to children under 13 years of age. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided us with personal information, please contact privacy@frntr.ai and we will delete such information promptly.

Users must be at least 13 years of age to use hello.food. Users under 18 should use hello.food with parental guidance.

Apple HealthKit - Specific Disclosures

Per Apple's requirements for applications that integrate with HealthKit, we make the following explicit disclosures:

  • hello.food does not use HealthKit data for advertising or marketing purposes.
  • hello.food does not share HealthKit data with third parties for advertising or marketing purposes.
  • HealthKit data is not used to train our dietary evaluation models unless you provide explicit, separate consent for such use.
  • All HealthKit data access requires your explicit permission, granted through the standard iOS HealthKit permission dialog.
  • You may revoke HealthKit access at any time through your iOS device settings.

Restaurant Menu Data - Special Disclosures

A. Owner-Submitted Menu Data

Menu Data submitted by verified restaurant owners through the Owner Portal is treated as proprietary business information. We publish this data to the hello.food platform and to authorized AI distribution channels in accordance with our Terms and Conditions. We do not sell owner-submitted Menu Data to third-party data brokers.

B. System-Collected Menu Data

Our Menu Hunter system collects publicly available menu information from restaurant websites and public sources. If you are a restaurant owner and wish to opt out of our system-collected menu data or claim ownership of your restaurant's menu representation, please contact restaurants@frntr.ai.

C. Deterministic Precedence

Our system applies a deterministic precedence hierarchy to all menu data: owner-verified data always takes priority over owner-provisional data, which takes priority over system-collected data. This means verified restaurant owners always control their menu representation on our platform.

Third-Party Services and Links

Our Services may contain links to or integrate with third-party services, websites, and applications. This Privacy Policy does not apply to those third-party services. We encourage you to review the privacy policies of any third-party services you use in connection with hello.food, including:

Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the new Privacy Policy on our website and within the app, and by sending you an email notification if we have your email address on file. The effective date at the top of this Policy will be updated accordingly.

Your continued use of our Services after the effective date of the revised Privacy Policy constitutes your acceptance of the changes. If you do not agree to the revised Privacy Policy, you must stop using the Services.

Contact Us

If you have questions about this Privacy Policy, our data practices, or wish to exercise your privacy rights, please contact us:

FRNTR, LLC - hello.food Privacy

Email: privacy@frntr.ai

General Inquiries: hi@frntr.ai

Restaurant Owners: restaurants@frntr.ai

We will respond to verifiable consumer requests within 45 days as required by applicable law, or as otherwise required by law.