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
Keep the recipe useful. Keep the data boring.
CookTheClip should collect the minimum data needed to convert clips, enforce quota, save recipes, and run billing.
Account data
Account, quota, saved-library, and plan details are handled with server-side access controls and exposed only where needed for the signed-in experience.
Video signals
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.
Deletion
Saved recipes and account data should be removable through account controls. Raw processing artifacts should expire automatically unless a user explicitly saves a recipe.
Rights and support requests
Copyright, privacy, safety, and support reports may include contact details, recipe IDs, source URLs, and review notes so the request can be handled.
Privacy commitments
CookTheClip is designed around minimal collection, private libraries, clear retention rules, and server-side handling for account and billing data.
- Hash anonymous usage keys before storing them.
- Never expose service-role keys to the browser.
- Delete temporary frames, audio, and transcripts on a schedule.
- Keep Stripe payment data in Stripe, not in app tables.
- Make saved recipe deletion obvious and reversible only when safe.
Manage your recipe data
Use account settings for saved recipes, plan details, and safety preferences.