Cookie notice

What is stored, exactly

In the strict sense this website sets no cookies at all — no response from it carries one. What it can keep are two entries in your browser's local storage, which the same rules treat as they treat cookies, so we ask the same way. This is the complete list:

Neither entry is ever sent to us. Unlike a cookie, local storage is not attached to the requests your browser makes; both stay on your device and are read only by the page in front of you.

How visits are counted

To know how many people read these pages, and which ones, each page sends one short record to this site's own server — the address the page itself came from, never another company's. The record holds the page's address, the name of the site that linked you here (its name only, not the page), the language, whether the window is phone-, tablet- or desktop-sized, and the family of your browser and operating system.

• Your IP address is not kept. The server uses it once to look up the country and city, then discards it; the stored record shows only those two.
• A visitor code that lasts one day. To count each visitor once a day, the server derives a code from the date, your address and your browser's self-description (its user agent) under a secret key. The code changes every midnight, so the same person on two days counts as two people, and nothing is stored on your device.
• Kept for 90 days in the site's own Microsoft Azure account — the provider that already delivers these pages — and read as daily totals.
• Not being counted needs no button. A browser that sends Global Privacy Control or Do Not Track is not counted at all, and neither is a visit with JavaScript switched off.

What is not here

Most cookie notices are long because of what the site loads from other companies. This one is short because this site loads nothing from anyone:

• No tracking analytics. No analytics service from another company, no heat maps, no session recording, no A/B testing — the counting described above is all there is.
• No advertising. No retargeting pixels, no social-network buttons, no audience matching.
• No third-party origin at all. Fonts, scripts, styles and images are all served from this host; there is no embedded video, map or chat widget. Our own release check fails if a page ever loads anything from another origin.
• No fingerprinting, and no identifier that outlives the day it was made.

One thing no website can avoid: the pages are delivered by Microsoft Azure's content network, and like any web server it has to process your IP address in order to answer a request. The visit counting described above is the only thing we have added on top of that.

Your choice, and how to change it

Accept allows the theme to be remembered. Reject allows nothing beyond the record of the rejection itself, and removes a remembered theme on the spot. Both buttons are the same size and either closes the question; nothing on the site is withheld whichever you press.

You can change your mind at any time with Cookie settings at the foot of every page. Your answer is kept for twelve months and then asked again. Clearing this site's data in your browser removes both entries, after which the question simply returns.

Who is responsible

This website is operated by the company below, which is the data controller for it. Questions about this notice, or any request about your personal data, go to the address shown.