Privacy

What we store

Your name and email address, and whatever your household saves: recipes, meal plans, grocery lists, and who belongs to the household.

A recipe photograph is re-encoded when it is saved. That removes the information a phone attaches to a picture, including where it was taken. Photographs saved before this became the case keep whatever they already carried.

Who can see it

Only active members of your household, according to the role each was given. Not other households, and not visitors. My Meal Planning is a private household service, not a public recipe feed.

Emails we send

We send emails about your account, such as the link that confirms your email address and password reset links.

We also send emails that help you plan your meals. They go to household members who can plan meals. They help you get started after you sign up, and they remind you the day before your shopping day when next week has no meals planned. To decide which email to send, we check whether your household has saved recipes and planned meals. An email may include the name of your household's most recent recipe. You can stop these emails with the link at the bottom of each one or on your Profile page. Stopping them does not stop emails about your account.

We send all of these emails through Resend, an email delivery service. Resend receives your email address and the email itself.

Visits and use of the service

When first-party measurement is enabled, we use a random browser cookie to understand how visitors find My Meal Planning, start a household, plan meals, and return. We record selected public pages, times, recognized referring websites, and approved campaign labels. We also keep household signup attribution, the first observed use of a dated meal plan, and daily household-use counts. Operator reports show aggregate figures. We do not keep a permanent browser-identifier link to your household.

This measurement does not store IP addresses, raw browser headers, names, emails, or recipe, meal, and grocery content. It is not sent to a third-party analytics provider. We respect Do Not Track and Global Privacy Control signals by excluding measurement for those requests.

The browser cookie lasts up to 395 days. Confirmed visitor/session records expire after up to 395 days without new activity. Unconfirmed browser/session records expire after 24 hours. Public page-view records are kept for up to 90 days, and household activity days for up to 395 days. Signup attribution and the first observed planning timestamp remain until the household is purged. Household measurement data is included in the Owner's export and removed by verified household purge; backup copies follow the retention described below.

Advertising measurement

Separately from that first-party measurement, when advertising measurement is turned on, the public pages of this website, such as the home, pricing, and signup pages, load the Meta Pixel, a script provided by Meta Platforms. It tells Meta that one of those pages was viewed, so we can see whether our ads on Facebook and Instagram bring visitors to My Meal Planning.

Meta receives the address of the page, the page you came from, and the time, along with what any website receives from a browser, such as its IP address, browser type and version, screen size, language, and time zone. The Pixel stores its own cookie on this website (_fbp), and another (_fbc) when you arrive from a Meta ad, so Meta can recognize the browser on a later visit. Each lasts up to 90 days after your most recent visit. If your browser is signed in to Facebook or Instagram, Meta may connect the visit to that account. Meta uses this information under its own privacy policy, including to deliver and measure ads.

The Pixel does not run once you are signed in, so it is never on the pages that show your household’s recipes, meal plans, grocery lists, or settings. It does not run on the sign-in, password, invitation, or email-confirmation pages either. Meta is not sent your name, email address, recipes, meal plans, grocery lists, searches, dietary preferences or allergies, household details, recipe-help requests, or payment details. The only event we send is the page view, we add no details of our own to it, and we have switched off the Pixel’s automatic collection of button clicks and page content. Like our own measurement, the Pixel is not loaded when your browser sends a Do Not Track or Global Privacy Control signal. You can also block it with your browser’s privacy settings or a content blocker, and manage your ad preferences in your Meta account settings.

Payment

Subscriptions are handled by Stripe on their own secure pages. Card details never reach My Meal Planning and are never stored here.

Storage and backups

Our hosting provider stores the service database and files so My Meal Planning can operate, stay reliable, and recover from data loss. We use Cloudflare R2 for off-site storage of hosting backup archives. These archives include the service database and home-directory files. They can contain account and household details, recipes, meal-planning and grocery information, saved recipe images, and temporary photo-import files that are present when a backup is made. The application sends photo-import files to its recipe-reading service; it does not upload live recipe images or import photos directly to R2.

Cloudflare acts as a service provider and data processor for My Meal Planning LLC when it stores these backup archives and uses subprocessors under its applicable terms.

Recipe help

Recipe help is provided by OpenAI. When you ask for recipe help or recipe ideas, or bring in a recipe from a web page, a photograph, or pasted text, that content is sent to OpenAI to prepare the draft. Recipe ideas also send the dietary preferences and allergies your household has saved. Please do not submit material you do not have permission to share.

For the recipe help My Meal Planning provides, we allow OpenAI to use what is sent to develop and improve its models and services, including training them. If your household uses its own assistance key, that content goes to OpenAI under your own OpenAI account and its settings instead.

Bringing in a recipe from a web page is best effort. My Meal Planning does not work around a site’s access controls. A photo submitted for recipe reading is staged privately while its import is processed, and the application cleans up staged files after import. A temporary file or backup copy can remain until it is removed and the relevant backup expires.

Nutrition figures

Nutrition figures are worked out on our own servers from a copy of the U.S. Department of Agriculture’s FoodData Central data that comes with the service. Nothing about your recipes or your household is sent to USDA, to OpenAI, or to anyone else to work them out.

The figures, any numbers your household enters for a recipe, and the foods your household picks for its ingredients are stored with your household’s recipes. They are included in your household’s export and deleted with the household. Nutrition figures are estimates for general information, not medical or dietary advice.

Deleting a household

A household Owner can request deletion. The household remains recoverable for 30 days. After that, a separate verified purge can remove its content from the active service. A small deletion record remains so a restore cannot bring the household back.

Backups can still contain content after it has been removed from the active service. Current hosting backups are retained for about thirty days, so a deleted household may remain in a backup until that copy expires. Off-site backup archives in R2 are kept for thirty days, so they can also contain deleted content until the relevant archive expires. Deletion does not immediately remove content from every backup.

Requests

For a privacy or data request, write to legal@mymealplanning.com. You can also export or delete your household yourself, at any time, from your account settings.

You must be at least 13 years old to hold an account.

Who runs this

This service is operated by My Meal Planning LLC.