This Acceptable Use Policy ("AUP") defines the boundaries of acceptable behavior when using Command Center ("CC"). This policy is incorporated into and subject to the Terms of Service.
Principle: CC is a development tool for managing legitimate software ideation and build processes. Use it for that purpose, respect other users' data, and take responsibility for the credentials you configure.
1. Permitted Use
CC is intended for:
- Managing software ideation using the ODRC framework (concepts, ideas, sessions)
- Tracking development jobs and build lifecycle
- Generating and delivering development specifications and documentation
- Coordinating work between AI assistants (Claude Chat and Claude Code) via the MCP server
- Configuring integrations with third-party development services (GitHub, domain providers)
2. Prohibited Conduct
2.1 Security and Access
You must not:
- Attempt to access, read, modify, or delete another user's data
- Circumvent, disable, or interfere with Firebase security rules or authentication mechanisms
- Use CC to store credentials for unauthorized access to any system
- Probe, scan, or test the vulnerability of the MCP server or any connected infrastructure
- Share your account access or API keys configured in CC with unauthorized individuals
2.2 Content
You must not use CC to create, store, or transmit:
- Content that is illegal under applicable law
- Malware, exploit code, or instructions for unauthorized system access
- Personal data of third parties without their consent
- Content that infringes the intellectual property rights of others
- Deceptive content intended to impersonate others or misrepresent its origin
2.3 Resource Usage
You must not:
- Abuse the MCP server with excessive automated requests beyond normal tool usage patterns
- Use CC as a general-purpose data storage system unrelated to development management
- Deliberately create excessive Firebase database load (e.g., rapid-fire writes, large data dumps)
- Use the document delivery system to push content to repositories you don't control
2.4 Third-Party Services
When using API keys configured in CC, you must:
- Comply with the terms of service of each third-party provider (GitHub, Anthropic, domain registrars)
- Use API access only for purposes those services authorize
- Respect rate limits and usage quotas of connected services
- Promptly revoke and replace any credentials you suspect have been compromised
3. Credential Responsibility
Important: API keys stored in CC's localStorage provide direct access to external services. A compromised browser or shared device can expose these credentials. Treat your CC session with the same care you would any system that stores sensitive credentials.
You are responsible for:
- Understanding the access scope of each API key you configure (e.g., a GitHub PAT with repo access can read/write all your repositories)
- Using appropriately scoped credentials (principle of least privilege)
- Rotating credentials periodically
- Clearing credentials when using shared or public devices
- Monitoring your connected accounts for unauthorized activity
4. AI-Assisted Workflows
CC facilitates AI-assisted development through Claude. When using AI features:
- You remain responsible for all actions taken based on AI-generated suggestions
- Review AI-generated code, specifications, and configurations before deploying them
- Do not use AI features to generate harmful, deceptive, or illegal content
- Comply with Anthropic's Usage Policies when interacting with Claude through CC
5. Reporting Violations
If you discover a security vulnerability or become aware of conduct that violates this policy, please contact us immediately at security@commandcenter.dev. We take reports seriously and will investigate promptly.
6. Enforcement
Violations of this AUP may result in:
- A warning and request to correct the behavior
- Temporary suspension of access
- Permanent termination of access
- Deletion of offending content
We will make reasonable efforts to provide notice before taking enforcement action, except in cases of severe or ongoing violations that threaten the security or integrity of the Service or other users' data.
7. Changes to This Policy
We may update this AUP from time to time. Changes will be posted on this page with an updated effective date. Material changes will be communicated to active users.
8. Contact
For questions about this Acceptable Use Policy, contact:
Dave Stewart
Email: legal@commandcenter.dev