Privacy and data sources

What the plugin runs

No code of its own. The plugin has no hooks, no local MCP server, and no scripts that Claude Code executes. Its one component that reaches the network is the remote MCP server.

The skills ask Claude to read one optional file in your project, .claude/cicada-guide.local.md, for default settings. Values from it, such as default_division and context_prefix, can go into tool calls.

What it sends

Each tool call goes to public.cicada.guide over HTTPS, and nowhere else. No credential, key, or environment variable is read or sent. No account is needed: calls are anonymous by default and are recorded without a person profile.

What the server records

For each tool call, the server records:

• the tool's name and the arguments your assistant passed, such as a search phrase, a name, or the summary shown on a bill card;
• the context note your assistant writes about the purpose of the call, including any context_prefix from project settings;
• the name of the AI model making the call;
• the app making the call: its name and version, and the User-Agent string it sends;
• how long the call took, the size of the response, and any error.

Connecting, listing the tools, loading a card, and refused or failed requests are recorded too, without arguments. The server doesn't record your conversation beyond the context note and the arguments, and it doesn't record the results it sends back.

Analytics go to PostHog (United States) and are kept for up to 7 years. Cloudflare, which hosts the server, keeps request logs for a few days. They can include your IP address and the approximate location Cloudflare derives from it, and rate limits are applied by IP address.

No email address, phone number, or precise location is collected. The district map's location toggle runs in your browser and is never sent. Nothing is sold or used for advertising.

What it fetches on your behalf

• get_latest_bill_document and read_pdf_bytes have the server download a bill's public document from the state legislature's own website. read_pdf_bytes accepts only legislature hosts on the server's allowlist.
• Cards load legislator photos and the bill card's PDF viewer from public.cicada.guide only. Any other data a card shows comes from the same server's tools, called through the host, not fetched by the card itself.

The full policy is at public.cicada.guide/privacy.

Data sources

Legislative records are sourced from LegiScan and Open States. Accuracy and freshness depend on those upstreams, and a bill's status may have advanced since the last data load.