Lantern WorksGPU prices, refreshed regularly, with each price's age shown

Privacy

This page describes what Lantern Works stores. It matches the code in this repository and the longer notes in PRIVACY.md and docs/MEASUREMENT.md.

The MCP package (lantern-works-deals-mcp)

Telemetry is off by default. With nothing set, the server sends no telemetry and writes no telemetry file. Its only network requests fetch the public feeds, with User-Agent: lantern-works-deals-mcp/<version>.

Set LANTERN_TELEMETRY=1 to opt in to an anonymous tool-call counter. It is enabled only when the value is exactly 1. At most once per UTC day the server sends aggregate counts only: tool name, package version, UTC day and number of calls. It does not send tool arguments, queries or results, or any user, host, client or install identifier. Local counts sit in a cache file until the day is over (at most 7 unsent days). Failures are ignored and never block a tool call.

The collector stores only the total per (day, tool, version). Its rate limiter keeps an in-memory hash and does not write IP addresses to storage. Aggregate totals are public at the collector’s /v1/stats. To turn telemetry off, unset LANTERN_TELEMETRY or set it to anything other than 1.

The hosted MCP endpoint

The hosted worker at https://lantern-works-mcp.lantern-works.workers.dev publishes counts at /stats.json. Call counts are anonymous daily totals. Distinct-caller counts use a daily-salted hash. Weekly repeat-caller counts use a pseudonymous, weekly-rotating id, described below.

This website

The site uses Cloudflare Web Analytics for page views; it sets no cookies. Clicks on search, compare, calculator and outbound links are counted as virtual page views under /e/.... Deal links (and the tracked_url field in the feed and MCP results) go through a /go/<deal-id> redirect on the telemetry worker. Vendor links use /go/v/<vendor-slug> (the slug is resolved only from the served GPU feed: a disclosed referral URL, else that vendor’s checked source URL, else the redeem URL of the vendor’s only deal; never a caller-supplied URL). Both add one to an aggregate counter per UTC day, deal id (vendor links are stored as v:<slug>), provider, src and ?ref= tag, then redirect to that listed URL. The counter also keeps a coarse user-agent class (ua_class: browser, bot, script, prefetch or other) worked out from the User-Agent and prefetch headers at request time; the raw user agent is never stored, so automated fetches can be left out of the published click count. No IP address, cookie, user agent or other identifier is stored.

More: Methodology · Install the MCP server · Source code