RecipeBank — Privacy Policy

Last updated: 2026-07-17

This policy covers the RecipeBank browser extension and the RecipeBank web app at recipebank.food.

What the extension does

The RecipeBank extension lets you save a recipe from a web page into your personal RecipeBank collection. It only acts when you invoke it.

What it accesses, and when

• The recipe page you're saving — only when you click the RecipeBank button. At that moment the extension reads the current page's content (title, ingredients, instructions, image) and its URL and title, so it can capture the recipe and record where it came from. It does not read pages in the background, and it does not monitor your browsing.
• Your RecipeBank sign-in — after you log in at recipebank.food, the extension receives a sign-in token so it can save recipes to your account.

What it stores, and where

• Locally on your device (browser storage): your RecipeBank sign-in token and your extension preferences, so you don't have to re-authenticate every time.
• In your RecipeBank account (our backend, hosted on Supabase): the recipes you choose to save. These belong to you and are visible only to your account.

What it does NOT do

• No tracking of your browsing history or activity.
• No selling or sharing of your data with advertisers or third parties.
• No access to any page except the one you explicitly choose to save from.
• No analytics or fingerprinting in the extension.

Data sharing

The only place your captured recipes and sign-in token go is your own RecipeBank account and its backend (Supabase), which we operate on your behalf. We do not share your data with anyone else.

Data retention and deletion

Your saved recipes remain in your account until you delete them or delete your account. Clearing the extension's data (or signing out) removes the locally stored token and preferences from your device.

Contact

Questions about this policy or your data: upstill@gmail.com