Last updated: 24 October 2026

Cookie Policy

A cookie is a small note a website asks your browser to keep, rather like a tag tied to a gatepost so the farmer knows you have been through before. Plenty of sites use them to count visitors or to follow people from one page to the next. Open Field Haven does not.

This page records what the site does today, so you can check the claim against what your browser shows you.

1. What this site sets

1. Cookies: none. The pages do not ask your browser to store any.
2. Browser storage: none. There is no saved consent choice, because there is nothing to consent to, and no local storage, session storage or similar record is written.
3. Analytics: none. We do not count visits, measure which pages are read or build a picture of who you are.
4. Advertising: none. No advertising tags, remarketing lists or conversion pixels are loaded, and no data is sent to advertising networks.
5. Third-party content: none. The site embeds no maps, videos, social buttons or outside fonts, so no other company is asked to serve anything to your browser while you read.

2. The small scripts that are here

Some pages run a few lines of script that make the page itself work: the menu button on a phone, the season tabs, the honeycomb notes on the home page, the print button on the hive checklist, and the “Download contacts” button on the legal pages. They run in your browser, keep nothing between visits and send nothing anywhere. The styling comes from a file stored on the same server as the pages.

3. What the server may keep

A web server normally writes an ordinary access log: an IP address, the time and the page that was asked for. That is how the internet works and not something we add. We run no code that reads those logs and we do not match them to anything you tell us by email. More about information you send us yourself is in the Privacy Policy.

4. The enquiry form

The form on the home page and the contact page does not post to a server of ours. It opens an email draft in your own mail program, and nothing is sent until you press send there. It uses no cookie to remember what you typed.

5. Why we chose not to track

Our visitors are people standing at the edge of a field with a question, not a crowd to be measured. A session is sold by answering that question well, so there is little a visit counter or a remarketing list would add. Leaving them out also keeps the pages light, which matters to anyone loading them over a rural mobile connection, and it means there is nothing to explain, secure or delete on your side.

6. A few terms, in plain words

• Cookie: a small text file a site asks your browser to keep and send back on later visits. We set none.
• Local storage: a similar notebook inside your browser that a page can write to and read from. We write nothing to it, so there is no remembered consent choice, no remembered form entry and no remembered season tab.
• Tracking pixel or tag: a tiny image or script loaded from another company so that it can see you visited. None are loaded here, and the only network requests a page makes are for our own text, images and styling.
• Shared devices: because nothing is stored, there is nothing to clear after using the site on a library, school or family computer.

7. If this changes

Should we later add visitor statistics or advertising tags, for example when a paid search campaign starts, you would see a cookie banner with a real choice, this page would list each tag by name and purpose, and the Advertising Disclosure and Privacy Policy would be updated before any tag went live. Until you see such a notice, the answer to “what does this site store?” is: nothing.