Cookie Policy

Last updated 1 October 2026

What we record ourselves

We keep a simple count of how the site is used, so we can tell which pages bring in work. This uses no cookies and writes nothing to your browser. It records:

• Page views — the page requested, the time, whether you were on a phone or a computer, which site you came from, and whether the visit came from an advert.
• Contact clicks — when someone taps a phone number, WhatsApp or text-message link, we record which link it was, where on the page it sat, which page it was on, whether you were on a phone or a computer, your browser’s identification string, the web address you came from, and the reference Google attaches to an advert click if you arrived from one of our adverts. We do not, and cannot, see the call or the message itself.
• Enquiry form submissions — covered in the Privacy Policy, since those contain your details.

To stop one machine flooding those counts, each record carries a scrambled one-way code derived from your IP address — and, for page views, your browser details as well. The recipe for that code changes at midnight each night, so the code we write today is different from the one we wrote yesterday and the same visitor cannot be followed from one day to the next. Records already stored keep the code they were written with until they are deleted. Your IP address itself is never stored in our database, and these records carry no name, no email and no phone number.

We delete these usage records after 14 months.

Server logs

Our hosting provider records standard technical information for every request — IP address, page requested, time, and browser type. This is how the site is kept running and protected from abuse. It is not tied to a cookie and is not used to build a profile of you.

Other companies your browser contacts

The pages themselves — typefaces, styles, scripts and most images — are served from this domain. Your browser also contacts:

• googletagmanager.com — on every page, to load the advertising tag described above. The tag then sends information back to Google on each page you open: the address of that page, the site you came from, your IP address and your browser details.
• api.postcodes.io — when you use the enquiry form, which appears on most pages of this site, and only once you have typed most of a postcode into it. We use it to check the postcode and fill in the area, which means that postcode and your IP address reach that service. It is a free public service run by Ideal Postcodes for looking up UK postcodes.
• supabase.co — on blog pages that carry a photograph, to load that image from our database provider’s file storage. It receives your IP address and browser details in order to send the image, and nothing else.

That was not always true of our typefaces. The site previously loaded them from Google Fonts, which meant your IP address reached Google’s servers on every page view. We now host those font files ourselves.

Controlling cookies yourself

Every browser lets you block or delete cookies for one site or across all sites through its settings. The Information Commissioner’s Office publishes plain-English guidance on cookies at ico.org.uk.

More on how we handle information

How we deal with personal information you give us — your name, phone number, address and job details — is covered in our Privacy Policy.