Privacy Policy

This site does not ask you to create an account, and it does not sell or share visitor data with advertisers. The only personal information it handles is what you actively type into a form — and in most cases that goes straight to a third party (Substack, Stripe, or your own email program) rather than to us.

When analytics is switched on, this site uses PostHog to count page views and a small number of named events — for example, that someone submitted the newsletter form and which part of the page it was on. It is configured deliberately:

• Autocapture is off. PostHog is not permitted to record arbitrary clicks or the contents of form fields. Only the specific events the site defines are sent.
• Do Not Track is respected. If your browser sends a DNT signal, no analytics events are recorded.
• Event data excludes your email address. The newsletter event records that a signup happened and where on the site it happened — never the address itself.
• Analytics uses browser storage (a cookie plus local storage) to recognise a returning browser across page loads.

Analytics is only active when the site has been configured with a PostHog key, and then only after you have accepted it. Nothing is loaded and no analytics storage is written until you do.

Analytics is not currently switched on for this site, so there is nothing to opt in or out of. No analytics cookies or storage are being set.

The newsletter is Dinesh’s Substack. When you enter an address and submit the form, the site opens Substack’s own subscribe page in a new tab with your address pre-filled; you complete the subscription there, under Substack’s privacy policy. Your address is not stored on this site.

Payments are handled by Stripe Checkout. When you contribute, this site sends Stripe the amount and whether the gift is one-time or recurring, then redirects you to a page hosted by Stripe. Card numbers are entered on Stripe’s page and are never transmitted to or stored by this site. Stripe’s handling of that data is governed by Stripe’s privacy policy.

The contact and speaking-request forms do not submit to a server. They assemble a message and open it in your own email program, which you then send yourself. That means the contents reach admin@dineshdsouza.com as an ordinary email, and are retained in that mailbox the way any email is. Nothing you type into those forms is recorded by this website.

Episodes, trailers, and interview clips play through YouTube’s embedded player. On most of the site the player only loads after you click play; on an individual episode page it loads with the page. Once it loads, YouTube can set its own cookies and sees your IP address, under Google’s privacy policy.

Some artwork — book covers and video thumbnails — is served from Amazon and YouTube rather than from this site, so those hosts receive your IP address when the images load.

Typefaces are downloaded from this site’s own domain. They are bundled at build time rather than fetched from Google Fonts, so viewing a page makes no request to Google for fonts.

• Cart. If you add an item to the cart, the item’s name, quantity, and display price are kept in your browser’s local storage so the cart survives a reload. This never leaves your device except as part of a checkout you start.
• Analytics. As described above, and only when analytics is configured and you haven’t enabled Do Not Track.

Clearing your browser’s site data removes both.

The site is hosted on Vercel, which processes standard web server request logs (including IP addresses) in order to deliver pages and protect against abuse. See Vercel’s privacy policy.

This site is general-audience commentary and is not directed at children. It does not knowingly collect personal information from children.

To ask what is held about you, to request deletion, or to raise anything else about this policy, write to admin@dineshdsouza.com, or use the contact page. Because this site stores so little, most requests will concern data held by Substack, Stripe, or YouTube, and we will point you to the right place.

This page is maintained alongside the site’s code, and the date at the top reflects the most recent substantive change to the practices described here.