Cookie policy.

What gets stored

• Your theme choice (light / dark) — kept locally in the browser. It is not a cookie and it is never sent anywhere.
• Portfolio view and return-to-list preferences — stored in sessionStorage for the tab session. They help you return to the place you were viewing; they are not used for tracking or sent with the form.
• An unsent form draft, ticks in guide checklists and text in the interactive editing example stay in the open page's memory. Draft message text is not saved in localStorage or sessionStorage and is not sent before you press the submit button.
• Visit statistics run without cookies: the counter is part of this domain, writes no file, and leaves no identifier that could recognise you on a later visit or on another site.
• A login cookie — only inside the admin panel, and only once signed in. An ordinary visitor never receives one.

What is not here

No advertising pixels, no remarketing, no heatmaps, no session recording. There are no embedded social widgets setting their own cookies the moment you arrive either.

You will not see a cookie consent box here either — not because it was forgotten, but because there is nothing to ask about. Consent is needed when a site stores something it does not need in order to work; this one stores nothing of the sort. Until August 2026 it ran Google Analytics, which set the _ga and _ga_* cookies. That was removed and replaced with a cookieless counter.

How to switch it off

Every browser can block or clear site data in its privacy settings, usually per individual site. Blocking it does not break this site: you lose the remembered theme and portfolio return preferences. Closing the tab also clears sessionStorage, although restoring the browser session may restore that data.

If you would rather your visit did not reach even the aggregate counter, a script-blocking extension or your browser's built-in tracking protection is enough. The site works normally either way.