Privacy Policy

Last updated: October 7, 2026 (sending your grocery list to a Kroger store)

SavorVault (“we,” “us”) provides a recipe-organizing app and website. This policy explains what information we collect and how we use it.

Information we collect

  • Account information: your email address and, if you sign in with Google or Apple, the basic profile information those services share with us (typically your name and email). You can also enter your name in Settings. Only your first name is shown to people you share a recipe or book with; your email is never shown.
  • Recipe content you create: recipe titles, ingredients, steps, notes, tags, categories, and any photos you attach to a recipe.
  • Planning content you create: meal plans, events and their menus, grocery lists and pantry staples, and recipe books (including their cover and page photos).
  • Plan and purchases: which SavorVault plan you have, and when it renews or ends. Subscriptions bought in the iOS app are handled by Apple, and ones bought on this website by Stripe; we receive the plan, dates, and a transaction reference, never your card or payment details.
  • Import count: how many AI-assisted imports you’ve used this month, for the Free plan’s monthly limit.
  • Camera and photo library access: the iOS app requests camera access to photograph recipe cards, and photo library access to attach photos to your recipes or import a recipe from an existing photo. Photos are only accessed when you choose to add or import one.
  • Clipboard (iOS app, once): the first time you sign in after installing, the app checks whether your clipboard appears to hold a web link, without reading it, so it can offer to open a SavorVault recipe link you copied on our website. The link is only read if you tap Paste, is used only to open that recipe, and is not stored.

How we use your information

We use your information to operate your account, sync your recipes between the app and this website, and to provide the features you use. We do not sell your personal information to third parties, and we do not use your recipe content for advertising.

AI-assisted recipe import

When you import a recipe from a photo, pasted text, or a social media post (its caption or description), or forward a recipe to your SavorVault email address, that photo, text, or email content (including attachments such as PDFs) is sent to our server and then to Anthropic, a third-party AI service, so it can extract the recipe’s title, ingredients, steps, and any notes or tips for you to review. When you import a recipe from a web link, the text of that public web page is also sent to Anthropic to find the recipe’s notes and tips. Anthropic processes this content to generate the result, does not use it to train its models, and deletes it after a limited retention period. This only happens when you choose to import a recipe one of these ways.

Forwarded emails and their attachments aren’t stored: they’re processed in memory and discarded once the recipes are read, and only the recipes extracted from them are saved to your account. The original email stays in your own mailbox (for example, your Sent folder), where you can delete it at any time.

Grocery lists and nutrition estimates

When you save a recipe, its ingredient lines (not your name or other account details) are sent to Anthropic to break each line into an amount, unit, and item for grocery lists, and to estimate its calories, protein, carbohydrate, and fat. The results are stored with the recipe in your account.

Nutrition figures in SavorVault, on recipes, meal plans, and recipe books, are estimates calculated from the ingredients and typical values for them. Actual values vary with brands, sizes, and preparation. They aren’t dietary, medical, or health advice and shouldn’t be relied on for medical conditions or allergies. SavorVault doesn’t collect information about your own diet or health.

Sending your grocery list to a Kroger store

If you choose to connect a Kroger-family store account (Kroger, Fry’s, Ralphs, King Soopers, Smith’s, Fred Meyer, Harris Teeter, and others), you sign in on Kroger’s own page — we never see your Kroger password. Kroger gives us a sign-in token that lets SavorVault add items to your cart at that store; we store it, with the store you choose, on our servers only, and use it only when you tap Send. We don’t place orders, see payment details, or read your order history.

When you send your list, the items on it (such as “chicken thighs”) and your store are sent to Kroger to find matching products and prices, and the products you pick are added to your cart. What happens in your cart and at checkout is covered by Kroger’s own privacy policy. You can disconnect at any time in Settings, which deletes the token from our servers; you can also remove SavorVault’s access from your Kroger account.

To decide whether to offer this feature at all, we check whether a Kroger-family store is near the approximate, city-level location our hosting provider derives from your IP address. That location isn’t stored with your account or used for anything else.

Where your data is stored

Your account and recipe data are stored with our database provider (Supabase), secured so that only you can access your own data, except for recipes you choose to share by link (below). Recipe photos are stored in a separate, private file storage service tied to your account.

Emails we send you (account confirmation, password resets, and notices when a forwarded recipe couldn’t be imported) go through our email provider (Resend). We don’t use analytics, advertising, or tracking tools in the app, and we don’t track you across other companies’ apps or websites.

Sharing recipes by link

When you share a recipe, we create a link to it (thesavorvault.com/r/…). Anyone who has that link can view the recipe without signing in, including its title, ingredients, steps, notes, category, cuisine, times, servings, photos, credit, and source link, along with your first name as the person who shared it. They can also download it as text or PDF, print it, forward the link, or save a copy to their own SavorVault account. Your email address and your other recipes are never shown.

Shared recipe pages are not listed on our website and ask search engines not to index them, but anyone you (or they) send the link to can open it. A link shows the recipe’s current version, so later edits appear on it. Deleting the recipe permanently disables its link; to disable a link without deleting the recipe, contact us through our Support page. Copies other people have already saved to their own accounts, downloaded, or printed are theirs and are not affected.

Recipe books can be shared the same way (thesavorvault.com/b/…). Anyone with a book's link can view its cover, dedication, and every recipe in it (with photos and stories), download or print it as a PDF, and save a full copy — including its recipes, photos, and extra pages — to their own SavorVault account. Deleting the book disables its link. If a book includes QR codes, each printed recipe also gets its own recipe link as described above.

Third-party sign-in

If you sign in with Google or Apple, those companies handle your credentials — we never see or store your password. We only receive the basic profile information needed to create and identify your account.

Your choices

You can edit or delete any recipe or category at any time, and you choose which recipes, if any, to share by link. You can delete your account and all associated data at any time from Settings → Delete Account, in the app or on this website. Deletion is permanent and removes your recipes, photos, categories, meal plans, events, grocery list, recipe books, share links, and any Kroger store connection, and ends a subscription bought on this website (a subscription bought through the App Store is cancelled in your iPhone’s Settings). If you need help, contact us through our Support page.

Changes to this policy

We’ll update this page if our data practices change, and update the “Last updated” date above.

This is a plain-language draft describing our actual current data practices — have it reviewed by a lawyer before relying on it as your final App Store submission policy.