This page explains current controlled paid beta data practices for LookRecipe and how uploaded material supports recipe generation.
Controlled-beta policy language. Legal review required before broad/public launch; do not treat this copy as final legal compliance advice.
LookRecipe may receive and store source still images, optional reference still images, look intent or vibe text, Resolve edition/profile choices, optional node tree context, generated diagnosis, generated recipe output, account identifiers, and basic usage history.
Images may be stored and processed to create visual diagnosis, node strategy, operator guidance, starting controls/ranges, protect/stop conditions, and warnings.
Uploaded source/reference images may be sent to configured AI/model providers for analysis. Model-provider processing is part of the recipe-generation workflow.
Account data is used to authenticate users, enforce plan limits, maintain usage history, and provide support.
Billing data is handled through Stripe. LookRecipe stores billing identifiers and plan state needed to provide the service, while payment method details are managed by Stripe.
Uploaded images and analysis data are retained as needed to provide history/recipe access unless deleted by request or future retention settings. Users can request deletion through support at TODO_SUPPORT_EMAIL.
Legal review required before broad/public launch. This controlled-beta privacy copy should not be treated as final legal compliance advice.