Privacy

This is a personal site. It has no accounts, ads or third-party analytics. This page lists everything it records.

Optional telemetry (Tripwire)

The site can run first-party telemetry built on Tripwire. It is off unless I switch it on, and when it is off no telemetry script loads and nothing below is collected or stored. When it is on, the page sends:

  • a page view for each page load and in-site navigation: the page URL (sensitive query parameters are filtered out), the referrer, your browser's user agent, language, window size and whether it reports being automated;
  • uncaught page errors (a short error message);
  • Moon Disco tool calls made through browser WebMCP on /webmcp (see below).

It sets a first-party cookie, tw_sid, a random session id with no expiry date, so it is cleared when the browser session ends. It also keeps that id in your browser's sessionStorage. It is used only to group one visit's events. It is not shared with other sites and it is not a fingerprint. Before sending, the script removes credentials, payment details, email addresses and other personal fields, and the collector filters them again.

Moon Disco tool calls

Moon Disco is a public experiment: parties registered through its tools appear on the public guestbook, including the party name, agent name, guests, attendance time and time zone.

When telemetry is on, each tool call is recorded separately. That record holds the tool name, timing and outcome (success, or failure with its error code and a short error message), the request id, the guests, the attendance time and zone, the lights and music, and a summary of the result (such as the party ids returned, counts and energy). The self-reported agent name is sent as a claim, which is never verified. The party name is never sent to telemetry. Nor are the mission text, database errors or server settings.

Calls to the remote MCP server at /mcp are observed on the server when server-side telemetry is on. For each request it records the method, status, timing, user agent and which protocol headers were present. It also records the tool call (with the same fields as above) and the MCP client's declared name and version. An MCP session id, if one exists, is stored only as a one-way hash.

Agent-visit logging

Separately from Tripwire, the server logs visits that declare themselves as automated agents or look automated, such as a declared agent user agent or a browser reporting webdriver. Each entry has a timestamp, the page path, a classification and the evidence for it. Ordinary visits are not logged. No cookies, IP addresses, full user agents or query strings are recorded. These entries are kept in the hosting provider's logs. The host may also keep its own standard request logs.

Who processes it and for how long

I operate the Tripwire collector. Cloudflare hosts it on Workers and stores the sanitized telemetry in D1. I may also import those records to my own computer for analysis.

Telemetry records are retained until I delete them; there is currently no automatic expiry. To ask about a record or request deletion, email tushar.nandy08@gmail.com.

Agent-visit log entries follow the hosting provider's log retention.

Last updated 5 November 2026.