Terms of Service

1. Two things, two licenses

The plugin itself — every skill, agent, hook, and the source code at github.com/KevinZai/commander — is licensed under MIT. Fork it, modify it, ship it, sell your own derivative. The MIT license terms govern that work, not these site Terms.

The hosted MCP server at mcp.commanderplugin.com, the marketing site, the docs site, and the waitlist API — those are operated services. These Terms govern your use of those services.

2. The deal in plain language

• The plugin is free. It will stay free for the plugin core.
• The hosted MCP server has a free tier of 100 calls per month per authenticated user, with sliding-window burst protection of 60 calls per minute.
• If we ever ship a paid tier (Pro Individual or Pro Team), we'll email anyone on the waitlist first.
• You can use everything for any purpose, commercial or personal, as long as you don't abuse the hosted infrastructure or impersonate someone.

3. Acceptable use

Don't do any of these against the hosted services:

• Circumvent the rate limits (rotating IPs, creating multiple accounts to multiply your free quota, scraping the catalog programmatically).
• Resell access to the hosted MCP server as if it were yours.
• Use the service to generate content that violates law, harasses someone, or attempts to compromise other infrastructure.
• Pretend to be CC Commander, Kevin Zicherman, or Axiom Marketing Inc.
• Reverse-engineer the auth or rate-limit logic to bypass it.

If we observe abuse, we may revoke your access without notice. We'll try to email you first if it's ambiguous.

4. Availability — AS-IS, no SLA

The hosted MCP server is provided as-is, without any warranty of uptime, accuracy, fitness for a particular purpose, or non-infringement. We make a best effort to keep it running and to notice when it's broken — but there is no service-level agreement and no compensation owed if it's down. If you have a workload that cannot tolerate downtime, run the plugin's local mode (it doesn't need our server).

5. Your responsibility for your work

The plugin generates suggestions for code, plans, and documentation via Claude (or any MCP client you connect). The output is not reviewed by us before it reaches you. You are responsible for reviewing, testing, and validating any code or content before using it. CC Commander, Kevin Zicherman, and Axiom Marketing Inc. accept no liability for damages caused by output you chose to use without review.

6. Limitation of liability

To the maximum extent permitted by law, the total liability of CC Commander, Kevin Zicherman, and Axiom Marketing Inc. for any claim arising out of the hosted services is capped at the greater of (a) the amount you paid us in the 12 months preceding the claim, or (b) USD $50. The plugin itself, being MIT-licensed, carries no warranty per the MIT license — your remedy under MIT is to fork.

7. Changes to these Terms

We may update these Terms when the services change. Material changes get a banner on commanderplugin.com or an email to the waitlist. The effective date at the top of this page reflects the latest revision. Continued use after a change means you accept the new Terms; if you don't, stop using the hosted services.

8. Governing law

These Terms are governed by the laws of the Province of Ontario and the federal laws of Canada applicable therein (the jurisdiction of incorporation of Axiom Marketing Inc.), without regard to conflict-of-laws rules. Disputes are subject to the exclusive jurisdiction of the courts located in the Province of Ontario, Canada.

9. Termination

You can stop using the hosted services any time — close your account, delete the plugin, walk away. We can revoke your hosted access for abuse (Section 3). The MIT-licensed plugin remains yours to use under MIT regardless.

10. Data processing — hosted MCP and anonymous telemetry

Hosted MCP server (mcp.commanderplugin.com)

When you use the hosted MCP server, tool calls (/v1/call) are processed server-side and transiently. Specifically:

• Your tool arguments are received and dispatched server-side to fulfill the request.
• We do not store, log, or retain tool inputs after the response is sent.
• Tool inputs are never sent to PostHog or any analytics system.
• The hosted MCP is stateless: no per-user tool history, no input persistence beyond the duration of the HTTP request.

Anonymous telemetry from the plugin and CLI

Enabled by default; opt-out is simple. By using the CC Commander plugin or CLI, you consent to the collection and analysis of anonymous usage events sent to PostHog. This data helps us understand which features provide value and prioritize improvements.

• Collection scope: Event names (e.g., hook_fired, skill_invoked), an anonymous device ID, OS version, Node.js version, and non-sensitive metadata.
• Sensitive data exclusion: We explicitly exclude any properties with keys matching prompts, file paths, secrets, or personal context. A recursive server-side scrubber (allowlist-aware, depth-bounded) drops these keys if they somehow reach us.
• Opt-out mechanism: Set CCC_TELEMETRY=0 in your shell or edit ~/.commander/config.json to set "telemetry": false. The plugin will not send events when disabled.
• Data use: Aggregate reports only — "X% of users invoke skill Y" and "hook Z triggers most often in scenario W." No personal profiles, no session replay, no retargeting.
• Data retention: PostHog retains events for 30 days by default.