Cookies
Every cookie this site sets, what it does, and how to get rid of it.
Last updated 18 September 2026
The short version
Three cookies, and none of them are for advertising or analytics. There is no tracking on this site to consent to, which is why there is no banner asking you to.
The cookies
- wildcard_overland_session
- Laravel's session cookie. It is what lets the site tell one request from the next while you are on it - without it, a form could not be submitted safely. Set on your first page view, expires when you close your browser or after a couple of hours idle. Strictly necessary.
- XSRF-TOKEN
- A security token. It proves a form was submitted from this site rather than from somewhere else pretending to be you. Same lifetime as the session. Strictly necessary.
- wo_visitor
- A random string with no meaning anywhere but here, and the only reason it exists is so that if you come back to a recipe you reviewed, the site can say "your review is already in" instead of inviting you to write it twice. It is only set when you actually submit a review - read the whole site and you will never be given one. It cannot be read by scripts, it is stored hashed at this end, and it lasts about thirteen months.
Things kept in your browser, which are not cookies
Two things are saved in your browser's local storage. Unlike cookies these are never sent anywhere - they sit on your device and the site reads them back. I cannot see them.
- theme
- Whether you chose the light or dark version of the site, so it does not flip back on your next visit.
- wildcard:checklist:…
- Which ingredients you have ticked off on a recipe, so the list survives a page reload while you are shopping or cooking. One entry per recipe, cleared automatically after about six weeks.
What there is not
- No Google Analytics, or any other analytics.
- No advertising or retargeting cookies.
- No social media tracking pixels.
- No cookies from affiliate programmes set by this site. Following an affiliate link may let the shop at the other end set its own - that is between you and them, and their policy governs it.
Getting rid of them
Every browser can clear cookies and local storage for a single site, usually under Settings, then Privacy, then something like "cookies and site data". Clearing them here costs you the theme you picked and any ingredient lists you had ticked off. It does not delete a review you have already left - for that, see the privacy page.
You can also block cookies for this site entirely. The pages will all still work. The one thing that will not is leaving a review, because the security token above is a cookie and without it the form has no way to prove the submission came from you.