Cookie policy

Cookies in use today: none

As this page is written, no cookies are set, no tracking pixels are loaded, no third-party scripts run, no fingerprinting is performed, and nothing capable of identifying you is stored. Every page is pre-built HTML served from a single domain, and it reads exactly the same whether your browser accepts cookies or blocks all of them.

That is not a temporary state while something is being configured. A reference site of tables and dates has no functional need for cookies — there is nothing to log in to, no basket, and no preference worth remembering — so none are used.

One thing is written to your browser, and it is worth naming rather than glossing over. The framework this site is built with remembers your scroll position as you move between pages, so that going back returns you where you were; it keeps that under «sveltekit:scroll» and «sveltekit:snapshot» in sessionStorage. That is purely functional — it holds a position on a page, not anything about you — and sessionStorage, unlike a cookie, is never attached to a request, so it never leaves your browser and reaches neither us nor anyone else. Your browser discards it when you close the tab.

If analytics is switched on

The one thing that would change this is audience measurement. If Google Analytics 4 is enabled, a consent banner appears at the foot of the page and asks before anything loads. Decline, or ignore it, and no analytics script is fetched and no analytics cookie is set. Accept, and GA4 sets its own first-party cookies — typically «_ga» and a per-property «_ga_…» cookie, used to tell visits apart and count returning readers, with a lifetime of up to two years.

Before that happens, this page will list each cookie by name, purpose and lifetime. The rule holds in that order: this page names a cookie first, the cookie is set second. You will not find one here that is not written on this page.

The consent record

If the banner ever appears, your answer has to be remembered or you would be asked again on every page. It is stored in your own browser, in localStorage, under the key «cc-consent», with the value «granted» or «denied».

That record is written only when you press Accept or Decline — arriving and reading without answering leaves no consent record at all. It is not a cookie: it stays in the browser and is never attached to a request, so it is never sent to this site or to anyone else. It holds your choice and nothing more — no identifier, no timestamp, no history.

Changing your mind

Withdrawing consent has to be as easy as giving it, so there is a button for it here. It erases the stored choice; if audience measurement is switched on, the banner will ask again the next time you load a page, and until you answer nothing is loaded.

Clearing site data for costacaddie.com in your browser settings does the same thing and more, removing anything else stored along with it. Browsers also let you block cookies and storage for a site outright; doing so here costs you nothing, because no part of this site depends on either.

Questions about any of this: ferran@crisalide.io.

Last updated 2 Aug 2026