Terms

This is the part that matters most. Cooklist suggests recipes; it doesn’t know your kitchen, your ingredients or your health.

• Check every ingredient yourself if an allergy, an intolerance or a medical diet is involved. Diet labels such as “gluten-free” or “dairy-free” are estimates made from the ingredient list, not a guarantee, and a brand of sauce, broth or seasoning can change the answer.
• Cook to safe temperatures and use your own judgement on doneness, freshness and storage. Times and temperatures in a recipe are a guide.
• Nutrition figures are estimates, and nothing here is medical, nutritional or dietary advice. Talk to a professional about anything that affects your health.

• You must be at least 13 years old, or older if that’s the age where you live at which you can agree to a service like this on your own.
• You sign in with Google, and an account is for one person. We can decide who gets an account, and access to some parts may be limited.
• Keep your Google account secure. Anything done from your account is treated as done by you, so tell us at privacy@cooklist.me if you think someone else has got in.
• Your household shares meals, the shopping list, guidance, equipment and the product map with everyone in it. Your ratings, favourites and private notes stay yours.

• AI requests use credits. Asking for a recipe or a meal plan uses credits according to how much the AI had to read and write, so a plan with several new recipes uses more than a single recipe, and a plan built only from recipes already in the library uses the least. A request that fails uses none. Settings shows your credits and what each request used.
• Every account starts with some credits, and more can be added. The starting credits are once per person: if you delete your account and open another within 180 days, the new one starts with none. Because a request is charged when it finishes, your last one can take your credits slightly below zero; you then can’t start another until more are added. Credits can only be used here: they have no cash value and can’t be transferred or exchanged for money. Once credits are used they’re gone, including when you don’t like the recipe you got. Credits don’t expire while your account exists; if you delete your account, any credits left go with it.
• Buying credits. You can buy more credits in Settings, where the price and the number of credits are shown before you pay. Payment is taken by Stripe through its Link service, which is the seller of record: it adds any sales tax or VAT, sends your receipt, and appears on your card statement. We never see your card.
• Refunds. For 7 days after a purchase you can refund it yourself in Settings, as long as all of that purchase’s credits are still in your balance. A refund is always of the whole purchase: the full payment goes back to the card you used and the credits come off your balance. Once any of the credits have been used, or after 7 days, a purchase isn’t refundable, except where the law where you live says otherwise. If Stripe or your card’s bank returns a payment to you some other way, the credits from that purchase are taken back, which can leave your balance below zero.
• Don’t abuse it. Generating recipes in bulk, scripting the site, scraping it, or using it to build a competing recipe database isn’t on. So is anything unlawful, and anything that tries to break, overload or work around the site’s limits.
• AI output can be wrong, odd or repetitive. If a recipe looks unsafe or plain bad, don’t cook it, and tell us.

• Recipes are shared with every household on the site. A recipe the AI writes for you joins one library that everyone can see, search and cook from. Don’t put anything private in a recipe request.
• What stays inside your household: who asked for a recipe and what they typed, your cooking history, ratings, favourites and notes.
• What you type — recipe requests, your household’s guidance, meal names and your own notes — you let us store and use to run Cooklist, including sending it to the AI that writes your recipes. You still own your words.

Cooklist never places an order and never checks out for you. Choosing the Walmart option opens walmart.com with the products on your list, and everything after that, including prices, availability, substitutions, payment and delivery, is between you and Walmart, under their terms. Prices and products shown here can be out of date or wrong. Cooklist isn’t connected to Walmart, and Walmart doesn’t endorse it.

• You can stop whenever you like. Settings has a button to download a copy of your data and one to delete your account, and privacy@cooklist.me works too. The Privacy page says exactly what deletion removes.
• We can suspend or close an account for one of three reasons: it breaks these terms, it puts the site or other people at risk, or the law requires it. We’ll tell you the reason and how to reply, unless doing so would help someone who is abusing the site or we’re legally barred from saying. Write to privacy@cooklist.me if you think we’ve got it wrong.
• We can change or close Cooklist itself. If it closes, we’ll give notice in the app and by email, with time to ask for a copy of your data.
• Recipes already in the shared library stay there when an account goes, without your name on them.

Cooklist is offered as it is. It can be down, lose recent changes, change its features, or stop altogether. We don’t promise it will be available, correct or fit for any particular purpose, and we’re not liable for what follows from using it, including a meal that didn’t work, a shopping trip that went wrong, or lost data. If we are found liable anyway, the most we owe is what you paid us in the twelve months before the problem.

Where the law gives you rights that can’t be signed away, those still apply. These terms are governed by the laws of the State of Arkansas, USA, but if you’re a consumer somewhere else, you keep the protections of the law where you live.

If these terms change, the date at the top changes too, and we’ll mention anything significant in the app. Questions: privacy@cooklist.me.