Privacy
What this site collects, stores, and shares — which is almost nothing.
This is a personal site: prose, photographs, a CV. It is built as static files and served as-is. It runs no analytics, sets no tracking or advertising cookies, embeds no third-party scripts, and loads no fonts or other assets from anyone else's servers. Reading requires no account and sends nothing; the one interactive feature — leaving a note on an essay — is strictly opt-in and described in full below. Nothing here is for sale. The site is built to know as little about you as it can. What follows is the full account of the little that remains.
What the site stores in your browser
At your request only, the site saves functional state in your browser's local storage: the color theme and reading mode you choose; and, if you use Ask AI, the animal avatar assigned to you (which you can change), its on-device chat history, plus a small, decaying memory of the pages and subjects needed to resolve follow-up questions. The command dialog also keeps a bounded list of commands you run so its history and local ranking survive a reload. If you use the reading trail, the passages you select, their source links, their order, and your private notes are stored locally and synchronized only among open tabs in this browser. Removing a trail card permanently tombstones it and purges its quotation and note from durable storage. Ask AI uses Chrome's built-in on-device model. The questions, answers, histories, interest memory, and reading trail never leave your device; none is an identifier; the History panel can erase the saved chats, and clearing your browser data removes all local state.
The interactive workbook's File menu can hand you a file: the sheet as CSV, or a session trace for reporting a defect. The file is built in this tab and saved by your browser to your own machine. The site uploads nothing, keeps no copy, and is not told that you saved it. Two of those exports are worth knowing apart before you send one to anybody: a full trace contains your sheet's cell contents, while a shape-only trace replaces every value, note and name with a blank or a placeholder and keeps only the structure. The menu offers both and picks neither for you.
The same menu can read a file in: "Import CSV into sheet" opens your browser's own file picker, and the file you choose is read inside this tab. Nothing is uploaded and nothing is stored — the bytes become cells in the sheet you are looking at, and closing the page forgets them along with every other edit you made to that figure. The site has no network path for them at all: its content security policy allows no outside origin, so there is nowhere for a file to be sent even by mistake. The picker itself is your operating system's; the page never sees a file you did not choose in it, and never sees the rest of your disk.
If — and only if — you sign in to leave a note, the site sets a single first-party session cookie so it knows the note is yours. The cookie is HttpOnly (no script can read it), is never used to follow you around the site, and expires after thirty days or when you sign out. During the sign-in handshake itself one more, short-lived cookie is set to carry the exchange safely; it too is unreadable to scripts and is deleted the moment sign-in finishes. If you never sign in, the site sets no cookies of its own.
If you sign in to leave a note
Notes on essays require signing in with Google, Apple, or GitHub — not to identify you to me, but so a party you already trust vouches that you are a person. The site deliberately keeps almost none of what those providers offer. It stores exactly four things: which provider you used, the opaque subject identifier the provider assigns (a meaningless string — not your email), a first-party public pseudonym, and the identifier of the animal avatar you chose or were assigned. It does not request or retain your provider display name, profile photograph, or email address. The provider's tokens are discarded the moment sign-in completes; no password ever exists here.
A note you post is held for review before it appears, and published notes show only your pseudonym, your animal avatar, and what you wrote. The Your comments page lets you change that public profile and see, edit, or delete all your notes without finding each article again. An edit returns the note to review before it is published again. You may still write to the address below to have the entire author record corrected or deleted.
What the host can see
The site is served by Cloudflare. Like any web server, Cloudflare records ordinary request data in its logs — your IP address, the time, the page requested, your browser's user-agent — and may set a strictly-necessary cookie (__cf_bm) to tell human visitors from bots. This exists to deliver and protect the site, not to profile you, and is governed by Cloudflare's privacy policy. I do not run any analytics over these logs.
Third parties
Passively, one: the site advertises a Webmention endpoint at webmention.io so that replies and mentions published on other sites can be gathered. Simply reading a page here sends nothing to it; it comes into play only when some other site sends a mention of mine.
Actively, and only at your choice, one more: signing in to leave a note sends you to Google, Apple, or GitHub — whichever you pick — as described above. Reading a page sends nothing to any of them.
Outbound links may carry you elsewhere. Your browser, told to honor Referrer-Policy: strict-origin, reveals to those sites only that you arrived from this site's address — never which page you were reading.
Your data, and how to reach me
The Your comments page provides self-service access to the public profile and notes associated with the signed-in account. To request deletion of the underlying author record, or if you have a question about what is held, write to yesudeep@gmail.com.
This note may change as the site does; the date above is when it was last revised. The site is provided as-is, without warranty.