Last updated: 16 October 2026
Christopher Lewis, trading as Green Leaf Cooking, is responsible for the personal information used to run this household meal-planning service. You can contact him at support@greenleafcooking.com or at the postal address below.
Information the service uses
- Account information: your account identifier, email address, display name and sign-in details. Firebase Authentication handles passwords; Green Leaf Cooking cannot read your password.
- Your kitchen: household numbers and portion settings, food choices, meal plans, shopping progress, recorded Stock, favourites, cooking history, recipe notes, saved AI drafts and ingredient edits.
- Membership: Stripe customer and subscription identifiers, subscription status, renewal or trial dates, whether a trial has already been used, and records needed to link a payment to the correct account. Stripe handles card details; Green Leaf Cooking does not receive your full card number.
- Support and technical information: information you send by email and technical information needed to deliver and secure requests, such as IP addresses, browser information, request logs and sign-in events. Hosting and authentication providers also process technical information.
Food choices are for meal planning, not medical assessment. You do not need to provide a diagnosis or explain why you avoid an ingredient. Please keep medical records, payment-card details and other unnecessary sensitive information out of recipe notes, support attachments and AI requests.
Why information is used and the legal grounds
- Providing the service: account access, saving or synchronising your kitchen, calculating quantities, sharing a household, handling membership and carrying out an AI feature you request are used to perform our agreement with you, or to take steps you request before entering it.
- Security and reliable operation: preventing misuse, remembering trial eligibility, applying usage limits, investigating errors and resolving support issues are based on our legitimate interests in running a secure and reliable service. We use information relevant to those purposes rather than using meal choices for advertising profiles.
- Legal obligations: information needed for accounting, tax, payment disputes or legally required responses is kept and used where necessary to meet those obligations.
Account and payment information is necessary for the corresponding account or paid feature. Without it, that feature cannot be provided. You choose the optional information you enter and whether to use household sharing, AI tools, photographs or device notifications. We do not sell your personal information.
Device storage and household sharing
The app uses browser storage and an offline cache to remember your settings, kitchen and working app files. Sign-in and payment providers use their own essential storage to operate those services. This release does not include advertising pixels or audience analytics.
Signed-in accounts can synchronise their own workspace through Firebase. In a shared Premium household, members can see and change the shared plans, shopping, Stock, favourites, cooking records, AI drafts and approved recipe edits. Household membership also includes identifiers and display names used to show who has joined. Keep your household code private and share it only with people you trust.
Personal recipe notes, your payment details and device notification choices are not part of the shared kitchen record. Resetting local app data does not by itself delete your account, shared household or subscription.
Photographs and optional AI features
When you choose photo scanning, the prepared photograph and ingredient catalogue are sent through the Green Leaf Cooking server to OpenAI to suggest Stock items. Green Leaf Cooking does not save that photograph in your account or Stock record. OpenAI's processing and retention are described in its API data policy. Review the detected items before adding them.
Create from Stock sends the relevant ingredient names and quantities, portion context, selected extras and food preferences. An ingredient-swap request sends the chosen recipe, requested edit, serving context and avoidance choices. Saved results are kept in your workspace or shared household when you save them. AI suggestions do not assess medical suitability or replace checking ingredients, food safety and cooking instructions yourself.
Feedback and website comments
Feedback is sent to a private inbox managed by Green Leaf Cooking. We store the comments you submit, an optional contact email, the app version, the submission date and, if you are signed in, your account identity. Feedback is separate from shared household cooking data. Limited request information is used to deter spam; the feedback inbox keeps a daily network fingerprint rather than a raw IP address.
When email notifications are connected, Resend processes a private email copy of your comments and optional contact email for delivery to Green Leaf Cooking support. Your account identity and withdrawal token are not included in that email. Email copies are separate from app inbox records, so a request to delete feedback also covers any support email copy we retain.
Sharing permission is optional and unticked by default. If you give permission, Green Leaf Cooking may choose your What is working well comment for the homepage, using your exact words and chosen display name. Your email and improvement suggestions stay private. We keep the permission wording, date and any withdrawal. You can withdraw permission in Send feedback on the device you used, or contact support with your feedback reference. Withdrawn comments are removed from live website sharing. Feedback messages can be deleted when no longer needed; minimal permission and withdrawal records may remain to record that decision.
Providers and international processing
The service uses Google/Firebase for sign-in and cloud synchronisation, Netlify for hosting, server functions and private billing or usage records, Stripe for checkout and subscription management, and OpenAI for the AI features you request. Support email is handled through the service's email provider. Each receives information relevant to the work it performs. Stripe also processes some information for its own payment, security and legal purposes.
The shared database is configured in a European region. That does not mean every provider keeps all information in the UK or Europe: authentication, hosting, support, payment and AI processing can involve other countries, including the United States.
The providers' published data-processing terms describe their international-transfer safeguards, which can include recognised adequacy arrangements and standard contractual clauses with UK transfer terms. Read Firebase's privacy information, Netlify's privacy information, Stripe's data-processing terms and OpenAI's data-processing terms. Contact us to ask about the safeguards relevant to your information or obtain further details.
How long information is kept
- On your device: kitchen records and preferences remain until you remove them, reset the app or clear browser storage. Clearing storage can remove information that has not synchronised elsewhere.
- Account and kitchen data: cloud records remain while needed for your account and the service you use. You can ask for deletion. Removing one member does not erase a shared household that other members still use.
- Billing and previous trials: limited payment links, previous-trial and dispute records can be kept after cancellation or account deletion where needed for accounting obligations, resolving a payment issue or preventing repeated trial misuse. The criteria are the applicable legal record-keeping period, any unresolved dispute and whether the record is still necessary for that limited purpose.
- Support and operational records: these are kept while needed to resolve the request, investigate a relevant security issue or establish the resulting decision. Provider logs and backups follow the provider's applicable retention and deletion arrangements; they may not disappear immediately when a live account record is removed.
Information is not kept merely to build advertising profiles. We do not claim that provider backups or legally required payment records are immediately erased when you clear the app.
Your privacy rights
Depending on the information and legal grounds, you can ask for access, correction, deletion, restriction or a portable copy of your personal information. These rights have legal limits, for example where payment records must be retained. Where processing relies on consent, you may withdraw it without affecting processing that was lawful before withdrawal.
Your right to object: you can object to processing based on legitimate interests. Tell us what you object to and your circumstances so we can assess the request.
Email support@greenleafcooking.com from the account address where possible. We may need reasonable information to verify that the request concerns your account. We will normally respond within one month; if a lawful extension is needed, we will explain it.
You can also complain to the UK's Information Commissioner's Office. Visit ico.org.uk/make-a-complaint or call 0303 123 1113. You do not have to contact us first to exercise that right.
Account deletion and automated checks
Settings includes a device-data export and an email link to request account and cloud-data deletion. A device export is not a complete copy of provider payment records; request those through support if needed. Tell us if you also want to end a subscription. Clearing local storage or signing out does not cancel it.
Subscription status and usage limits are checked automatically to control access to paid features. These checks use your current membership and recorded usage, rather than scoring your food preferences. Contact support if an access or billing decision appears wrong.
Changes
This page's date identifies the current notice. Material changes will be explained through an appropriate service notice. Contact us if you need help understanding how a feature uses your information.