Privacy Policy
Last updated August 9, 2026
Who we are
Supper Table by Miz Kathi’s (“Supper Table,” “we,” “us”) is a recipe, meal-planning, and shopping-list app, with an optional suite of tools for home-based food businesses. This policy explains what we collect, why, and how you can control it.
Information we collect
Account information. If you sign in, we collect your email address (for passwordless magic-link sign-in) or, if you use “Sign in with Google,” the name, email, and profile photo Google shares with us. We never see or store a password — the app doesn’t use them.
Content you create. Recipes you save or write, meal plans, shopping lists, favorites, ratings and reviews, and — if you use the Business tools — inventory, invoices you upload, menu items, sales records, and resale labels.
Nutrition & exercise tracking (optional). If you use the Nutrition & Exercise tools, we store what you choose to enter: your food diary and exercise history (dated log entries), your daily nutrition targets, and — if you fill it in — an optional body profile (sex, age, height, weight, activity level) used only to personalize calorie estimates on your own account. None of this is shared with anyone besides the service providers below that make the feature work, and it’s never used for advertising. If you scan a barcode to log a food item, the barcode itself (not your account or identity) is sent to Open Food Facts, an open product database, to look up its nutrition facts — see “Who we share it with” below.
Device-local preferences. Things like dietary/allergen filters and light/dark theme are stored only in your browser’s local storage, not on our servers, and don’t sync between devices.
Usage with Chef AI. When you ask Chef AI for pairings, nutrition insights, or recipe improvements, the relevant recipe text and your question are sent to our AI provider to generate a response. We don’t send your account identity along with that request.
Payment information. If you subscribe to Premium or Chef Pro, your card details are entered directly into Stripe’s hosted checkout page — we never see or store your full card number. We do store your Stripe customer and subscription IDs, which subscription tier you have, and billing status (e.g. active, canceled), so the app can grant or remove access.
The browser extension
The Supper Table browser extension runs on the pages you visit so it can detect a recipe’s allergens and diet tags and show a badge automatically, without you having to click anything first. That’s the reason it asks for a broader permission than a typical extension (“read and change your data on the websites you visit”) — here’s exactly what that is and isn’t used for.
What happens on every page. The extension reads the structured recipe data (if any) already embedded in the page you’re viewing — entirely in your browser — to check for allergens and diet tags. This never leaves your device and is never sent to us unless you explicitly choose to save that recipe.
What gets sent to us, and when. Only when you click “Save recipe from this page,” use the right-click “Import to Supper Table” menu, or run a batch import: the recipe’s title, ingredients, and steps are sent to Supabase to save it to your account, the same way saving a recipe in the web app works. A cost estimate (if shown) and a check for a similar recipe already in our catalog go through our own servers the same way the rest of Chef AI does — see “Who we share it with” above, no new third party is involved.
Batch import opens candidate recipe links from a page you’re viewing in hidden background tabs to read them the same way, then closes them — it doesn’t change what tab you’re looking at or send your browsing history anywhere.
Signing in. The extension uses your existing Supper Table account via a one-time paired sign-in — it doesn’t create a separate account or ask for a password. Your session is stored locally in the browser (via Chrome’s extension storage), the same purpose your browser’s local storage already serves for the web app.
The extension doesn’t include any analytics or advertising code.
Connecting a Dexcom glucose monitor (optional)
If you choose to connect a Dexcom CGM from the Nutrition page, you’re redirected to Dexcom’s own sign-in page — we never see or store your Dexcom password. Dexcom then gives us a token that lets us request your glucose readings on your behalf, which you can revoke at any time from Dexcom’s own account settings, or by clicking “Disconnect” in Supper Table.
When you click “Sync now,” we request your recent glucose readings from Dexcom and store them in your account so you can see them alongside your food diary. This data is never sold, never used for advertising, and never shared with anyone besides you. Readings already synced stay in your account if you disconnect — disconnecting only stops future syncing.
Dexcom’s data is retrospective, typically 1–3 hours behind real time, not a live feed, and nothing in Supper Table is medical advice — always use your CGM’s own app or device for anything time-sensitive.
How we use your information
- To operate the app: save your recipes, plans, and lists, and sync them across your devices when you’re signed in.
- To generate the AI features you ask for (pairings, nutrition estimates, recipe improvements, transforms, invoice scanning).
- To run the optional Business tools you choose to use (inventory, costing, resale labels).
- To communicate with you about your account, such as sign-in emails.
We do not sell your personal information, and we do not use it for third-party advertising.
Who we share it with
We share data only with the service providers that make the app work, and only as needed to run it:
- Supabase — our database, authentication, and file storage provider.
- Netlify — hosts the app.
- Anthropic — processes the text behind Chef AI’s pairing, nutrition, improvement, and invoice-scanning features.
- Stripe — processes payments for Premium/Chef Pro subscriptions and handles your card details directly; only used if you subscribe.
- Google — if you choose “Sign in with Google,” or via Google Analytics (see “Cookies & analytics” below).
- Kroger — only if you choose to connect your Kroger account to send a shopping list to your Kroger cart. Nothing is shared with Kroger unless you take that action.
- Dexcom — only if you choose to connect a Dexcom CGM to see your glucose readings in the app. Nothing is requested from Dexcom unless you take that action.
- Open Food Facts — only if you scan a barcode in the food diary; we send the barcode number to look up nutrition facts. No account information is included in that request.
We don’t share your data with anyone else, except where required by law.
Cookies & analytics
We use your browser’s local storage to keep you signed in and to remember device-local preferences. We also use Google Analytics to understand how people use the app (pages visited, general usage patterns) — this sets analytics cookies in your browser. We don’t use it, or anything else, for third-party advertising.
Data retention & deletion
We keep your account data for as long as your account is active. You can delete your account yourself from the Account page, or contact us at the email below and we’ll take care of it. If you have an active Premium/Chef Pro subscription, deleting your account also immediately cancels it.
Children's privacy
Supper Table isn’t directed at children under 13, and we don’t knowingly collect information from them.
Security
We rely on our providers’ industry-standard security practices (encryption in transit, access controls) to protect your data, but no method of storage or transmission is 100% secure.
Changes to this policy
If we make material changes to this policy, we’ll update the date at the top of this page.
Contact us
Questions about this policy or your data? Email jdvincent@cafecotillion.com.

