Privacy
This site runs no analytics and collects nothing about you. Some posts embed social media cards, which are the only third-party frames here.
Short version: this site collects nothing about you. There is no analytics, no tracking pixel, no advertising network, no comment system, no newsletter, and no account to create. Nothing on these pages asks you for a name, an email address, or anything else, because nothing here has anywhere to put it.
The one exception is embedded social media posts. Where a post quotes something I published on a social network, the card is loaded from that network, and that network can see you when it loads. This is described in full under external links and embeds.
Cookies
This site sets no cookies of its own, and nothing here reads one. The social media embeds described below are frames belonging to those networks, and a network may set cookies inside its own frame under its own domain — I cannot read those and they are not mine. Every page without an embed is cookie-free. Your browser may keep its own cache of the pages and fonts it downloaded, which is ordinary browser behaviour and stays on your device.
Analytics
None. No measurement script of any kind loads. I have no dashboard, no visitor counts, and no way to tell one reader from another.
Comments
None. No comment widget loads and no identity is requested. If you want to respond to something I have written, the contact page lists the places to do it.
Hosting and server logs
The site is hosted on Vercel, which serves the pages and keeps the standard operational request logs a web host keeps — IP address, timestamp, requested URL, user agent — for a short period, to run and protect the service. I do not query, export, or analyse those logs, and they are governed by Vercel's privacy policy. Fonts are served from this domain rather than a font CDN, so loading a page does not tell anyone else that you did.
External links and embeds
Posts link out to other sites — GitHub, Sitecore documentation, Medium, LinkedIn. Following a link puts you on someone else's site under their privacy policy, not this one. Embedded images are served from this domain unless a post says otherwise.
Some posts embed a social media card — usually the original version of something I published elsewhere. These are the only third-party frames on the site. When such a post loads, your browser fetches the card from that network, so the network sees your IP address, the page you are on, and — if you are signed in to it — very likely which account is looking. That happens whether or not you click it. I get none of this back; it goes to the network, under its own privacy policy.
Today the only one in use is LinkedIn, on a single post. If I embed from another network, it can only be one whose origin has been added to the site's content security policy, and that policy lets these frames paint and nothing more: an embed cannot run script in the page around it, or reach anything else on this domain. Blocking third-party cookies — the default in Safari and Firefox — limits what any of them can join up. A content blocker, or simply not opening a post that carries one, avoids them entirely.
Feeds and machine-readable copies
The RSS feed, the sitemap, and the llms.txt index are static files. Requesting any page with an Accept: text/markdown header returns the same content as markdown. None of these is logged or treated differently from an ordinary page request.
Your data
There is no data of yours here to access, correct, or delete, because none was collected. If that ever changes, this page changes with it and the change will be visible in the site's public git history.
Contact
Questions about this page can go to any of the channels on the contact page.