Privacy policy

What Feast Planner keeps

• Your Google account basics. When you sign in with Google, Feast Planner gets your name, email address, Google account ID and profile photo, and keeps them with when you last signed in.
• What you add. Your recipes, with their ingredients, steps, tags, times, servings, calories and links, and the photos you add to them; the recipes you save; drafts of recipes the extension added that are missing something; your meal plan and the meals you’ve cooked; and your shopping list, with the things you add to it and what you’ve checked off.
• How many pages and photos AI read for you each day, to keep to a daily limit.
• When you added each photo, and its size, to keep to the limits on photos. This is kept after the photo is deleted.
• Your household, if you make or join one: its name, who’s in it and who owns it, and the invitations it has sent, with the email address, who sent it and when; and its meal plan, the meals it’s cooked and its shopping list.
• When you sent each invitation, without the address, to keep to the limit on invitations a day. This is kept for a day, even after you leave the household or it’s deleted.
• The devices you’ve turned notifications on for: the address your browser’s push service gave each one for Feast Planner’s notifications, the keys to encrypt them with, and when you turned them on, or last opened the Household page on it.

It’s used only to run Feast Planner for you: to show your recipes, plan your meals, make your shopping list, read recipes from the pages and photos you give it, and keep your household, what it shares and its notifications.

Reading recipes from other sites

• When you import a link, Feast Planner’s server opens the page, and for a Pinterest pin, the recipe page the pin links to. The site sees Feast Planner asking for the page, not you.
• Feast Planner keeps the recipe it found there, without who asked, for up to 90 days, so anyone who imports the same link gets it straight away.
• When a page doesn’t set out its recipe clearly, Feast Planner may send the page’s address and text to an AI model, through Vercel AI Gateway, to read the recipe. Nothing about you is sent with it.
• Recipe photos and your Google profile photo are loaded through Feast Planner’s server, so the sites they come from don’t see you looking at them.

Reading recipes from photos

• When you add a recipe from a photo, such as of a cookbook page, your browser makes the photo smaller and sends it to Feast Planner’s server. The server sends it to an AI model, through Vercel AI Gateway, to read the recipe. Nothing about you is sent with it.
• Feast Planner doesn’t keep the photo, unless you choose it as the recipe’s photo. Reading it only fills in the recipe for you to check, and Feast Planner keeps the recipe once you save it.

Photos you add to a recipe

• When you add a photo to a recipe, or choose one of the photos it was read from, your browser makes a smaller copy of it. It sends that to Feast Planner’s server to keep when you save the recipe, or straight away when you add it on the recipe’s own page. The server checks it’s a photo and makes a fresh copy without the details phones store with photos: where and when it was taken, and the phone that took it.
• The fresh copy is kept with Vercel Blob, Vercel’s file storage, until you remove or replace it, or delete the recipe.
• Each photo has a long, hard-to-guess address. Feast Planner shows it only with your recipe, but anyone who has the address can open it, even on a private recipe.
• If the photo is sent but isn’t added to the recipe, such as when the recipe isn’t saved, the photo is deleted within two days.

The extension and the bookmark

The Save to Feast Planner extension for Chrome, and the Save to Feast Planner bookmark, save the recipe on the page you’re looking at. They do nothing until you click them.

• When you click, they read the page you’re on: its address and title, what it tells search engines and social sites about itself (such as its description and photo), its recipe markup, and the text of its main part, or of the whole page when it has no main part. Nothing else: not your other tabs, your history, or what you’ve typed into forms.
• The extension sends that page to Feast Planner’s server, which reads the recipe and saves it to your recipes, privately. When the recipe is missing something, such as its steps, it’s kept as a draft in My recipes for you to finish or discard. When there’s no recipe on the page, nothing is kept. Feast Planner keeps up to 50 drafts, dropping the oldest first.
• The bookmark, and the extension’s right-click item in Chrome before version 127, open Feast Planner in a new tab with that page in the part of the address after the #, which browsers don’t send to servers. Feast Planner keeps it in that tab until the recipe’s been read, and sends it to its server to read the recipe, for you to check and save.
• What they send is used only to read that recipe for you, and isn’t kept for anyone else. It’s never sold, or used for anything else.
• The extension asks Chrome to read the page you’re on when you click it, to add its item to the right-click menu, and to reach Feast Planner’s own site: to send it the page, signed in as you, and to tell its pages it’s installed. It keeps nothing itself.

The extension’s use of the information it receives follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Public recipes

Only you, and the people in your household, see your recipes unless you make them public. You can make up to three public: anyone with the link can see them, including people who aren’t signed in, and search engines may list them. Your name and email address aren’t shown with them. Their photos are public too: they can appear in image search, and apps that show a preview when the link is shared keep a copy.

Households

• The people in a household see each other’s names and profile photos, who owns it, and the email addresses it has invited, with who invited them.
• They see each other’s recipes, private ones included, and the public recipes each of them has saved, and can plan meals with them. Each one says whose it is, by their first name. Only whoever made a recipe can change or delete it, change its photo, or make it public or private.
• The household has a meal plan, cooked meals and shopping list of its own, which everyone in it sees and changes. Your own meal plan, cooked meals and shopping list stay yours: nobody else sees them.
• When you leave a household, or are taken out of it, your recipes go with you. The household stops seeing them, and upcoming meals made with them come off its plan, while the meals it’s cooked with them stay in its history, by name. In the same way, you stop seeing the household’s recipes, and upcoming meals made with them come off your own plan.
• Nobody outside a household sees it. It isn’t on any public page or recipe, or shown to anyone else, except that someone invited sees who invited them and the household’s name, when it has one, once they sign in with that address.
• Feast Planner doesn’t email anyone, so tell the people you invite yourself. It doesn’t tell the household whether an address has a Feast Planner account, or whether the person is already in another household: an invitation looks the same either way. Declining one tells nobody.
• An invitation is deleted when it’s accepted or cancelled, or 14 days after it was last sent. Declining one hides it from you straight away, but it’s kept until then, so the household sees it just as it would if the address had no account.

Notifications

• Feast Planner sends notifications only to a device you turn them on for, on the Household page, and only to that device. Turning them on adds a small script to your browser, Feast Planner’s service worker, which shows them.
• They say who invited you to a household, by their first name, and the household’s name, or who joined yours. They never include an email address.
• Your browser’s push service delivers them: Google’s for Chrome and on Android phones, Apple’s for Safari and on iPhones and iPads, Mozilla’s for Firefox, and Microsoft’s for Edge on a computer. What they say is encrypted so the push service can’t read it.
• Turning them off, or signing out, stops them for that device, and tells Feast Planner to forget it. Feast Planner keeps up to 10 of your devices, forgetting first the one you turned them on for, or last opened the Household page on, longest ago, and forgets one its push service says is gone.

Adding to your shopping list by voice

• The microphone button beside “Add to the list” uses your browser’s own speech recognition. It listens only after you tap it, and stops when you tap it again, stop talking, or leave the page.
• Your browser can send what you say to a speech service to turn it into text: Google’s in Chrome and on Android phones, Apple’s on iPhones and in Safari, and Microsoft’s in Edge on a computer. Feast Planner gets only the text, as if you’d typed it, and never hears your voice.
• Your phone keyboard’s dictation works the same way, under your phone’s settings.

Cookies and your browser

A cookie keeps you signed in. Feast Planner has no advertising or tracking cookies, and no analytics. Your browser also remembers a few choices for you, such as your meal planner settings, how your shopping list is grouped, and whether you’re looking at your household’s plan or your own; these stay in your browser.

Who else handles it

• Google, to sign you in. Feast Planner’s use of information received from Google follows the Google API Services User Data Policy, including its Limited Use requirements.
• Vercel, which hosts Feast Planner and keeps the photos you add, and the service that stores its database.
• AI models, through Vercel AI Gateway, which get a page’s address and text, or the photos you add, as above.
• The sites you import from, which see Feast Planner’s server asking for their pages.
• Your browser’s speech service, such as Google’s, Apple’s or Microsoft’s, which gets what you say when you use the microphone, as above.
• Your browser’s push service, such as Google’s, Apple’s, Mozilla’s or Microsoft’s, which delivers the notifications you turn on without being able to read them, as above.

No one else. Feast Planner doesn’t sell your data or share it for advertising.

Keeping and deleting

What you add is kept until you delete it. You can delete your recipes, drafts and planned meals at any time; deleting a recipe deletes its ingredients and steps, and takes it off every plan it’s on, your household’s included. Things you add to your shopping list are kept until you remove them, or, once checked off, until your next shop. Removing or replacing a recipe’s photo, or deleting the recipe, deletes the photo within two days, and usually straight away. To delete your account and everything in it, including your photos, email lamberson.david.ray@gmail.com.

Leaving a household takes you out of it, and its owner can take anyone else out. When the last person leaves, the household is deleted, with its invitations, meal plan, cooked meals and shopping list.

To report a public recipe, email lamberson.david.ray@gmail.com.

Children

Feast Planner isn’t meant for children under 13.

Changes

If what Feast Planner keeps or shares changes, this page will say so, with a new date at the top.

On October 23, 2026, Feast Picker was renamed Feast Planner and moved to www.feastplanner.app. The new name and address change nothing about what it keeps or shares.

On October 23, 2026, this page began to cover the things you add to your shopping list yourself, and adding them by voice.

On October 24, 2026, this page began to cover households, and the notifications Feast Planner can send to your devices.

On October 25, 2026, households began to share their members’ recipes, and to have a meal plan, cooked meals and shopping list of their own.

Questions

Email lamberson.david.ray@gmail.com about anything on this page. You can also go back to Feast Planner.