Cookies

Not for analytics, not for advertising, not for sessions, not for preferences, and not for the account. No response from this site carries a Set-Cookie header, and nothing in its code writes one. No third-party script runs here that might set one on the way past, because no third-party script runs here at all.

This is why you have not been asked to accept anything. A consent banner exists to obtain permission for cookies that are not strictly necessary; with none of any kind, a banner would be a click demanded for no reason, standing between a reader and an Act.

Three values, at most, and only once you have done the thing that creates each one. They live in your browser’s local storage:

The first is written when you press the theme button. The second is written when you enter an email address to keep follows, bookmarks and notes, and it is what lets the site greet you and show you your own lists on the next visit without asking again. The third is a short list the site keeps so it can mark what the collection has picked up since you were last here.

Local storage is not a cookie, and the difference is the part that matters rather than a technicality: a cookie is attached to every single request your browser makes to this site, so the server sees it whether or not it needs it. None of these is ever attached to anything. They are read by the page itself, on your device. The theme and the seen-list are never transmitted at all. Your address is sent only when a request genuinely needs to know whose list to touch — opening the account panel, following a section, saving a note — and never on an ordinary page view.

This is also why the site is fast. Because nothing identifying rides along with a page request, every page can be cached and served from the edge, which a cookie would have made impossible.

Clearing your browser’s site data removes all three. That signs the account out on this device and returns the site to the light theme, as it opens for anyone who has never pressed the button. It does not delete the account itself — entering the same address again brings the lists back. To delete the account and everything in it, use the delete button in the account panel, which is described in the privacy notice.

Page views are counted, and the counting is deliberately built so that no cookie or identifier is needed: a counter for that kind of page is incremented, and nothing is written about who opened it. This holds whether or not you have an account — the counting has no idea either way, and the two are never joined. The cost of that choice is that this site can report views and cannot report visitors. That is the right trade for a site people read while drafting.

The full description is in the privacy notice.

Every provision here links to the regulator’s own page or file — the income-tax department, the Reserve Bank, SEBI, the Ministry of Corporate Affairs and so on. Those are other people’s websites, they set their own cookies, and this notice does not reach them. Opening an official document puts you on that regulator’s site under its terms, not these.