What this site collects.

There is no Google Analytics on this site, and no analytics of any other brand. No advertising pixel, no Meta pixel, no LinkedIn insight tag, no heatmap recorder, no session replay. Nothing on any page profiles you, follows you to another site, or builds an audience list you can later be advertised to.

The site sets no cookies and stores nothing in your browser. It reads nothing back from your browser either — no local storage, no session storage, no fingerprinting.

Every font, stylesheet, script and image is served from this domain. That is deliberate: web fonts used to be loaded from Google's servers here, which quietly handed Google the address of every visitor who read a page. They are hosted here now, so that request never leaves.

Where a video appears — on the videos page, or inside one of two blog posts — it is a picture and a play button until you press it. Nothing is requested from YouTube, not the player, not the thumbnail, not your address, unless you choose to watch.

The calendar on the contact page is Calendly, embedded in a frame. It loads when you open that page, which means Calendly can see that a browser opened it. If you go on to book, the form collects your name, your email address, your timezone, anything you write in the message field, and the email address of anyone you add as a guest. Calendly receives all of it, and so do we, as a calendar invitation and an email.

What we do with it afterwards is unremarkable: it stays in that inbox and that calendar, and we use it to have the conversation you booked. We do not add you to a mailing list, we do not sell or share it, and there is no marketing automation behind it — the site has no mailing list to add you to.

Calendly is a separate company with its own terms, and what it does with your details is governed by Calendly's privacy notice rather than by this page. The booking panel says the same thing at the moment you fill it in, because that is when it matters.

The assistant in the corner of every page answers questions about what we do, using the text of this site. It does nothing until you open it and type something.

When you send a message, it goes to a small service we run on Cloudflare, which finds the relevant passages from these pages and passes your question and those passages to a language-model provider to be turned into an answer. Your message reaches that provider. It is not stored by us: the service writes no log of conversations, and there is no database of them to read.

One thing is counted, and it is worth being precise about. To stop a single visitor flooding the service, it keeps a running count of requests. That counter is keyed on a salted one-way hash of the network address rather than the address itself, so what is stored cannot be turned back into who you are, and it expires after a day.

Treat the chat the way you would treat a first email to a stranger. Do not paste anything confidential into it — not because we are reading it, but because it is a conversation with a machine you have not met, and that is the sensible rule for all of them.

Wherever you live, you can ask us what we hold about you, ask for a copy of it, ask us to correct it, or ask us to delete it. In practice that means a booking: a name, an email address and whatever you wrote in the message. Write to shreyasdavework@gmail.com and say what you want done, and we will do it and tell you when it is done.

We have not set a fixed schedule for deleting old bookings, so we are not going to claim one here. Ask and yours is removed.

If any of this changes — a new tool, a new embed, anything that would make a sentence above untrue — this page changes with it, and the change is the point. A privacy notice is only worth reading if it describes the site you are actually on.