Cookies, and why there is no banner

The short version

No cookies. No local storage. No session storage. No tracking pixel, no advertising tag, no embedded video, no social widget, no font loaded from somebody else's server. Visits are counted, without storing anything on your device, and the section below says how and how to opt out.

This is not a claim I would like to be able to make. It is a property of how the site is built, and it is checked automatically every time the site is built, because a claim that is checked once decays and a claim that is checked always does not.

Why that means no banner

The rule that produces cookie banners is about storing information on your device, or reading information already there. If nothing is stored and nothing is read, there is nothing for you to agree to, and a banner asking you to agree to nothing would be theatre.

That is a statement about this site's use of your device and nothing more. How I handle information you deliberately send me, such as through the contact form, is a separate question with a separate answer, and it is in the privacy notice.

The two things that contact anybody else

The check on the contact form

The contact page carries a Cloudflare Turnstile widget, which is what establishes that a form submission came from a person rather than from a script. It is on that page only.

Two things are true about it and both matter:

• It makes a request to Cloudflare. Your browser contacts challenges.cloudflare.com and brunhild.challenges.cloudflare.com. Cloudflare therefore receives your IP address, as any server does when you connect to it.
• It stores nothing on your device. Measured on the running site on 24 August 2026, with a clean browser profile: no cookie from any origin, no local storage, no session storage, on the contact page and on a page without the widget.

So the widget is a third party request rather than third party storage. Those are different things and the difference is the whole reason this page can say what it says.

Counting visits

Every page counts visits with Cloudflare Web Analytics, so that I can see which pages people read and whether they load quickly. The same two things are true of it:

• It makes a request to Cloudflare. Your browser loads a small script from static.cloudflareinsights.com and sends a short report to cloudflareinsights.com when the page has loaded and again when you leave it. Cloudflare therefore receives your IP address, as any server does when you connect to it.
• It stores nothing on your device. In Cloudflare's own words, it "does not use any client-side state, such as cookies or localStorage", and it does not fingerprint you.

If your browser sends Global Privacy Control or Do Not Track, the script is never loaded and your visit is not counted. Nothing is stored to remember that choice, because your browser is already remembering it for you. The privacy notice says how to turn either on.

If you book a call

The Book a call button in the header does not lead to a page on this site. It goes to Microsoft Bookings at bookings.cloud.microsoft, which is Microsoft's booking system rather than mine, and it is the one link here that takes you somewhere with different rules.

What that page stores on your device is Microsoft's decision. I have not measured it the way the rest of this page is measured, so there is no list here rather than a list I cannot back. Microsoft's own account of it is in its privacy statement at privacy.microsoft.com.

Everything else on this page is still true. Nothing is stored on your device by dalaric.com itself, and you only reach the booking page by choosing to. But it carries the Dalaric name, so saying nothing about it would be the sort of technicality this page exists to avoid.

If you would rather not, the contact form reaches me just as well, and so does the phone.

How to check it yourself

Every figure on this site is meant to be checkable in about thirty seconds, and this one is no exception.

Open any page here, press F12 to open your browser's developer tools, and look under Application or Storage. Cookies will be empty, Local Storage will be empty, and Session Storage will be empty. Do the same on the contact page, which is the one carrying the widget, and you will find the same three empty lists.

If you ever find otherwise, tell me and I will treat it as a fault rather than as a difference of opinion.

What would change this

Adding an embedded video, a font from somebody else's server, a chat widget or a social button would each break some part of what this page says. None of those is planned. Visit counting went in before the site was published, and it stores nothing, so it changed what this page lists rather than what it promises. If one is ever added, this page changes first and the build stops if it does not.

If it ever does change, clients get an email about it before it happens rather than a quietly edited page. That is the same commitment the privacy notice makes, for the same reason: a promise you can only verify by re-reading a page you have no reason to revisit is not much of a promise.

This page carries a dated note of what changed and when, most recent first, in the same way. Today there is nothing to list, which is the entry.

Client sites, and the two answers are different

The websites I build set no cookies either, one page or thirty, which is why they carry no banner. Same property as this page describes, for the same reason, and it is a property of how they are built rather than a setting somebody has to remember.

A larger site is likelier to want something that would break that. An embedded map, a video player, a font from somebody else's server or a chat widget each bring cookies with them, and then that site needs a banner like everybody else's. None of it is forbidden and some of it is genuinely worth having. What happens is that I say so before it goes on rather than after. The brochure websites page says the same thing where somebody buying one would read it.

A WordPress site on a care plan is a different answer

If your site is WordPress, this page is not about it, and you should not read it as though it were. WordPress sites run plugins, and plugins set cookies. An analytics plugin, a shop, a booking system, a chat widget, an embedded map or video, a consent banner that is itself a cookie: any of those can arrive with a plugin you install on a Tuesday afternoon, and several of them are the reason you wanted the plugin.

That is your call to make and yours to disclose. You own the site, you choose what runs on it, and you are the one the rules apply to. What I do is keep the thing patched and running. I do not audit what your plugins store on your visitors' devices, and I would be overstepping if I decided which ones you may have.

What you get from me is an answer when you ask. If you want to know what your site is actually setting, ask and I will go and look rather than guess, and I will tell you plainly whether you need a banner. That is a better use of half an hour than either of us reading a plugin's marketing page.