Privacy Policy

Effective date: 30 October 2026 · Version 1.0

This policy describes how the kaspa-mcp public connector (https://kaspa-mcp.kaspa-mcp.workers.dev, open source at https://github.com/MikeyKaspa/kaspa-mcp) handles information when you connect an AI assistant to it.

1. Who we are

kaspa-mcp is an open-source Model Context Protocol (MCP) server. The shared demo Worker is operated for community use. Self-hosted copies are operated by whoever deploys them — this policy covers the shared public demo unless your self-host publishes a different policy.

2. What the service does

The connector lets an AI assistant read public Kaspa network data, prepare unsigned transactions, and (on self-host with your consent) optionally auto-sign with a key you store on your deployment. The shared demo is keyless: it does not accept or store mainnet private keys.

3. Data we process

• Request metadata: IP address (for rate limiting via Cloudflare), timestamps, tool names, and error codes.
• Tool inputs you send: addresses, amounts, network choice, contract parameters, and similar fields needed to prepare or look up transactions. Do not send seed phrases or mainnet private keys.
• Short-lived sessions: unsigned transaction payloads for tap-to-approve pages may be stored in Workers KV with a short TTL (about 15 minutes), then expire.
• Optional demo key header: if you set X-Kaspa-Demo-Key, it is used only as a rate-limit bucket identifier.

4. What we do not collect

• Account passwords or Internet Identity-style credentials (the shared demo is open; no sign-in).
• Mainnet private keys, mnemonics, or keystores (rejected by the connector).
• Conversation history from your AI app beyond what the assistant includes in a tool call.
• Advertising profiles or sale of personal data to third parties.

5. Third parties

Requests may pass through Cloudflare (hosting and rate limiting) and public Kaspa REST/RPC endpoints you or the defaults configure. Those providers process connection data under their own policies. Explorers linked in responses are third-party sites.

6. Retention

Rate-limit counters are ephemeral. Sign/campaign/page KV entries expire by TTL or when overwritten. Cloudflare and edge logs follow Cloudflare's retention. We do not build long-term user profiles from chat content.

7. Self-host

If you deploy your own copy, you are the operator: keys in your secrets, your logs, your privacy obligations. The shared demo never receives your self-host spending key.

8. Contact

Questions or data requests: open a GitHub issue on https://github.com/MikeyKaspa/kaspa-mcp/issues with privacy in the title, or see Support.