Legal
Privacy policy
What this site records when you visit, who records it, and for how long.
New What changed in this version
- You can now create an account to comment, with Google, Apple or a code sent to your email. Reading still needs no account.
- Signing in sets one cookie, only for people who sign in. Readers still get none.
- New sections:Accounts and sign-in,Comments and profiles,Emails and Deleting your account.
This site is a personal blog. You can read every page without an account. You only give your details if you choose to: by writing through the contact page, or by creating an account to comment.
The short version
- Readers who don't sign in get no cookies. Signing in sets one cookie that keeps you signed in, and nothing else.
- An account stores your email, your profile and your comments. Your email is never shown on the site or shared.
- Emails are only sent when you ask for a code, or for notifications you can turn off in one click.
- You can delete your account yourself, from your account settings.
- Anonymous page statistics are counted by this site itself, on its own server. Nothing is sent to a third party.
- Standard access logs, including your IP address, are kept for 14 days, then deleted.
- Your theme and recent searches stay in your own browser and never reach the server.
- Nothing is sold, and nothing is shared for advertising. There are no ads.
Server logs
Like every web server, this one writes a line for each request it answers: your IP address, the date and time, the address you asked for, the page you came from, your browser's name, and the result. These logs exist to keep the site running and to investigate abuse or errors. They are rotated daily and deleted after 14 days.
The application behind the site keeps its own log of requests, without your IP address. An address can include what you typed into search (for example /api/search?q=redis), so a search can appear in that log for up to 14 days.
Protection against abuse
A few actions are rate-limited to keep the site available: sending a message from the contact page, signing in, and the owner's own tools. To count requests, the server keeps a shortened form of the IP address for one minute, then forgets it. Ordinary reading is not rate-limited.
Page statistics
To learn which articles are read and what is hard to find, the site counts its own page views, on the same server that serves them. No analytics service is involved.
- No cookies and no local storage. Each visit is counted under a one-way hash that changes every day, so a visit is not linked to your visits on other days.
- No session recording. Your screen, mouse movements, keystrokes and clicks are not recorded.
- Do Not Track is respected. If your browser sends it, or Global Privacy Control, nothing is counted.
Page statistics are deleted after 400 days.
Messages from the contact page
When you send a message, the site stores your name, your email address and your message, with the time it was sent. It is used only to read and answer your message, and kept until the author deletes it.
Accounts and sign-in
You need an account only to comment, reply, mark a comment helpful or follow a discussion. An account stores:
- Your email address, to sign you in and to send the emails you chose. It is never shown on the site.
- Your profile: display name, username, and, if you add them, a short bio and a photo.
- Your settings: which sign-in methods are linked and which emails you want.
- The date you joined and the date you last signed in.
Signing in with Google or Apple
If you choose Google, Google sends this site your name, email address, profile photo and an account ID that recognises you next time. If you choose Apple, Apple sends an account ID, your email address (or a private relay address, if you choose to hide yours) and, the first time only, your name. This site never sees your Google or Apple password. The sign-in screen itself belongs to Google or Apple, under their own privacy policies.
Signing in with an email code
When you ask for a code, the site emails you six digits. Only a one-way hash of the code is stored. It works once, stops working after 10 minutes, and is cancelled after 5 wrong tries. The code is also in the email's subject line, so your phone can offer to fill it in.
The sign-in cookie
Signing in sets one cookie,[COOKIE NAME], that keeps you signed in for [30 days]. It can't be read by scripts, is only sent over HTTPS, and is deleted when you sign out. It is not used for anything else.
Comments and profiles
Comments are public. Anyone can see your display name, username, photo, the comment, when you posted it, how many people found it helpful, and your public profile page listing your comments. Your email address never appears.
- Review. Your first comment is checked by the author before others see it. After that, your comments appear straight away.
- Helpful votes. A vote is stored with your account so it counts once. Nobody can see who voted.
- Reports. If you report a comment, the author sees your report; the person you reported doesn't see who reported them. Reports are kept for [90 days] after they are dealt with.
- Posting limits. Posting is rate-limited like signing in, using the same one-minute shortened IP address described under protection against abuse.
- Editing and deleting. An edited comment shows that it was edited. A deleted comment's text is removed at once; if it had replies, a “This comment was deleted” line stays so the replies still make sense.
Emails
The site only emails you in these cases:
- Sign-in codes, when you ask for one.
- Replies to your comments and new comments in discussions you follow. On by default; turn them off in your settings or with the link in any of these emails.
- A weekly digest of new articles, only if you turn it on.
Emails are sent through [EMAIL PROVIDER], which receives your email address and the message in order to deliver it. Emails contain no tracking pixels and no tracked links.
Deleting your account
You can delete your account from account settings. Your email, profile, linked sign-in methods and settings are deleted at once, and from backups within [30 days]. Your comments stay, shown as “Deleted user”, so replies to them still make sense; delete them one by one first if you want them gone. To get a copy of your data, ask through the contact page.
What stays in your browser
Two small preferences are kept in your browser's local storage and never sent to the server: your theme (k13-theme) and the last five articles you opened from search (k13-recent).
Cookies
Readers who don't sign in get no cookies. If you sign in, the site sets the one sign-in cookie described above. The back office has its own cookies, used by the site's owner only. There are no advertising, analytics or third-party cookies, so there is no consent banner.
Google reCAPTCHA
When the site's spam protection is switched on, the contact page and the back-office sign-in pages show Google's reCAPTCHA box. Loading one of them sends Google your IP address and some details about your browser, under Google's privacy policy and terms. No other page loads anything from Google.
Who handles the data
- OVHcloud hosts the server that runs the site and keeps its logs, in Canada.
- Cloudflare R2 stores the images published in articles. Your browser asks this site for them, so your requests don't go to Cloudflare directly.
- Let's Encrypt issues the site's HTTPS certificate.
- Google and Apple, only if you choose to sign in with them.
- [EMAIL PROVIDER] delivers sign-in codes and notification emails.