ChirpIQX

Appearance

Privacy Policy ​

Effective Date: January 16, 2025 Last Updated: September 25, 2026

Introduction ​

ChirpIQX ("we", "us", or "our") operates the website chirp.semanticintent.dev and associated documentation. This Privacy Policy explains how we collect, use, and protect information when you visit our site, run the ChirpIQX MCP server yourself, or use the hosted ChirpIQX connector.

TL;DR: We don't collect personal data, track you, or use cookies. If you run ChirpIQX yourself, your league data never leaves your machine. If you use the hosted connector, the roster you paste is sent to our server, used to answer that one request, and not stored — see The hosted connector.

Information We Collect ​

Information You Provide ​

We do not require you to create an account or provide personal information to access ChirpIQX documentation.

Automatically Collected Information ​

Currently Collected: None

  • No analytics tracking
  • No cookies or local storage (beyond temporary session data)
  • No IP address logging
  • No user behavior tracking

VitePress Local Search: Our documentation uses VitePress's built-in local search, which indexes content entirely in your browser. Search data never leaves your device.

Future Changes ​

If we implement analytics or tracking in the future:

  • This policy will be updated with clear notice
  • We will use privacy-respecting tools (e.g., Plausible Analytics, Cloudflare Analytics)
  • You will be notified via this page

How We Use Information ​

Since we don't collect personal information, we don't use, share, or sell any user data.

Third-Party Services ​

GitHub Pages / Cloudflare Pages (Hosting) ​

ChirpIQX is hosted on [GitHub Pages / Cloudflare Pages]. These platforms may collect:

  • IP addresses (for server logs and DDoS protection)
  • Browser metadata (User-Agent strings)
  • Request timestamps

These are standard hosting practices beyond our control. Refer to:

NHL Public API ​

ChirpIQX's MCP server reads the NHL's public API for schedules, rosters, season statistics and standings. When you use the MCP server:

  • Requests go directly from your machine to the NHL's public endpoints
  • No credentials are involved — the NHL API requires no key, token or account
  • No identifying information is sent. A request for a club's schedule says nothing about you, your league or your team
  • We never see or store anything. There is no ChirpIQX server; the software runs entirely on your machine

Your league data — when you run ChirpIQX yourself ​

When you install the MCP server and run it on your own machine, the roster, opponent and standings you paste are parsed locally and written to .chirp-data/ inside your own installation directory.

  • This data never leaves your machine
  • It is not transmitted to us, to the NHL, or to any fantasy platform
  • You can inspect it with the show_stored_data tool, and delete it at any time with show_stored_data(clear: "roster") or by removing the .chirp-data/ directory

The hosted connector ​

ChirpIQX is also available as a hosted MCP connector at https://chirp-mcp.semanticintent.dev/mcp, run on Cloudflare Workers. It works differently from a local install, and this section describes exactly how.

What you send. Each tool call carries whatever you or your AI assistant put in it — typically a pasted roster (player names, and sometimes lineup slots such as BN or IR), an opponent's roster, playoff weeks, or a list of drafted players. Nothing else is requested: no account, no name, no email, no fantasy platform login.

How it is used. The pasted text is resolved against public NHL rosters and used to answer that single request. The response goes back to the client that asked.

What is stored. Nothing you send. The hosted connector is stateless: it has no database of users or rosters, and it does not write your request to storage. The tools that save a roster (set_roster and related) are not offered on the hosted connector for this reason. The only data it keeps is public NHL data — schedules, rosters, statistics and standings — cached so that it does not have to re-fetch it for every request.

What is logged. Our code does not log the contents of your requests. Our hosting provider, Cloudflare, records operational metadata for each request — such as the time, the path, the response status and the requesting IP address — and keeps it for up to 7 days, for debugging and abuse prevention. Your IP address is also used, transiently, to apply a rate limit.

Who else sees it. We do not sell, share or transfer request data to anyone. It is processed by Cloudflare as our hosting provider, under Cloudflare's privacy policy. The connector makes its own requests to the NHL's public API for public hockey data; those requests contain nothing you sent.

Your AI assistant. If you use the hosted connector through an AI assistant such as Claude, that assistant also sees your conversation and tool calls. That is governed by the assistant provider's own privacy policy, not this one.

Retention and deletion. Because nothing you send is stored, there is nothing to delete. Cloudflare's operational logs expire on their own within 7 days.

Data Storage and Security ​

  • ChirpIQX Documentation Site: No user data is stored
  • MCP server, run yourself: All data remains on your local machine
  • Hosted connector: Request contents are processed in memory and not stored; operational logs expire within 7 days (see The hosted connector)
  • GitHub Repository: Public and open-source (no private data)

Your Rights ​

Since we don't collect personal data, data subject rights (GDPR, CCPA) don't apply to site visitors.

If you use the MCP server locally:

  • You control all data (stored on your machine)
  • You can delete all data by removing the MCP server files
  • No data is transmitted to ChirpIQX servers

If you use the hosted connector:

  • Nothing you send is stored, so there is no personal data held about you to access, correct or delete
  • Operational logs held by Cloudflare contain your IP address and expire within 7 days
  • Questions about either can be raised through the contact options below

Children's Privacy ​

ChirpIQX is not directed at children under 13. We do not knowingly collect information from children.

Changes to This Policy ​

We may update this Privacy Policy periodically. Changes will be posted on this page with an updated "Last Updated" date.

For significant changes (e.g., adding tracking), we will add a prominent notice to the homepage.

Contact ​

Questions about this Privacy Policy?

Philosophy: ChirpIQX is built for fantasy hockey enthusiasts, by fantasy hockey enthusiasts. We respect your privacy because we'd want the same respect. No dark patterns, no tracking, no BS.

Smart Chirps. Winning Insights. Privacy Respected. 🏒