Cookie Policy

A cookie is a small file a website asks your browser to keep. This site also uses two related browser features — local storage and session storage — which do the same job without travelling back to our server. All three are listed here, because from your side of the screen the difference does not matter: something is being kept on your device.

There are exactly two groups of them on this site, and only one of them is optional.

Two values, both written by this site, both readable only by this site. They carry no identifier for you and are never sent to anyone else.

These cannot be switched off, because one of them is the record of your cookie choice. Switching it off would mean asking you the same question on every page.

If you accept analytics on the cookie notice, this site loads Google Analytics 4 and Microsoft Clarity. They count visits, show which pages get read, and show where people give up — which is how the course pages get improved.

Until you accept, none of these exist. The scripts are not requested, so no cookie is written and no data reaches Google or Microsoft. This is enforced in the code rather than promised in prose: components/analytics.tsx renders nothing at all until the consent record says yes.

Advertising is switched off inside Google Analytics for this site: ad storage, ad user data and ad personalisation stay denied even for visitors who accept analytics. We run no advertising or remarketing pixel, which is why the notice offers no marketing category — there is nothing there to decide about.

The contact page can show a Google map and some course pages can show a YouTube video. Neither loads on its own.

• The map sits behind a button. Nothing is requested from Google until you press it.
• Videos are embedded through YouTube's no-cookie domain, which holds back its storage until you press play.

Once you load one, that provider receives your IP address and may set cookies under its own policy — Google's for the map and the player. We cannot see or control those, which is why they are loaded only on your action.

Use the Cookie settings link in the footer of any page. It reopens the notice with the switches showing, and your new answer takes effect immediately.

Turning analytics back off does more than stop the next page load: the cookies the two products already set are deleted and the page reloads, so nothing that was allowed under the old answer keeps recording under the new one.

You can also block or delete cookies in your browser settings. Doing that for the two strictly necessary keys is harmless — the site works, it will simply ask about cookies again.

We never treat scrolling, or carrying on reading, as consent. Nothing optional loads until you press a button on the notice.

This page is the full inventory, and it is updated in the same change as the code. If a tag is ever added, it appears in the table and the notice asks you again rather than assuming your old answer covers it.