Privacy Policy

• Account information — your email address, display name, and username
• Recipe data — recipes you import, scan, speak, or create
• Usage data — which features you use (we use this to improve the app, never sold)
• Photos — images you upload to recipes, stored on our own server
• Shopping lists, meal plans, and preferences you create
• Cooking activity and notes — when you cook a recipe and any notes you write about it (see "Cooking activity and notes" below)
• Feedback messages you submit through the app

• We do not sell your data to anyone — ever
• We do not show ads
• We do not share your data with third parties except the services listed below
• We do not collect payment information directly — if billing is active, it's handled securely by Stripe

These are every external service ChefsBook sends data to, and what each one receives.

• Supabase — database and file storage (self-hosted on our own server, not Supabase cloud).
• Anthropic (Claude) — AI features: recipe extraction, scanning, translation, suggestions and moderation. Recipe text, and photos you scan, are sent for processing. Under Anthropic's API terms this content is not used to train their models.
• Replicate — AI image generation. A recipe's title and description are sent to generate an illustrative image.
• Resend — transactional email (welcome, password reset). Receives your email address.
• ScrapingBee — fallback page fetching when a recipe site blocks a direct request. Receives only the URL you asked us to import.
• YouTube / Google — importing a recipe from a video. Receives the video URL you provide.
• Google Books — looking up cookbook details. Receives the book title or ISBN you search for.
• Google Photos — optional. Only if you choose to import a photo from it. You pick the photos in Google's own picker; we download those photos server-side and re-host them, so we never store a Google link. The access token lives in a session cookie and no long-lived refresh token is kept.
• Lulu — print-on-demand, only if you order a physical cookbook. Receives your order and shipping details in order to print and deliver it.
• Stripe — payment processing, if and when billing is active. Card details go directly to Stripe; we never receive or store them.
• Pexels and Unsplash — stock photo suggestions. Receive the search term only; no personal data.
• Logo.dev — store logo lookup. Receives only the store name.
• Cloudflare — CDN and secure tunnel. Handles web traffic with standard CDN privacy practices.

The ChefsBook browser extension captures the HTML of pages you explicitly choose to import. This HTML is sent to our servers for recipe extraction only. We do not capture your browsing history or any pages you did not choose to import. The extension stores your ChefsBook login token locally in Chrome storage.

All user data is stored on our own dedicated self-hosted server, located in the United States. Your data is not stored in third-party cloud services — we self-host the database and all uploaded images. Backups are stored locally on the same server.

• You can delete your account and all associated data at any time from Settings
• You can export your recipes in CSV or JSON format from Settings
• You can contact us at [email protected] with any data questions

When you cook a recipe in ChefsBook, we record cooking activity — what you cooked, when, and whether the session was completed — to power features like your cooking history and the Sous Chef's guidance. If you write a note during or after a cooking session (for example, a substitution or a reminder for next time), that note is stored with your account and is visible only to you in the app — it is never shown to other users, on public recipe pages, or in any feed.

Administrators can view aggregate cooking activity (such as how many sessions happen per day, or which recipes are cooked most) to understand how the app is used. Administrators can also look up individual cooking activity, including who cooked what and when, and can read the text of cooking notes, when needed to operate, support, or improve the app. This admin access is a deliberate exception to the "visible only to you" rule above, and is limited to administrators — it does not change who else can see your activity or notes.

We use session cookies for authentication only. We do not use tracking cookies, advertising cookies, or any third-party analytics cookies.

ChefsBook is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal data, please contact us and we will delete it.

If we make significant changes to this privacy policy, we will notify registered users by email. Minor wording changes may be made without notification.

Questions about your privacy? We're happy to help.

Email: [email protected]
Website: chefsbk.app