Clip and recipe data
CookTheClip uses submitted clip URLs, source metadata, captions, transcripts, media signals, and generated recipe content to provide conversions and saved recipes.
Privacy
CookTheClip should collect the minimum data needed to convert clips, enforce quota, save recipes, and run billing.
CookTheClip uses submitted clip URLs, source metadata, captions, transcripts, media signals, and generated recipe content to provide conversions and saved recipes.
Account, quota, saved-library, and plan details are handled with server-side access controls and exposed only where needed for the signed-in experience.
Frame samples, captions, transcripts, audio transcripts, and source metadata are used to generate recipe estimates and retained only when there is a clear product need.
Saved recipes and account data should be removable through account controls. Raw processing artifacts should expire automatically unless a user explicitly saves a recipe.
Copyright, privacy, safety, and support reports may include contact details, recipe IDs, source URLs, and review notes so the request can be handled.
CookTheClip is designed around minimal collection, private libraries, clear retention rules, and server-side handling for account and billing data.
Use account settings for saved recipes, plan details, and safety preferences.