Last updated: 20 November 2026
This explains what CookSwap knows about you, why, who else gets to see it, and how to get it back or get rid of it. It's written to be read rather than to be defended in court, so if anything here is unclear, ask and we'll fix the wording.
CookSwap is run by Liane and Paul Nelson, who are the data controllers for everything described here. Throughout this notice, “we” means the two of them — CookSwap is a couple, not a company. The quickest way to reach us is hello@cookswap.com.
CookSwap uses Sign in with Google. When you do that, Google tells us your name, your email address and your profile picture, and we keep those. We never see your Google password, and we can't do anything else with your Google account.
The cookie policy covers the cookies in detail.
Mostly, whoever you decide. Every post carries a privacy setting:
New posts start as Public. The setting is next to the Post button, so you can choose Members, My Kitchen or Only me before you post, and you can change it at any time afterwards by editing the post. Posts made before 17 September 2026 kept the setting they were made with.
The privacy setting decides who sees a post on CookSwap. The photographs in a post are stored as separate files with their own web addresses, so someone who is given the address of a photo can open it whatever the post's setting. We don't publish those addresses anywhere a post's setting doesn't allow.
Recipes are public. That's what the site is for: anyone can read one without signing in, and search engines index them. You choose whether your name appears on a recipe or whether it's credited to "a CookSwap member".
Some things are private unless you say otherwise: your pantry, your shelf, your meal plans, your favourites and your own diets are yours alone. Your shelf becomes visible to anyone holding the link if you create one, and Stop sharing switches that link off for good.
If you nudge someone in a post, they're told, and their name appears on it.
CookSwap is a small site standing on other people's infrastructure. These are all of them:
| Who | What reaches them | Why |
|---|---|---|
| Your name, email and picture at sign-in | Signing you in | |
| Google (Gemini) | Posts and natters as you write them; every photograph you upload, whether to a post, a recipe or your profile; recipes as you save them; ingredient lists; help and interface text | Checking posts, recipes and pictures before they appear, translating, generating recipes, reading your shelf and receipt photographs, working out diet labels |
| Microsoft (Clarity) | How you move around the site: taps, scrolls and the pages you visit, with anything you type hidden. Only if you accepted analytics cookies. | Finding the parts of the site people struggle with |
| Cloudflare (R2) | Photographs on posts and profiles | Storing and serving them |
| Pollinations | A recipe title | Generating a picture for an AI recipe |
| ip‑api.com | Your IP address | Working out which country you're in, so we suggest shops that deliver to you |
Most of these are in the United States, so your information travels there. They're bound by contract to protect it and to use it only for what we've asked.
When you tap an ingredient or a shop button, that's an ordinary link. We don't send anything about you to the shop — you simply arrive there, and what happens next is between you and them.
Until you tell us otherwise. Closing your account removes your name, email address, photograph and profile permanently.
Two things survive, and you should know before you close:
We don't charge for any of that and we'll answer within a month.
Tell us first — hello@cookswap.com — and we'll try to put it right. If you're not satisfied you can complain to the Information Commissioner's Office at ico.org.uk, or by phone on 0303 123 1113. You don't have to come to us first, but it's usually quicker.
CookSwap is for people aged 16 and over. If you believe a child has an account, tell us and we'll remove it.
If we change what we do with your information we'll update this page and change the date at the top. Anything significant, we'll say so on the site rather than hoping you notice.