Privacy

This privacy policy is a best-effort draft for planning and private testing. It must be reviewed before public launch.

Account information may include your email address, username, display name, password hash, profile text, avatar, authentication provider links, email verification status, and notification preferences.

Recipe content may include recipes, versions, ingredients, tools, steps, cover images, categories, cuisine, meal types, methods, tags, dietary flags, fermentation details, brewing details, preservation details, remixes, saved recipes, and suggested edits.

Support and feedback information may include feedback text, current page URL, account identifier if signed in, optional contact email, feedback status, and reviewer notes.

Operational information may include session data, security logs, request metadata, error logs, and hosting-provider logs such as IP address, browser, device, and timestamp where collected by infrastructure.

We use information to provide account access, email verification, password reset, recipe publishing, recipe search, version history, Cookbook saves, suggested edits, feedback review, notifications, security, debugging, abuse prevention, and product improvement.

Transactional emails may be sent for account verification, password reset, suggested edits, feedback follow-up, and similar service-related purposes. Notification preferences control optional notification categories where available.

Published public recipes and related public recipe metadata may be visible to other users and visitors. Registered users may save public recipes to a private Cookbook or remix public recipes.

If an account is deleted, public published recipes may be retained and anonymized to a deleted-user placeholder so links, remixes, saved recipes, and version history continue to work. Deleted-user profile pages are not browsable.

We may use service providers for hosting, database storage, image/file storage, authentication, email delivery, logging, backups, and security. Resend or another SMTP provider may process email addresses and email content needed to send transactional messages.

Future architecture may move some hosting or storage to Folsom Innovations infrastructure, including a Lenovo-hosted component, while retaining third-party services where useful.

RecipeVersion currently intends to use essential cookies and similar technologies for authentication, sessions, security, and basic operation.

We do not currently intend to use optional analytics, advertising pixels, session replay, or marketing cookies. If optional tracking is added later, it should be loaded only after appropriate consent and policy updates.

You may delete your account from settings. Private drafts and private account data may be deleted. Public published recipes may be retained in anonymized form. Feedback may be retained without the deleted account attached so product issues can still be reviewed.

Backups, logs, and security records may persist for a limited period according to operational and legal needs. Final retention periods require legal and infrastructure review.

You can update profile information and notification preferences in settings. You can delete your account from settings. You can submit feedback or privacy requests using the in-app feedback control until a dedicated contact channel is finalized.