Data handling
Uploaded stills and workflow context are used to generate recipe guidance. This page explains the current public workflow in plain language.
Data flow summary
upload / process / history / recipe text
source stills, reference stills, intent, workflow context
diagnostics, reference mood, recipe generation
analysis records and recipe history when the product stores them
copy-friendly recipe text as the portable artifact
The short version before the detailed policy notes: inputs support recipe guidance, account history may preserve outputs, and current policy/support channels remain the source for storage, provider, and deletion details.
Source stills, optional references, creative intent, and workflow context supplied for a recipe run.
Generating diagnosis, reference mood interpretation, recipe guidance, and output UI.
Analysis records, uploaded image records, generated recipes, usage records, and account history when the product stores them.
Privacy, terms, product boundaries, and support remain the current references for policy-specific questions.
The copy-friendly recipe text can be kept in notes, client docs, or Resolve workflow checklists.
Inputs, processing, storage/history, policy references, and portability stay separated so the page reads like an operating guide.
What a recipe run can receive and why those inputs stay attached to the recipe workflow.
A recipe run can include visual inputs, written intent, and workflow context supplied by the user.
Uploaded inputs support the recipe artifact, not automatic grade application.
How recipe generation may involve configured model/provider processing without implying automatic grade application.
Recipe generation may use configured AI/model providers to analyze uploaded stills, text, and context.
What may be stored for account history and where retention/deletion policy still needs final review.
LookRecipe stores analysis records and recipe history to provide your account history and allow you to reopen results.
Retention and deletion details should be checked in the current product policy or through support.
Where to find policy references, support paths, and the copy-friendly recipe artifact.
The copy-friendly recipe is the portable artifact: you can keep recipe text outside the app for notes, client docs, or Resolve workflow checklists.
For current policy language, read the privacy and terms pages and contact support for specific deletion or data-handling questions.
This page avoids unsupported no-training, fixed retention, compliance, or certification claims.
LookRecipe creates explainable grading guidance from uploaded stills and context. Review the boundaries, policy pages, and example output before choosing the plan depth that fits your work.
Portable artifact
copy-friendly recipe text
Keep the recipe in notes, client docs, or a Resolve checklist. No LUT, DRX, or PowerGrade export is implied.
