Privacy Policy

Last updated: August 22, 2026

MealTalk LLC ("MealTalk", "we", "us") makes a voice-first macro and calorie tracking app. This policy explains what we collect, how we use it, and the choices you have. We keep it short and plain on purpose.

Our guiding rule for your data is simple: we look at what our users say, never at who is saying it, except when you talk to us directly. In practice that means three things:

• Your log is yours. Your meals, weight, goals, and history belong to your account. They are not a feed we browse. The tools we use day to day do not show us who logged what, and reaching past them into an individual account is a deliberate step we take to answer a problem you raised or because the law requires it.
• The data that improves the product is de-identified. When we check a food's nutrition, we work from the phrase and the nutrition panel, not from your name. When we look at how the app is doing overall, we look at counts and distributions, never a list of named people.
• We connect data to you only when you started the conversation. Signing in, emailing us, or sending feedback from the app are all cases where we need to know who you are in order to answer you.

What we collect

• Your email address. We use it to sign you in with a one-time link and to contact you about your account.
• The meals you log. The foods, portions, and macros you record, plus any notes or corrections you make.
• What you say or type to log a meal. When you speak, your iPhone uses Apple's speech recognition to turn your voice into text. Depending on your device and language, Apple may process that audio on the device or on Apple's servers; that step is Apple's, under Apple's privacy policy. What reaches us is the resulting text, not an audio recording.
• Photos you take of food packaging. If you scan a nutrition label or a printed recipe, that image is sent to our AI provider to be read, and the extracted nutrition text is what we keep. We do not keep a copy of the photo, and we never open your photo library on our own.
• Weight and activity data you record. Your body weight entries and the goal and activity details you provide, and, if you choose to connect Apple Health, a daily summary of your activity. We use these to set and track your daily targets.
• Voice-and-parse improvement log, only if you opt in. If you accept the "Help us improve MealTalk" prompt, we save the text of what you said along with what our parser made of it, linked to your account, so we can find and fix wrong results. This is off unless you turn it on, and you can change it any time in Settings. Declining costs you nothing.
• Recipe links you share. If you import a recipe from a social media link, we receive that link and the recipe content we read from it. See "Who we share data with" for how link imports are processed.
• Basic usage and error data. Events like logging a meal, so we can keep the app working and improve accuracy. Crash and performance reports are collected without your account attached to them. We do not use any of this to track you across other apps or websites, and the app contains no advertising or analytics trackers.
• Creator attribution. If you use a creator link or recovery code, we keep the confirmed code, how it arrived, and when it was claimed. A web visit alone is not treated as an install or a confirmed claim.
• Install source. If you open MealTalk from a MealTalk website or campaign link, Apple's Smart App Banner, a creator link, or a friend invite, we keep the first channel we saw (for example website, Instagram, App Store, or a creator link) on your account. A visit to mealtalk.ai alone is not treated as an install. We do not use advertising pixels, third-party attribution SDKs, or cookies for this.
• Subscription and offer facts. Apple and RevenueCat provide purchase, renewal, refund, reversal, product, environment, and estimated transaction economics. We record whether an offer was present, but never store the raw Apple offer code or your Apple ID.
• User referral records. Your stable MealTalk invite code, whether a claim was made, privacy-safe progress states, referral notification choice, Apple product and transaction identifiers needed to verify eligibility, and referral audit events. We do not collect contacts, inspect your clipboard, fingerprint a device, or expose one participant's meals, plan, price, email, or identity to the other.

How we use it

• To identify the foods you mention and return their macros.
• To save your logs and show your daily totals.
• To improve our food database and the accuracy of our results.
• To diagnose crashes and fix problems.
• To send you sign-in links and important account messages.
• To confirm creator attribution, calculate and audit creator commission, handle refunds, reconcile Apple reporting, and provide subscription support.
• To understand which public pages and posts lead people to MealTalk.

Apple Health

Connecting Apple Health is optional and off until you turn it on. We read your weight, and, if you enable the exercise feature, your active energy, workouts, and step count, so we can show your trend and adjust your daily targets.

One thing worth being straight about: the permission sheet iOS shows also asks for permission to write calories and macros back to Apple Health. That is groundwork for a feature we have not shipped. MealTalk does not currently write anything to Apple Health. If that changes, we will say so here first. You can review or revoke any of this in the Health app at any time.

How your food entries improve MealTalk

When you log a food that is not yet in our database, the food name and related details may be added to an internal review list so we can add it and improve coverage for everyone. A founder reviews these entries, including the words you used and the nutrition information we found, to verify the food and add it to our database.

This review is not linked to your identity, and not merely as a matter of policy: the review list has no field for who submitted an entry, so there is nothing for a reviewer to look up. The reviewer sees the phrase and the nutrition panel. The list is used only to build our verified food database and is never shared publicly.

The same applies when you flag a result as wrong. The correction that reaches our food review queue carries the food and what went wrong, with no account attached to it.

How we look at the app overall

To understand whether MealTalk is working, we look at aggregates: how many people logged a meal today, how often a parse succeeds, which phrasings we handle badly. These are counts and distributions. Our internal dashboards deliberately do not produce a list of named users, and a per-person view that once existed was removed for that reason.

Two places do involve a person, both because you contacted us. When you send feedback or a bug report from the app, a founder is notified and can see your name and email, because feedback is a message to us and we may need to reply. Founders are also notified when someone signs up. Outside those, operational alerts about food logging identify testers only by a short code, not by name or email.

We should be equally clear about the limit of this: MealTalk is run by two founders with administrative access to the production database. We do not have a system that records each time a founder looks at an individual account, so we are not going to claim one. What we can tell you is how the tools are built, which is the part that actually constrains us day to day: the review and dashboard surfaces we use are the de-identified ones described above.

Who we share data with

We do not sell your personal data. We share limited data with service providers that help us operate MealTalk, and only so they can provide their service to us. Here is who they are and what actually reaches them:

• Supabase hosts our database, sign-in, and server code. Your account and your logs live here.
• AI providers that read your food descriptions. The text of what you logged, and a nutrition label photo when you scan one, is sent to be interpreted. This runs through OpenRouter (which routes to Anthropic's Claude models) and, for some requests, directly to Google (Gemini). We send the words and the food context. We do not send your name, your email, or your account identifier with them.
• Web search and page-reading providers used to find macros for foods not yet in our database: Exa, Firecrawl, and Tavily. These receive a food search query built from the food name, not your log and not your identity. We also read public nutrition sources such as USDA FoodData Central and Open Food Facts.
• Recipe imports. If you import a recipe from a social link, the link you share is sent to ScrapeCreators to retrieve the post and its caption, and to YouTube's API for YouTube links. When the caption is not enough, the video's audio is sent to OpenAI for transcription so we can read the recipe from the video itself.
• Sentry for crash and performance reports. We do not attach your account to these.
• Email delivery for your sign-in links.
• Apple and RevenueCat for App Store billing, redemption, receipt synchronization, subscription support, and transaction reporting. RevenueCat records purchases; it is not what unlocks the app.

These providers process this data to deliver their service to us, and each is governed by its own terms and privacy policy. Because what we send them carries no name, email, or account identifier, the food text they receive is not connected to you on their side.

Creators receive only aggregate reporting about links, confirmed claims, qualifying transactions, commissions, and payouts. We do not give creators the names, email addresses, account identifiers, meal data, Apple IDs, or individual purchase history of referred users. Creator relationships are paid partnerships and creators must disclose them as required by law.

We may also disclose data if required by law, or to protect the rights and safety of our users and MealTalk.

How long we keep it

We keep your account and your logs while your account is active. When you delete your account, most of your data is deleted outright. Some records are instead irreversibly disconnected from you rather than removed: parse and app telemetry rows have your account identifier stripped, and the food entries that improved our database stay in the database, since they never carried your identity in the first place. Deleting your MealTalk account does not cancel an App Store subscription, which only Apple can do.

When you delete your account, we also remove the links and customer snapshots that connect creator attribution and subscription transactions to your MealTalk identity. We retain a one-way fingerprint only to prevent a later billing webhook from recreating that link; the marker does not contain the original account identifier. We retain de-identified transaction facts, creator contracts, code history, commission adjustments, reconciliations, and payout records for seven years after the applicable payout year so we can meet tax, accounting, fraud, dispute, and audit obligations. Those retained records do not include meal data, Apple IDs, raw Apple offer codes, tax forms, or payout-account details.

Referral privacy, retention, and deletion

• Your invite code, notification choice, referral relationships, rewards, and RevenueCat transaction facts remain while your account is active. In-app account deletion removes the records where you are the subject. If the other participant keeps an account, their relationship state can remain with your identity removed so their support and reward history stays coherent.
• Referral audit events expire 25 months after creation. They contain state names and limited operational metadata, not raw invalid codes, raw Apple offer codes, names, email addresses, Apple IDs, full IP addresses, contacts, or meal data.
• Apple friend offer codes are encrypted at import and readable only by the protected server allocation path. The recoverable encrypted value is erased when the qualifying Apple purchase confirms redemption, when the code expires, or when support confirms it is invalid. A code's non-secret status record remains for reconciliation.
• Referral status notifications are off by default and require a separate choice inside the referral hub. Meal reminder and monthly recap choices do not enable them. Turning the referral choice off stops new referral status messages.
• A data export includes your own invite code and privacy-safe relationship and reward states. It never includes another person's identity, subscription plan, price, meals, or private dates.

Your choices

• Export. The in-app export gives you your meal log, weight history, current weight-goal plan, and your confirmed creator attribution and subscription records. It does not yet include everything we hold, such as your saved meals, custom foods and imported recipes, water log, or feedback you have sent us. If you want those too, email us and we will put them together for you.
• Deletion. You can delete your account from inside the app. That removes your logs, weights, goals, saved meals, custom foods, recipes, water log, feedback, device tokens, and improvement-log entries. A few records are kept in de-identified form rather than deleted, described in the next section.
• The improvement log. Turn the voice-and-parse improvement log on or off any time in Settings.
• Access and correction. Ask us to see or correct your personal data at any time.

Email hello@mealtalk.ai and we will help.

This website

mealtalk.ai runs no advertising pixels, third-party analytics, or tracking cookies. A small first-party script tags App Store links and Apple's Smart App Banner with a campaign name (website, Instagram, and so on) so the app can record how a new account arrived. It does not store a visitor id or follow you to other sites. If you previously joined our beta update list, we keep that email only for the update you requested. Ask us and we will remove it.

Security

We use reasonable measures to protect your data. Access to your rows is enforced by the database itself, using rules tied to your signed-in account, so another user cannot read your logs. Data is encrypted in transit. No method of storage or transmission is perfectly secure, but we work to keep your information safe.

Children

MealTalk is not directed to children under 13, and we do not knowingly collect data from them.

Contact

Questions about this policy, your data, or a referral? Email support@mealtalk.ai.