Privacy
Privacy Policy
Effective October 8, 2026
CraveCraft Kitchen does not require an account to browse recipes. Optional accounts use an email address and display name. CraveCraft does not ask for payment details. If you choose to save a preferred name or other remembered cooking detail, it is handled as described below.
Saved recipes, saved cooking-assistant conversations, and cooking preferences are stored in your browser using local storage. Cooking preferences are also mirrored to a first-party functional cookie so they can be restored on that device if local storage is temporarily unavailable. They can be removed from the relevant Saved or Remembered Preferences controls, or by clearing browser data. When signed out, this information stays on your device. When signed in to a verified account, supported saved content, preferences, meal plans, Progress data, and cooking state can sync to your account through Supabase. These records are not used for advertising. Removing synced content queues its removal from your account; offline removals need a connection before completing.
Optional recipe activity personalization
Taste-based personalization is off until you opt in through Personalization and confirm you are 18 or older. When enabled, deliberate recipe selections, recommendation clicks, successful recipe adaptations, recipe shopping-list additions, and Guided Cooking start/progress/completion can suggest uncertain interests. We do not use idle time, scrolling, passive card displays, or old mention counters as this feature’s evidence.
Activity records contain catalog recipe identifiers, action classes, timestamps, and coarse six-hour occasions. They have no cookie mirror. When signed in, supported activity records can sync to your account. At most 96 recipe/occasion records are kept; evidence expires after 30 days and older evidence has less influence. Expired records are ignored on read and removed on the next recorded action or Reset. No name, raw conversation, or cross-site browsing is stored in these activity records.
The site uses this evidence for recipe recommendations, creative Custom Recipe direction, and occasional optional memory offers. It does not automatically become Remembered Details. A bounded selection of events may accompany an existing text Assistant request, where application logic validates catalog references and derives a compact uncertain-interest summary. That summary may be included in the existing AI service request. Providers process requests under their own terms; activity is not sent as a separate advertising or analytics feed.
Off stops new collection and use but keeps existing activity. Reset recipe activity deletes these activity records without deleting confirmed Remembered Details or saved conversations. Clearing browser data removes the device copy, not synced account records. This feature is not offered to users who have not confirmed they are 18 or older; there is no age inference from cooking behavior or verified-age account system.
The cooking assistant uses a randomly generated first-party visitor cookie and server-side usage records so it can apply reasonable request-rate protections without requiring an account. A temporary signed session token may also be stored for authorized testing. These values do not contain your name, email address, or chat messages.
The cooking assistant handles many common questions directly on the site. Questions that require additional reasoning may be sent, together with a limited amount of recent chat context and relevant recipe information, to a third-party AI service. Do not include sensitive personal information in a cooking-assistant message. Assistant messages may also be processed briefly to prevent abuse and enforce reasonable request limits.
Features you intentionally use may send additional content to the service that performs that task. An attached cooking photo may be sent for visual analysis, Voice Mode sends audio and limited conversation context to its voice service, and generating an image for a Custom Recipe sends a recipe-derived image prompt to the image service. Do not submit sensitive information through these features. Each provider may process service data under its own terms and privacy practices.
Hosting providers may receive standard technical information such as IP address, browser type, requested pages, timestamps, and error logs as part of operating and securing the site. We use this information only for delivery, reliability, troubleshooting, and abuse prevention.
If analytics, advertisements, affiliate links, additional data collection are introduced, this policy will be updated before those features are enabled. Third-party links have their own privacy practices, which CraveCraft Kitchen does not control.
Optional accounts and private sync
Supabase handles account authentication and stores your account profile and supported saved records. Google sign-in uses Google and Supabase; email confirmation and password recovery use the configured email service. Account photos and generated recipe images use a private storage bucket with access limited to your account. Credentials are handled by the authentication services and are not saved in recipe or chat content.
Signing out ends this device’s account session and does not delete your cloud account. Conflict review preserves pending device changes rather than silently overwriting them. Server-side usage records enforce daily or weekly feature allowances; a first-party visitor cookie helps combine same-day Assistant usage at sign-in. Owner access is checked on the server.
Nutrition estimates and AI cooking guidance are informational and are not medical advice.