Cookie policy
A cookie is a piece of data a site stores in your browser so it can remember something from one page to the next.
This site's analytics use no cookies. The theme preference and form protection serve separate purposes, described below.
How the language works without a cookie
From the address. / is Spanish and /en/… is English, and the language button
changes the URL. There is nothing to remember between pages.
Until July 2026 this site wrote a NEXT_LOCALE cookie holding the language.
Nothing read it, so it is gone.
The analytics use no cookies either
I do measure visits, because I want to know what gets read and what does not. I use Matomo (opens in a new tab) on a server of my own, not a third-party service that makes its living from the data.
It is configured not to write cookies (disableCookies), so no identifier is
left in your browser. Nothing follows you from one site to another, and your
visits here are never joined up with what you do anywhere else.
What it does do, with the exact detail: to work out whether the page you just opened continues the visit you started five minutes ago or is a new visit, Matomo computes a fingerprint on the server from your IP address and your user-agent string — that is, from the same things your browser sends any site when it asks for a page. The window in which it uses that is 30 minutes. Past that it stops counting you as the same person: come back tomorrow and Matomo records a new visit and does not flag it as returning.
That is what the system does, which is worth not confusing with what would be impossible. Each visit's fingerprint is stored, so two records sharing one could be compared afterwards. Nobody does that here and nothing is set up to, but telling you it is impossible would go further than I can support.
So the fingerprint is not there to follow you. It is there to avoid counting you five times for reading five pages in a row.
The IP address is stored with its last two octets masked: arrive from
203.0.113.47 and what is kept is 203.0.0.0. That does not make it anonymous,
and I am not going to tell you it does: it remains personal data and is treated
as such.
Theme preference
When a page loads, the site checks the colour preference reported by your
browser (prefers-color-scheme) to show the light or dark theme. If you choose
one from the control in the masthead, it stores only the theme key in
localStorage, with the value light or dark, and reads it on later visits to
keep your choice.
That preference stays in your browser: it is not sent to the server, combined with other data or used for measurement, advertising or profiling. You can remove it by clearing this site's data in your browser.
Form protection
Cloudflare Turnstile runs when you submit a valid contact or newsletter form. It examines browser and connection signals to help detect automated abuse and may ask you to select a checkbox. The server checks the result before accepting the submission. This security check is separate from audience measurement.
The check can also use browser local storage on Cloudflare's origin. Removing the form or finishing the challenge does not guarantee that this storage is cleared; we do not use it to measure the audience.
We configure Turnstile without pre-clearance, which would issue an additional
cf_clearance cookie. That does not mean the check accesses no device information.
Cloudflare describes its processing and detector improvement in the
Turnstile privacy notice (opens in a new tab).
We do not use advertising cookies. The Matomo configuration described above measures audience activity without cookies; the theme preference follows your choice. The privacy policy describes the providers and data processing.
Clearing stored site data
If you visited the old WordPress site, your browser may also retain data from that version. You can inspect and clear this site's stored data in your browser: