We use cookies to keep you signed in, and β only if you say yes β to see how the site gets used. The full list.
Last updated: 20 November 2026
We use low‑fat, low‑carb cookies here β but a few crumbs may still be left on your device. This policy explains exactly what those crumbs are, why they're there, and what you can do about them.
A cookie is a small text file stored on your device by your browser when you visit a website. Cookies are not programmes β they can't carry viruses or install software. They just help a site remember things between page loads, such as whether you're logged in.
Six cookies in total β two that keep the kitchen running, and four that tell us how many people came to dinner and where they got lost looking for the cutlery:
| Name | Purpose | Duration | Type |
|---|---|---|---|
| PHPSESSID | Keeps you signed in. Without this cookie you would be logged out every time you close your browser. | 30 days from last sign‑in | Essential |
| cs_consent_v2 | Remembers the cookie choice you made on this banner so we don't ask you again. The number goes up whenever what you're agreeing to changes, which is why you may have been asked twice. | 1 year | Essential |
| _ga | Google Analytics. Tells us how many people visit CookSwap and which pages they use, so we know what to improve. Only set if you choose "Got it, I'm hungry". | 2 years | Analytics |
| _ga_QS750877Q2 | Google Analytics. Keeps track of a single visit so repeat page views aren't counted as separate people. Only set if you choose "Got it, I'm hungry". | 2 years | Analytics |
| _clck | Microsoft Clarity. Recognises a returning browser so separate visits can be understood as the same person. Only set if you choose "Got it, I'm hungry". | 1 year | Analytics |
| _clsk | Microsoft Clarity. Joins the pages of one visit together so it can be replayed as a single session. Only set if you choose "Got it, I'm hungry". | 1 day | Analytics |
The first two are essential β the site simply won't work without them. You can't turn those off any more than you can bake without an oven.
The four analytics cookies are the ones we'd really rather you said yes to. Google Analytics tells us how many people visit and which recipes are popular. We have not switched on its advertising features or cross‑site tracking.
Microsoft Clarity goes a step further, and we'd rather say so than bury it. It records how a visit unfolds β where you tap, how far you scroll, the moment you give up looking for something β and lets us replay that visit afterwards, which is genuinely the quickest way to find the bits of the site nobody can work out. It is set to hide what you type into boxes, so your recipes, posts and searches aren't captured as you write them. We don't sell any of it. We wouldn't know who to sell it to.
Both are still, legally speaking, optional β so if you choose "Essential only" we don't load either of them at all. Not "load it quietly", not "load it but promise not to look". Neither script is ever fetched and no analytics cookie is ever set.
Here's the honest bit. Some of our partners are Very Large Corporations Indeed, and β as with virtually every other website and app on the interweb net thingy β they are not especially careful eaters. They spill crumbs on the carpet. We can hand them a plate and ask nicely, but once a partner's cookie is on your device it follows their rules and their privacy policy, not ours. We can't control what it does or how long it hangs about.
We'd rather say that plainly than pretend otherwise. What we can promise is that we won't quietly add new ones: we'll update this page before any new third‑party feature goes live, and ask your permission again where the law requires it.
Right now we use two: Google Analytics and Microsoft Clarity β and both come from what are, by some margin, Very Large Corporations Indeed. They act as our data processors, and they only get anything at all if you've accepted analytics cookies. When we added Clarity we asked everyone again rather than assuming an earlier yes still counted, which is the promise above being kept.
One thing worth knowing plainly: Clarity also sets cookies on Microsoft's own web addresses rather than ours. We can delete the ones on cookswap.com when you change your mind, but we have no power over those, so to clear them completely you'll need your browser's own settings.
You can read how each company handles the data at policies.google.com and privacy.microsoft.com, and you can opt out at any time using the link below.
You have several ways to manage cookies:
CookSwap uses Google OAuth to handle sign‑in. When you click "Continue with Google", you are redirected to Google's own servers to authenticate. Google may set its own cookies during that process β those are governed by Google's Privacy Policy, not ours. Once you return to CookSwap, we only receive the information Google passes back (your name, email address, and profile picture) and we store that in our own database.
If we introduce new cookies we will update this page before they go live and, where required by law, ask for your consent again. The date at the top of this page always reflects when it was last changed.