Cookie policy

• No cookie is set by either site.
• Nothing is written to local storage, session storage or an in-browser database.
• There is no analytics, no tag manager and no third-party script of any kind, so nothing else gets the chance to set one either.
• There is no login and no preference to remember, because there is nothing to log in to and nothing to configure.

The rule people mean when they say "cookie law" — Article 5(3) of the ePrivacy Directive, in Italy Article 122 of the Codice in materia di protezione dei dati personali — attaches to the act of storing or accessing information on a user’s device. This site does neither, so there is no consent to collect.

A banner asking you to agree to nothing is not caution, it is noise, and it trains people to click through the ones that matter. If that changes, the banner arrives with the thing that made it necessary.

• Your browser caches pages and images, as it does for every site. That is your browser’s own storage, under your control, and nothing here reads it.
• The web hosts log that a request arrived. That is a record on their servers, not storage on your device, and the privacy policy covers it.
• Other sites you reach from here — GitHub, PyPI, npm, RubyGems, Ko-fi — set their own cookies once you are on them. A link to a site is not an embed of it: nothing of theirs runs until you click.

• Privacy policy

Effective from 16 September 2026. Adding analytics, an embedded Ko-fi widget, a comment system or anything that remembers you between visits would re-open this question, and this page and its date would change first.