We do not measure you.

Intelligent by Design runs no analytics, sets no cookie for readers, and builds no profile of anyone who visits. There is no Google Analytics, no Plausible, no PostHog, and no performance-monitoring script. Reading an article here is not recorded against you, because nothing is here to record it.

What follows is the detail, and it is short.

When you read an article

The site is served by Vercel, our hosting provider. Like any web server, theirs receives the requests your browser makes — the page asked for, your IP address, your browser’s user-agent string, the time — and keeps operational logs of them. We do not query those logs to study readers, and they are not joined to anything else. This is the irreducible minimum of serving a page over the internet, not a choice we made on top of it.

Content embedded from elsewhere

Some articles embed material hosted by other companies, and loading it means your browser contacts them directly. We cannot see that exchange, and their policies govern it, not ours:

  • Posts from X (Twitter), where an article quotes one.
  • YouTube videos, requested through youtube-nocookie.com, the privacy-enhanced host that does not set a tracking cookie unless you press play.

Our own films are not in that list. They are served from our own storage and play without contacting anyone else. Typefaces are not in it either: the fonts are compiled into the site at build time, so no request ever goes to a font service while you read.

The feed

/feed.xml is a plain file. Subscribing to it tells us nothing — there is no list to join and no address to give us, and we could not count subscribers if we wanted to.

Content Studio

Our authoring tool at /content-studio is password-gated and used only by us. It sets one cookie, a session token, which exists to keep an author signed in and does nothing else. If you are reading the public site you never receive it. Drafting there sends article text to Google’s Gemini models from our server; no reader data is involved, because the tool never sees any.

Your YouTube account, if you connect one

We use Google’s OAuth to publish our own films to our own YouTube channel. The authorisation is granted by us, for our channel, and the resulting credential is used for nothing but uploading those films and their captions. Information received from Google APIs is handled in accordance with the Google API Services User Data Policy, including its Limited Use requirements. We do not ask readers to connect a Google account and have no way to use one.

What we never do

We do not sell, rent, or trade information about readers. We do not run advertising, so there is no ad network here to pass anything to. We have no reader database to breach.

Asking us about this

Write to mathurutsav@gmail.com. If you want the server logs for your IP address removed, say so and we will ask our host to purge them. We will tell you plainly what is and is not possible rather than quoting a process at you.

Last updated 25 October 2026.