Cookies

There is no cookie banner

Not as a stance, but because there is nothing to ask you about. This site sets no analytics cookies, no advertising cookies and no third-party cookies of any kind. Browse it and your browser stores nothing.

You can check that rather than take our word for it: open your browser's developer tools on this page and look at storage. It is empty.

What is set, and when

Three cookies exist. None of them appears on a page you are only reading — the first two are set when you open a page carrying a form, which on this site means the contact form, and the third only after someone signs in to the administration area.

Cookie	Purpose	Lifetime
.AspNetCore.Antiforgery.*	Protects a form submission against cross-site request forgery	Session
.AspNetCore.Mvc.CookieTempDataProvider	Carries the confirmation message across the redirect after you submit	Session
errordock.admin	Keeps an administrator signed in	Until sign-out

The administration cookie is HttpOnly, SameSite=Lax and secure-only in production. All three are strictly necessary in the sense the ePrivacy rules use: each one exists to deliver something you asked for. None is used to profile you, none is shared, and none follows you to another site.

No third-party requests at all

The reason the list is this short is architectural rather than editorial. The site's Content-Security-Policy is default-src 'self': the site uses system fonts, there is no tag manager, no analytics script, no embedded video and no CDN. A third party cannot set a cookie here because a third party is never contacted.

Blocking them

You can block cookies for this domain in your browser and every page will still render — the site is server-rendered and works without JavaScript. Form submission is what breaks: without the antiforgery cookie the contact form will refuse the post. That is the protection working, not a fault.

Cookies in the product

This page covers the marketing website only. The ErrorDock application is a separate deployment on its own origin, and the SDKs you install in your own application do not use cookies to identify users — identity there is an identifier you set and control, which is covered in Users and identity.