Cookie Policy

What it does keep is two small display values in your browser's local storage, on your own device, which your browser never sends to us or to anyone else. Nothing stored on your device tracks you. Separately, the hosting that delivers this site may keep ordinary technical records of requests, which is explained at the end of this page.

Google Fonts is the only third party your browser is asked to contact, for the site's typefaces. Our hosting provider is a separate matter: it handles requests on our behalf under a written contract. Both are explained in full below.

No. This site sets no cookies at all, first party or third party. There is no Google Analytics or any other analytics, no tracking pixels, no advertising tags and no social media trackers. Nothing on these pages is profiling you or following you between websites. Records kept by whoever hosts the site are a separate matter, and they are dealt with under "Hosting and server records" below.

For anyone who has not had a reason to care what a cookie is: it is a small piece of text that a website asks your browser to store and then sends back to that website on later visits. Cookies are how sites keep you logged in, and they are also how advertising networks recognise the same person across many different sites. This site does neither, so it has no need for them.

You will not see a cookie consent banner here, and that is deliberate rather than an oversight. Consent banners exist so people can refuse non-essential cookies and trackers. There are none on this site to refuse.

The site loads its typefaces from Google Fonts, at fonts.googleapis.com and fonts.gstatic.com. That is the only third party your browser is asked to contact when it loads a page here, and it happens automatically as the page loads, in the same way as fetching an image hosted elsewhere. It is not the whole third-party picture, though: the site itself is delivered by a hosting provider that processes requests on our behalf under a written contract, which is covered under "Hosting and server records" below.

Because your browser connects to Google directly to collect the font files, that connection reaches Google's servers with your IP address and ordinary browser details such as the browser and version you are using and the operating system it runs on. Google says it logs these requests and uses aggregated data about font usage to improve the service, and that it does not use Google Fonts requests to build profiles of the people making them or to serve advertising. You can read that for yourself in Google's Google Fonts privacy FAQ at developers.google.com/fonts/faq/privacy rather than take our word for it.

Google Fonts is operated by Google LLC in the United States, so this request involves a transfer of personal data outside the UK. The safeguard relied on for that transfer is [TO CONFIRM: whether Google's UK-US Data Bridge certification or its IDTA and UK Addendum terms are the relied-on safeguard, per Google's current terms], and details of it are available on request.

An IP address is personal data and this is a transfer to a third party, so we would rather set it out plainly than leave it unmentioned. Google's own handling of that data is governed by its privacy policy. If you would prefer the request not to happen at all, you can block remote fonts in your browser, as described in the next section; the site will then use a typeface already on your device and will remain perfectly readable.

If you arrived here from the footer link about updating your cookie consent, this is the honest answer: there is no consent to update, because there is no consent banner and nothing has been set that would need one. We show no banner because this site sets no cookies and runs no analytics, advertising or social media trackers, so there is nothing non-essential for you to accept or refuse.

The rule itself is broader than cookies, so it is worth stating properly. Under the Privacy and Electronic Communications Regulations, consent is needed before anything is stored on your device, or read back from it, unless that storing or reading is strictly necessary to provide the service you have asked for. It applies to reading a value as much as to writing one, and it applies whether or not the information identifies you, and whether or not it is shared with anyone. So each of the items above has to stand on that test, not on being harmless.

eicrpro-admin-on passes it because it never arises for you. It is only ever written on the site owner's own device, by the owner's own action of switching the editing controls on. Nothing is stored on an ordinary visitor's device by it at all, so there is nothing for you to consent to.

eicrpro-hero-dark is not a record of any choice you made: it is a cached copy of a brightness setting the site owner picked. It is stored solely so that the page you asked for renders at the correct brightness on first paint, and on that basis we treat it as strictly necessary to display the page you requested. If that argument is thought thin, the alternative is to send the value with the page itself and store nothing on your device, and we would rather set the question out than pretend it does not arise. Either way, you do not need our permission to be rid of it: clear the site data or use a private window, as set out above.

If this ever changes, for example if we added a contact form, an online booking tool or any form of visitor measurement, we would ask for your consent before anything non-essential was stored, and this page would be rewritten to say exactly what was involved and how to withdraw that consent. Until then, the most accurate cookie setting we can offer you is the one you already have in your browser.

Separately from anything stored in your browser, this site is delivered by a hosting provider, which handles requests on our behalf as our processor under a written contract. [TO CONFIRM: hosting provider name and the country its servers are in.] If those servers sit outside the UK, that is a transfer of personal data outside the UK, and this page will be updated to name the safeguard relied on.

Web servers commonly keep access logs recording technical details of each request, such as the IP address it came from, the time it was made and the page requested. The application code that runs this site writes no such log. Whether the hosting layer in front of it keeps one is a question about the hosting arrangement, and we are not going to describe records we have not verified: [TO CONFIRM: the hosting provider, whether it keeps access logs, which fields those logs contain, and the retention period]. If it turns out that no access logs are kept at all, this section will say so plainly, which is a stronger statement than the one we can make today.

Any records of that kind would be created by the server rather than by anything on your device, so clearing your site data or using a private window does not affect them. Whatever exists, we do not use it for marketing, measurement or profiling, and we do not combine it with anything else to build a picture of individual visitors.