What I collect, and what I don’t.

The short version

There is no advertising network here and no tracking pixel. Nothing about you is sold or rented, to anyone, ever. There is one analytics script — Google Analytics, on the public pages, set up to count readers rather than to profile them, and described in full below. You can read every recipe on this site without giving me anything at all — an account is only needed to join in.

What I store

If you only read

Nothing that identifies you personally, and no account. Cloudflare, which serves the site, keeps standard infrastructure logs to route traffic and stop attacks; those are Cloudflare’s, not mine, and I do not build profiles from them.

The public pages do run Google Analytics, so Google is told which page was viewed, roughly where in the world you are, and how you arrived. Three things are deliberately true about how it is set up here:

• The address sent to Google is rebuilt, not passed along. Only the page path and campaign tags survive; everything else in the web address is discarded before Google sees it. That matters because links in my emails carry one-time codes — the link that confirms a subscription is the same one that unsubscribes it — and those never reach Google.
• The settings that would let Google join your visit here to its advertising profile of you are switched off. This measures my pages; it does not feed anyone’s ad targeting.
• It is not on every page. Sign-in, account, newsletter confirmation and unsubscribe pages, my own writing tools, and this page and the terms are all left alone.

If your browser sends a Global Privacy Control signal, none of it runs at all. Neither does it if you use a content blocker, and nothing on the site breaks when you do.

If you subscribe to the newsletter

Your email address, when you confirmed it, and where you signed up from. Confirmation is double opt-in, so an address does nothing at all until its owner clicks the link in the email. Every email carries a working unsubscribe link, and unsubscribing takes effect immediately.

If you create an account

Your name, your email address, and — if you signed up with a password rather than Google, Apple or Facebook — a hashed version of that password. I never see your actual password. If you sign in with a social account, I receive your name, email address and profile picture from that provider and nothing else; I never get access to your contacts, your files, or your account there.

Signing in creates a session record holding your IP address and browser user agent, so that you can be signed out everywhere if a device is lost.

If you comment or rate a recipe

Your comment, your rating, and a link to your account. Your name is shown publicly next to what you wrote. Your email address is never displayed — I see it when moderating, and that is all. Comments are reviewed before they appear.

Who else sees it

Four companies, each doing one job:

• Cloudflare hosts the site and stores the database. Everything above lives on their infrastructure.
• Resend sends email — newsletters, account confirmations and password resets. They receive your email address and the contents of those messages.
• OpenAI helps draft recipe writing from my own cooking notes. Nothing you submit is sent to them. Your comments, your account and your email address are never part of that.
• Google receives analytics about which pages are viewed, as described above. It never receives your name, your email address, your comments, or the one-time codes in my email links. If you also sign in with Google, that is a separate thing and it is covered below.

If you sign in with Google, Apple or Facebook, that provider knows you signed in here. That is inherent to how those buttons work, and it is why email and password remains an option.

Cookies

One cookie is mine: set only if you sign in, holding your session so you stay signed in between visits. It is not readable by scripts and is not used to follow you anywhere. Signing out removes it.

Google Analytics sets its own cookies on the public pages, so a reader who comes back is counted as one person rather than two. They hold a random identifier, not anything about you. A content blocker or a Global Privacy Control signal stops them being set at all, and nothing on the site breaks.

There are no advertising cookies, and nothing here is used to build an advertising profile of you.

Recipes, nutrition, and health

Nutrition figures on this site are estimates, calculated from reference data for the ingredients listed. They are not measured, and they will differ from what you actually cook.

I write about my own experience with food, weight and habit. I am not a doctor, a dietitian, or a licensed anything, and nothing here is medical or nutritional advice. If a decision about your health hangs on it, ask someone qualified.

What you can ask for

Whoever you are and wherever you live: you can ask for a copy of everything I hold about you, ask me to correct it, or ask me to delete it. Deleting your account removes your account record and your session history.

Comments you have already posted are a deliberate exception. Once published they are part of a public conversation other people have replied to, so by default they stay with your name detached from your account. If you want the words themselves removed too, ask and I will remove them.

Email hello@wellmadedaily.com and I will actually reply. There is no form and no ticket system; it reaches a person.

Children

This site is not intended for children under 13, and accounts are not knowingly created for them. If you believe a child has created one, tell me and I will remove it.

Changes

If what the site collects changes, this page changes first, and the date at the top changes with it. If a change is significant and you have an account, I will email you rather than quietly editing the page.