Privacy

The short version

This site collects no personal information from you. There is no form here that sends us your data. The newsletter runs on Substack: when you click Subscribe you go to Substack and enter your address there, under Substack's privacy policy rather than ours. We also count how the course is being read, using our own Cloudflare account rather than a third-party analytics service, without cookies and without anything that identifies you. We do not track you across the web and we do not sell anything to anyone.

The long version, in plain English

What we collect

• Nothing personal through this site. Every Subscribe button links out to our Substack publication. If you subscribe, Substack receives your address and manages the list; we never see it or store it here.
• Hosting signals from Cloudflare, which serves this site. Like any host, Cloudflare processes visitor IP addresses in order to deliver pages and block attacks; what it shows us is only aggregated counts, meaning page requests, response codes, and broad geographic regions. It sets no cookies here, and nothing it hands us identifies you.
• Anonymous product events, so we can see how the course is working and make it better: which chapters get reached, whether you tried the Build Plan or Playbook, and which buttons get clicked. These are first-party, written to our own Cloudflare account and never to a third-party analytics service. They carry no cookie, no IP address, and nothing personal. Each event does carry a random id that lets us tell one reading session from another; your browser keeps it for the life of that tab and forgets it when you close the tab, so it cannot follow you to another visit, another tab, or another device. If your browser sends a Do Not Track or Global Privacy Control signal, we record nothing at all.

If you email us

If you write to us with a question or a correction, we receive your address and whatever you send. That mail sits in our inbox with Google, which runs it under its own privacy policy, the same way the newsletter sits with Substack. We use it only to reply. We do not add you to the newsletter and we do not pass on what you send. Ask us at [email protected] and we will delete it.

Why there is a newsletter

So we can write to you: a note when new chapters land, and the occasional one when we publish something else worth your time. It is delivered through Substack, which owns the subscriber list and the sending, and it is the same publication the flagship site uses.

Where things live

Your subscription, meaning your address and the fact that you signed up, lives with Substack under their privacy policy. This site holds none of it, and it has no database of its own. (Data, where information lives covers what that choice means in practice.)

Build Plans you fill out at /course/build-plan never leave your device. The form auto-saves to your browser's local storage so you can come back, and the export actions (PDF, email, Markdown) all happen locally. We do not store your Build Plan anywhere on our servers, by design.

Your course progress (which chapters you have opened and marked done) works the same way: it lives only in your browser's local storage, never on our servers, and is never tied to you across devices.

How long we keep it

Apart from any mail you send us, we keep nothing about you, so there is nothing on our side to hold or delete. Mail you send sits in our inbox until we delete it, and you can ask us to remove it at any time. Your subscription is yours to manage on Substack.

Who we share it with

No one. We do not sell, rent, lease, or trade anything about you. Ever. Mail you send us stays with us and goes no further; we will not add you to the newsletter or pass your note to anyone else.

Your rights

• Manage or delete your subscription. Use the controls in any Substack email, or your Substack account, to change or remove your address. Substack is the controller for the list.
• Unsubscribe. Every Substack email carries a one-click unsubscribe link.
• Ask us anything. Email [email protected] and we will answer within a few days, though the subscription data itself lives with Substack.

How to reach us

[email protected] is the address we read for anything on this page. You can also message Shivali on LinkedIn or Girish on LinkedIn.

If this policy changes

We will update the date at the top of this page and note what changed. The current version of this policy always lives at /privacy. Latest change (August 10, 2026): the newsletter moved to Substack, so this site no longer collects or stores any email address. We deleted the signup form and the key-value store behind it, and rewrote every section that described them.

If we have a breach

The site itself stores nothing about you, so there is no store here to breach. The only personal data we control is whatever you have sent us by email, which lives in Google's mail service under its security. If that is compromised in a way that affects you, we will tell you directly and promptly, within 72 hours of knowing, with what happened, what was exposed, and what you should do. That duty sits with us rather than with our vendors, and we keep a short written plan for it so the first hour is not spent deciding who does what. The subscriber list is Substack's to hold and to answer for, and we would confirm in writing what they are doing.