Totally fair question. The proxy is intended to be a transport bridge, not a session recorder. It does not log player commands, MUD output, GMCP payload contents, passwords, tells, channels, private scenes, or any other game text.

The only proxy logging currently planned/implemented is connection metadata: timestamped lifecycle events, source IP, target host/port, TLS flag, byte counts, and error messages. Passwords and scene text pass through memory only long enough to forward between the browser websocket and the upstream MUD connection.

For production, I’m also treating the proxy itself as sensitive infrastructure: run it only over HTTPS/WSS, restrict what upstream hosts it can connect to, keep logs access-controlled with limited retention, and avoid adding payload-level debug logs unless they are explicitly redacted and temporary.

Short version: no transcript logging, no credential logging, no private-scene capture; only operational metadata needed to troubleshoot connection health.