Privacy Policy

Live Better AI (“we”, “us”, “our”) is committed to protecting your privacy. This policy explains what we collect, why, and who we share it with. Live Better AI is operated by CMB AI LLC.

Information we collect

To build and personalize your meal plans, we collect:

• Account details. Your name and email address. If you sign in with Apple or Google, they share your name and email with us; Apple lets you hide your real address behind a private relay address, and that works here.
• Meal-planning profile. The answers you give during setup: household size and members, cooking preferences, budget, and your food preferences and dietary restrictions and allergies. Allergen information is health-adjacent and we treat it with care; it is used only to keep unsafe ingredients out of your plans.
• Body statistics and goals. If you provide them, figures such as height, weight, activity level, and calorie or weight goals, used to size your plans, and any weigh-ins you log.
• Household members. An adult account holder may add children to a household plan, including their ages and food needs. Children do not need accounts, and the service is not directed to children under 13.
• Images you upload. Photos of a fridge, a receipt, or a recipe you import. These are processed to extract items or recipe details.
• Usage data. Your plans, saved recipes, swipes, and inventory, so the product can remember your taste and pantry.
• Recipe ratings. When you rate a recipe from 1 to 5 stars, we keep your rating with your account and use it to tune your suggestions. Once enough members have rated a recipe, we show everyone its average and the number of ratings. Your name and account are never shown with it.
• Feedback on your grocery orders. If you tell us an Instacart order did not come together, we save your answer and the grocery items you pick, with the order it was about, so we can fix how we build lists. If you tell us how the amounts on a grocery list landed (too much, about right, or too little), or that you did not shop that list, we save that answer too, with the grocery items you rate and the list it was about. Only you and our team can see it.
• Push notification token. If you turn on meal plan notifications in the mobile app, we store an app-specific token and an installation identifier with your account so a notification can reach that device, and a record of when we sent each notification, kept for 90 days, which we use to limit how often we send them. We use them for notifications, not advertising.

Some of this, such as allergies, health-related diet settings like Diabetic-friendly, body measurements, weight goals and weigh-ins, is consumer health data under some state laws. Our Consumer Health Data Privacy Policy explains how we handle it and how to use your rights.

If you ask us to make a photo for one of your own recipes, we send that recipe’s name and its ingredient list to our image provider. We do not send your name, your email address or any other personal information. If you choose your own recipe photo, we store it privately to display with that recipe until you remove it or delete your account, and we never show it to anyone else unless you choose to share it. We do not send your own recipe photo to the image provider.

Before you create an account

You can set up your first week, and swipe a short deck of recipes, before an account exists. Your household, goal and food-preference answers, including which recipes you chose, stay on your device until you create an account or choose to use Live Better AI without one. During that recipe deck, our servers deliver the recipes and PostHog product analytics, when enabled, records each calibration swipe choice (love, save or skip) and the total number of swipes, without the recipe ID or title. Those app analytics events may be associated with your account if you later sign up or use Live Better AI without an account. If you look up a grocery store, we pass the ZIP code you type to Instacart to list nearby stores. If you neither sign up nor use Live Better AI without an account, we do not turn your setup answers into a meal-planning profile.

Using Live Better AI without an account

You can skip creating an account. When you do, we create a random guest ID for your phone on our servers, so your setup answers, swipes, weeks, grocery lists, imported recipes and Instacart list links work the way they do for members. A guest has no email address or password. Guest data is tied to that phone: if you delete the app, reset the phone or delete your guest data, we cannot bring it back. You can save your account at any time in Settings with Apple, Google or email, and everything stays as it is. You can delete your guest data at any time in Settings. If a guest ID is not used for 90 days, we delete it and its data. Everything else in this policy, including our Consumer Health Data Policy, applies to guest use.

How we use your information

We use your information to build and personalize meal plans and grocery lists, remember your taste and pantry, and communicate with you about your account. We do not sell your personal information.

Meal plan notifications are optional. The app asks before requesting notification permission. If you allow them, we send your push token to Expo, which passes each notification to Apple or Google for delivery, depending on your device. You can turn them off in the app's Notifications settings. Turning them off or deleting your account removes stored tokens. Signing out in Settings unregisters that device. Cook-timer alerts stay on your device and do not use this token.

Who we share it with

To deliver the service we share data with a small set of processors:

• Past purchases. Live Better AI is free to use and sells nothing. If you bought a subscription on our website before it became free, our payment processor, Stripe, handled the payment. We never see or store your full card number. We keep what Stripe gave us so we can honor that subscription and keep payment records.
• AI providers. Meal plans are assembled from our recipe library without calling an AI provider. When you choose a feature that reads a fridge, receipt or recipe photo, or imports pasted recipe text, that content goes to Anthropic for extraction. Social video audio goes to OpenAI for transcription; extracted social text may then go to Anthropic to identify a recipe. Ingredient names may go to Anthropic’s Claude Haiku to make a shopping list clearer. If you request a generated photograph for a recipe saved in your account, OpenAI receives its title and ingredient names along with our house style reference photos. Anthropic checks the saved recipe title and ingredients before generation and checks the generated image with the recipe title afterward. We do not send your account name or email with these requests. Other AI features may send the text you give them to our AI providers.
• Recipe providers. Recipes are served from our own library. When you import a recipe by link, our servers fetch that page and may use the source site’s public metadata service, including Meta’s oEmbed service for Instagram or Facebook links. Your account details are not sent with that request. Spoonacular supplied recipes in our library.
• Grocery export. When you send a grocery list to Instacart, the list items you choose are shared so the cart can be built. We send the list or recipe title, ingredient names, quantities and units, and, when available, a recipe image, cooking time and a link back to our site. A chosen store key may be added to a recipe link. Shopping-list links are used exactly as Instacart provides them. We do not add your account name or email. Instacart adds its own affiliate campaign information to the shopping link so an order may earn us a commission (see our Terms). We do not add your account ID or a share reference to new links. Older links may carry an account identifier until they expire. On our servers, we record the link, when it was prepared and opened, and which account or shared recipe it came from. Impact.com, our affiliate provider, may report the referral time, type and source, order value, and commission. We compare the referral time with our link records to estimate which visit led to an order; a time match alone cannot prove who placed it.
• Calendar subscription. If you choose Keep my calendar in sync, we make a private link for your account. Your calendar app, such as Apple Calendar or Google Calendar, fetches your planned meal names, days, times and recipe links from it, and anyone with the link can see them. Reset the link to turn the old one off.
• Infrastructure. Data is stored with our hosting and database providers under their security controls. Supabase and Amazon Web Services (AWS) host our database, sign-in service and file storage, and process that data on our behalf. Vercel runs our website and the servers behind the app, so the data you send us passes through it. Resend delivers account and service emails for us.
• Notification delivery. If you enable meal plan notifications, Expo and Apple or Google receive the token and notification content needed to deliver them to your device.

Every company we share your data with, including the service providers above and the advertising and analytics partners described below, is required to give it the same or equal protection as this policy.

We also disclose information when valid legal process, such as a subpoena or court order, requires it, as described on our Security page. A court, an agency or another party that receives information this way is not one of our partners, and the promise above does not bind it.

Connected Pinterest account

If you choose to connect Pinterest, we ask Pinterest for permission to read your account, boards and saved Pins. We read only your own public boards, and you select which of them to import. We read Pin links from those boards to find recipes, and store the imported recipes in your account with a credit to Pinterest and to the recipe's creator. For each Pin we read, we keep only its link and the link to its recipe (also for a Pin that did not import, so you can see why), with a one-way code for the board it came from, never the board's name. We never store Pinterest images, Pin titles or Pin descriptions. We never send anything from Pinterest to advertising partners. We keep encrypted connection tokens so an import can finish and your connection can stay active. While an import or a check is running, we also keep the numbers of the boards it reads and its place in them, encrypted, until it finishes.

If you keep a board updated, we check it for new Pins about once a day and import the recipes they link to. We also check when you open our Pinterest page or your saved recipes in the app or on our website, if the last check was more than 6 hours ago, and when you use Sync now in the app or Sync new Pins on our website. To do this we keep an encrypted list of your boards: each board you keep updated or turned off, with when its Pins last changed, its Pin count and when we last checked it, and your other boards, including the ones we offered you and the ones you said no to, so we never ask about a board twice. The list holds board numbers only, never board names, and is deleted when you disconnect.

You can turn updates off for any board, or disconnect Pinterest at any time. Disconnecting ends our access at once. Within 30 days we delete the recipes Pinterest brought into your account, every Pinterest credit and the Pin links we kept. A recipe that was already in your account before you added it from Pinterest stays, without its Pinterest credit.

Cookies and advertising

We use the Meta (Facebook) Pixel, the Pinterest Tag, Google Ads conversion tags and PostHog product analytics to understand how Live Better AI is used and to measure how our advertising performs. These load when the applicable consent setting allows them.

Meta, Pinterest and Google may use what their tags and our events tell them to measure ads, and to target and deliver ads, including ads on their own services and on other websites and apps. This means they can collect information about your activity on our website over time and across different websites. PostHog is not used for advertising.

You can turn them off at any time: choose Cookie settings in the footer of any page and select “Decline.” We remember that choice on your device, and while it is set, no advertising or analytics cookies are written and the Meta Pixel, Pinterest Tag and Google Ads tag are not loaded. You can change your mind again from the same place.

You can also limit ads based on your activity: use the Digital Advertising Alliance’s opt-out at optout.aboutads.info, the ad settings in your Meta account (Accounts Center, then Ad preferences) and in your Pinterest account (Settings, then Privacy and data), and your phone’s settings. On an iPhone, go to Settings, then Privacy & Security, then Tracking. On Android, use your device’s Google ad settings, or turn off Share app events with Meta in our app’s Settings.

Do Not Track and Global Privacy Control. Some browsers send a Do Not Track signal. There is no common standard for it, so our website does not change what it does when it receives one. Our website does not yet treat a Global Privacy Control signal as a choice to decline. To turn off advertising and analytics tags, use Cookie settings as described above.

If you are visiting from the European Economic Area, the United Kingdom, or Switzerland, we ask first: nothing loads until you choose “Accept” on the banner. We do the same whenever we cannot tell where a visit is coming from.

In the United States and other places outside those regions, these tags and analytics load when you visit unless you already declined in Cookie settings.

Some conversion events are also sent from our servers, not just from your browser: to Meta, a signup, a week you build, a recipe you open or save, and a grocery list you open; to Pinterest, a signup and a grocery list you open. They never say which recipe it was. These server events honor the same consent choice: if you declined cookies, nothing is sent. Identifying fields such as your email and account ID are hashed before they leave, per each platform’s specification. The events may also include your IP address and browser or app user agent. An Instacart handoff event may include the number of items sent to the cart, but not their names, quantities or your dietary settings.

On the website, if Google Ads conversion tracking is configured and your consent allows it, a signup may also send Google a conversion event. An email used for matching is normalized and hashed before it is sent. We do not send Google your meal plan or grocery items.

In the iPhone app, Meta’s app SDK runs on every install. Until you tap Allow on Apple’s tracking prompt, it runs with advertiser tracking off and does not read your advertising identifier. It sends Meta app events (opening the app, creating your account, and opening a grocery list) with device and app details, which Meta uses for aggregated ad measurement through Apple’s SKAdNetwork. If you tap Allow, it may also send your advertising identifier and a hashed email for matching. Earlier versions of the app, after you tap Allow, send your raw device advertising identifier, when available, to our server for Meta app events, and Meta may receive it together with your device model, operating system version, app version, locale, time zone, screen size and density. After you tap Allow, we send a hashed copy of your advertising identifier to Pinterest; Pinterest may also receive your IP address and app user agent for an Instacart handoff. We may send Meta and Pinterest a hashed email or account ID for matching. For an Instacart handoff, Pinterest may receive the item count, but not item names, quantities or your dietary settings. If you tap Ask App Not to Track, the app never reads your advertising identifier, nothing is sent to Pinterest from the app, and we remove any stored advertising identifier and device context; Meta’s SDK keeps advertiser tracking off. If you withdraw permission later in iOS Settings, the app turns advertiser tracking off and clears that stored context the next time you open it. The app still works.

In the Android app, you can choose Share app events with Meta in Settings. It is off by default. If you turn it on, the app tells Meta, through Meta’s app SDK, when you create your account and when you open a grocery list. It sends no subscription events. Meta may receive ordinary app, device, and network details needed to process those events. We do not send your recipes, meal plans, grocery items, dietary settings or account ID with them, and the Android app does not collect the Advertising ID. Turning the setting off stops future Meta app events. The meal planner still works.

Data shared with Meta or Pinterest this way is also governed by their own privacy policies.

Product analytics

We use PostHog, a product-analytics service, to understand how Live Better AI is used in our app and on our website: events such as screens viewed, recipes swiped, and plans built. These events are tied to a pseudonymous user ID. We do not send diet modes, medical or weight goals, religious food settings, allergies or body measurements as person properties. This is first-party analytics run under our own account: it is not used for advertising, it does not track you across other apps or websites, and we do not sell or share this data with data brokers.

AI assistants you connect

You can connect Live Better AI to an AI assistant that supports our connector, so the assistant can help you plan meals and shop. To connect, you sign in to Live Better AI and approve the assistant on our approval page. That page names the assistant and its maker, lists what it can see and do, and links its privacy policy.

• What it can see. Depending on the assistant, your meal plans, saved recipes, grocery lists and pantry, and for some assistants the names of the people in your household, who is a child, and foods they dislike. Meal plans can reveal health information, such as a diet you follow. For recipes you imported from other websites, it sees only the title and links.
• What stays with us. Your allergies and other food restrictions, diet settings, health and weight goals, ages, height, weight and activity level. We use them to screen recipes for you and never send them to an assistant.
• What it can do. Depending on the assistant, search our recipes and suggest meals, build a week or swap a meal, change your grocery list, pantry or household, save or import recipes, and make Instacart shopping-list links for you to open. It never places an order or pays for anything. Some assistants let you allow changes without asking each time. When you approve an assistant you can choose Read only instead of Full access: it can then see what is listed above, but cannot change anything or make Instacart links with your account. You can switch at any time in Settings, then Connected apps.
• After it has your data. The assistant’s maker’s privacy policy covers what happens to it.
• What we keep. A log of what each connected assistant asked for: which tool, which assistant, whether it worked and when, never what was said or what came back. We keep it for 13 months. We send no advertising events about your use of an assistant.
• Without an account. If you use the connector without connecting an account, what you ask for, including foods to avoid, is used for that answer only and is not tied to you. We may keep the answer for up to an hour under a one-way code, so the same question is answered faster.

To disconnect, go to Settings, then Connected apps, on our website and choose Disconnect. Removing the connector inside the assistant alone may not end its access, so disconnect with us too. We also disconnect an assistant you have not used for 90 days.

Data storage and security

Your data is stored securely and access is restricted. Each account can only see its own data. We keep your information while your account is open, or as needed to provide the service and meet legal obligations. When you delete something, or delete your account, it leaves our live database right away. Copies in our backups are deleted automatically: database backups after 7 days, and earlier versions of stored files, such as photos, after 30 days. After our move to new servers in October 2026, we keep a standby copy of our old database for up to 14 days, and then delete it. Some records are kept longer, as described under Your rights. If the law requires us to keep something longer, for example under a court order or a legal hold, we keep only what it covers, only for as long as it requires, and then delete it.

Your rights

You can access, correct, or delete your personal data at any time. Account deletion is available in your settings and on our account deletion page, and you can also contact us at support@livebetterai.com. Deleting your account removes your profile, plans, uploaded content and public-week shares. We retain payment and affiliate records for accounting with their account links removed. When you delete your account, we keep a keyed, one-way fingerprint of your email address, not the address itself. We use it only to recognize a returning address, so a recreated account is not treated as a new sign-up (for example, it does not get the welcome email again). It cannot be turned back into your email.

After account deletion, we keep an anonymous record that a purchase was reported to Meta, with nothing in that record linking it to you.

Changes to this policy

We may update this policy. We post the new version here and change the date at the top. Before a material change takes effect, we tell members by email or with a notice in the app or on our website.

Contact us

Questions about this Privacy Policy? Contact us at support@livebetterai.com, or write to CMB AI LLC (Live Better AI), P.O. Box 540562, Houston, TX 77254.