Privacy Policy
This policy describes what this site actually does, not what a template says a website might do. There are no accounts here, no logins and no newsletter, which removes most of what a privacy policy usually has to cover.
What is left is genuinely worth reading: advertising cookies, the comments we store, the bot check on the comment form, and three things kept in your own browser.
At a Glance
The short version. Detail follows below.
What we collect
Only what you type into a comment or the contact form. Advertising and anti-spam partners set their own cookies, described below.
What we do not collect
No accounts, no passwords, no newsletter list, no payment details. We never ask for your address or phone number, and there is nothing to log in to.
Your choices
Ad personalisation can be turned off at Google's own settings. Everything we keep in your browser can be cleared from your browser at any time, and nothing breaks if you do.
What Is Stored and Where
Everything this site stores, the reason for it, and who holds it.
| What | Why | Where it lives |
|---|---|---|
| A comment you post | To display it publicly under the page you posted it on | Supabase, a hosted database. Stores the name you type (or "Guest"), the comment text, the page path and a timestamp. No email, no IP address, no account. |
| A message you send us | To read and reply to it | Our email inbox. Not added to any list, because there is no list. |
| Advertising cookies | To serve and measure ads once advertising is enabled | Google AdSense and its partners, under their own policies. |
| A bot check token | To make automated comment spam harder | Cloudflare Turnstile, which runs on the comment form. It is decorative here: posting works even if the check does not complete. |
| Your saved meal plan | So a plan you built is still there when you come back | Your own browser (localStorage). Never sent to us. |
| Recipe step progress | So ticked ingredients and steps survive a page refresh while you cook | Your own browser (localStorage). Never sent to us. |
| A comment throttle timestamp | To slow down accidental double posting | Your own browser (localStorage). Never sent to us. |
localStorage entries stay on your device until you clear your browser data. Nothing on this site stops working without them; you simply lose a saved plan.
Advertising
This site is funded by advertising and uses Google AdSense. Google and its partners may use cookies to serve ads based on your prior visits to this and other sites, which is the standard mechanism behind personalised advertising.
You can turn personalised advertising off at Google's Ads Settings, and opt out of third party vendor cookies at aboutads.info. Doing so does not remove advertising; it makes what you see less targeted.
We do not sell data, because we do not hold data worth selling. There is no user database beyond the comments table described above.
Comments
Comments publish immediately and are public. The name field is optional and defaults to "Guest", and we deliberately do not ask for an email address, which means a comment cannot be tied back to a person by us.
We may remove a comment that is spam, abusive or unlawful. If you want one of your own comments taken down, use the contact page and describe which page and roughly when you posted it, since without an account there is no other way to identify it.
Because the comment text is stored to be displayed publicly, please do not put anything private in one. A comment is a public statement, not a message to us.
Your Rights and How to Use Them
Under UK GDPR you have rights of access, correction and erasure over personal data a site holds about you. In practice the only thing this site can hold is a comment you chose to post and any message you sent us, so a request will usually be about one of those.
Write to us through the contact page with enough detail to identify the item. We will act within one month, which is the statutory period, and normally much sooner.
This policy will be updated if the site starts doing something new, and the effective date below changes when that happens. It is not a rotating date designed to look fresh.
Effective Date
This policy is effective from 31 May 2026 and describes the site as it operates on that date. Advertising is not yet enabled; the advertising section above takes effect when it is.
Privacy Questions
No, and there is not one to create. Comments take an optional name and nothing else, and every tool works without signing in.
Only if you email us, in which case it is in our inbox so we can reply. The comment form does not ask for one.
Three things: a saved meal plan, recipe step progress, and a timestamp that slows down double posting a comment. All three stay on your device and clear with your browser data.
At Google's Ads Settings, and for third party vendors at aboutads.info. Ads still appear; they become less targeted.
Yes. Use the contact page and tell us which page and roughly when you posted. There is no account, so those details are how we find it.
If analytics are added, this policy will be updated to name the provider and what it collects before they go live.