Cookie Policy

This site sets no cookies of its own. There is nothing here to log in to, no basket and no account, so there is nothing to remember about you between one page and the next. There is no advertising, no social media pixel and no tracking.

It does keep one setting in your browser’s local storage: whether you chose the 3D version of the front page or the plain one. That is a preference you set, held on your device and never sent to me. It is described in section four.

One cookie does reach you, and it is not mine: the site runs on a machine at my house and is proxied through Cloudflare, which sets a security cookie to tell real browsers from bots. It is described below.

I do count page views, using analytics software I run on that same machine. It is cookieless - it puts nothing on your device and holds nothing that identifies you.

That is why you are not greeted by a consent banner. A banner exists to ask permission for things stored on your device that are not strictly necessary, and a cookie that keeps a site from being knocked over is strictly necessary.

A cookie is a small text file a website asks your browser to keep and to send back on later visits. It is how a site remembers something between one page and the next - typically that you are signed in. Local storage does a similar job, but the data stays in your browser and is never sent to the server unless the page decides to send it. This site sets no cookies at all; it uses one item of local storage, for a preference you chose yourself. The only cookie you will pick up here is Cloudflare’s, described in the next section.

This site runs on a machine at my house rather than with a hosting company, and the domain is proxied through Cloudflare - so my home broadband address is not published in DNS, and the constant automated scanning any public site attracts is absorbed before it reaches me. Your browser therefore connects to Cloudflare, which passes the request on.

That means Cloudflare can set cookies of its own on this domain. Which ones depends on what it decides about a request, but the ones to expect are:

__cf_bm

Tells automated traffic apart from real browsers. It holds no personal information and cannot be read across sites; it expires after about 30 minutes.

cf_clearance

Set only if you are shown a security check and pass it, so that you are not asked again on the next page.

These are Cloudflare’s standard security cookies, not analytics or advertising, and Cloudflare does not use them to build a profile of you or to follow you to other sites. They are strictly necessary for keeping the site reachable, which is why they need no consent banner. What Cloudflare does with the traffic itself is in the Privacy Policy.

The front page can be read two ways: as a 3D scene you scroll through, or as a plain page with the same words in it. There is a button to switch, and switching is worth remembering - being put back into a WebGL scene you deliberately left would be irritating.

So one value is written to your browser’s local storage, under the name jg:view-mode. Its content is the word scene or the word flat. That is the whole of it.

It is not a cookie and it is never sent to my server - local storage stays in the browser unless a page deliberately transmits it, and this one does not. It holds no identifier, cannot be read by any other site, and tells me nothing, because I never see it. Clearing your site data removes it and the page simply decides again.

The page also decides on its own to show you the plain version if your device cannot run WebGL, or if you have asked your system for reduced motion. Neither of those checks stores anything.

This site uses Umami, a privacy-focused analytics tool that I run on my own hardware rather than handing your visit to an analytics company.

Umami is cookieless. It stores nothing on your device, sets no identifier, records no personal information and cannot follow you to other websites. It counts page views and keeps rough aggregates - which pages are read, which site a visit arrived from, roughly which country and what sort of device, and how quickly pages loaded for you.

It also counts one action: sending the contact form. That is a count of events, not a record of who did it - your name, email address and message go to my inbox by email and never near the analytics database. The Privacy Policy covers what happens to those.

If I ever add something that genuinely does track you - advertising or third-party analytics - I will ask for your consent first, and you will be able to say no.

Almost nothing on this site comes from another company. Fonts are downloaded when the site is built and served from this domain rather than fetched from Google while you read, and every image is served from here too.

The one thing loaded from elsewhere is the Umami script described above, which comes from analytics.jdg.one - a separate domain, but one I own, on the same machine. That domain is proxied through Cloudflare too, so the same security cookie can be set against it. No other company sees your visit.

Every browser lets you view, block and delete cookies and site data, usually under Privacy or Site settings. In the case of this site there is almost nothing for those controls to find: blocking cookies here loses you nothing, though it may get you shown Cloudflare’s security check more often.

Guidance for each browser is on aboutcookies.org.

For everything else I do with personal information, see the Privacy Policy. Any questions about this page can go to [email protected].