Privacy Policy

Account sign-in is provided through Lovable Cloud authentication. You may use email and password or Google sign-in. Week to Plate does not receive your Google password. Authentication infrastructure handles account identifiers, sign-in sessions, confirmation, and recovery information.

Your household profile can include a household name, adult and child counts, optional child age ranges, food likes and dislikes, dietary restrictions, allergies, cooking preferences, meal targets, budget preferences, and optional state or postal information used for supported seasonal guidance.

Using the product can store pantry items, weekly and monthly plans, recipe choices and placements, grocery lists and checkoffs, prep plans and task state, cooking history, saved weeks, leftover relationships, household recipe preferences, and user-created or imported recipes. User-created recipes are private to their owner under the current visibility model.

Guest planning uses a real anonymous account after bot verification. Guest household and planning data is stored in the same account-backed system and may persist in the browser session on that device. Exiting a guest session can make that data unrecoverable. Guest data is not fabricated demo data.

The Contact form stores the name you provide, your email, topic, and message. A Recipe Removal Request stores your name, email, relationship to the content, Week to Plate and original-source links, request type, and any details you provide. These records are private and used for operator review and follow-up. Do not include unnecessary sensitive information.

Information is used to operate authentication, personalize meal planning, maintain pantry and household state, generate grocery and prep outputs, preserve saved activity, answer requests, review source corrections or removal requests, protect the service, and diagnose technical problems.

Week to Plate does not currently integrate a named client-side analytics or advertising product. The hosting platform provides aggregate visitor and page-view analytics and may produce operational request, device, browser, network, approximate-location, security, and error information. Week to Plate does not track precise device location.

Lovable Cloud provides authentication, database, and hosting infrastructure. Cloudflare Turnstile is used to verify guest activation and may receive a verification token and edge-observed IP address. Authentication emails are handled by the authentication infrastructure. No separate contact-form email provider is currently configured.

Recipe imports fetch the source URL on the server. Links to recipe publishers and other external sites are governed by those sites' own privacy practices.

Session and product state may use browser storage so sign-in and guest access can persist on a device. Private household, planning, request, and user-recipe data is protected by account-scoped access controls. Public recipe records and source attribution are visible in the Recipe Library.

Week to Plate does not sell personal information and does not currently use personal information for third-party advertising. Information may be handled by infrastructure providers to operate and secure the service, or disclosed when reasonably necessary to comply with law or protect rights and safety.

Information is retained while needed to provide the service, maintain records, review requests, protect security, and meet legal obligations. You can permanently delete your account and private data from the Household page. To ask about access or correction of account data, choose “Account or data request” on the Contact page. Some records may need to be retained for legal, security, or operational reasons.

Week to Plate uses account authorization, row-level access controls, server-side validation, private request storage, and abuse controls. No online service can guarantee absolute security, so use a unique password and avoid sending secrets through public forms.

Week to Plate is a household planning service, not a service designed for children to operate independently. A household may optionally record child counts and broad age ranges to improve planning. That information is household-planning data, not a medical record.

This policy may be updated as the product and its data practices change. The date above identifies the current version. For privacy questions or requests, use Contact.