You must consent to the items below to use Cookhae. Without the required consents, recipe extraction, saved-recipe library, and recommendations will not work.
1. Required collection and use
Items: Firebase anonymous user ID, video URLs you submit, public video metadata, text extracted from captions/subtitles, generated recipes, saved-recipe / planner / shopping data, app usage logs, error logs, IP address.
Purpose: account identification, recipe extraction and storage, search, recommendation, planner, shopping, security, abuse prevention, error response.
Retention: until account deletion or until the purpose is fulfilled. Records required by law or for dispute resolution may be retained for the period defined by law.
2. AI processing consent
The video URL, public metadata, captions/subtitle text, and your requests for variants / substitutions / recommendations may be sent to AI systems including Google Generative AI / Gemini to extract, summarize, transform and recommend recipes. AI output can be inaccurate; you must independently verify anything related to allergies, nutrition or health.
3. Global recipe sharing and cache
Recipes generated from public URLs may be stored in our global recipe cache for deduplication, search, recommendation, and quality. Whether or not you save a recipe to your library, the recipe and its source link generated from a public video may be visible to other users.
4. Coins, rewarded ads, and future payment processing
Coin balances, spend/grant history, and rewarded-ad grants are used to deliver coin/reward features, prevent abuse, process refunds and provide customer support. If paid purchases are introduced later, store transaction identifiers may also be processed for payment verification and refund support.
5. Optional: taste-based personalization
With your separate consent, signals from your saved recipes, cooked status, reviews, search queries, recommendation clicks, and preferred cuisine / mealType / spice can be used to personalize recommendations. You can turn this on or off in onboarding or settings; the default is OFF.
Effective date: April 25, 2026