Effective August 17, 2026

Privacy policy.

What the public site and owner-operated MCP service process.

Scope

This policy covers the Cloud Harness MCP website, installable skill/plugin package, and the private MCP service operated by its owner. Cloud Harness is not offered as an anonymous or multi-tenant public account service.

Website data

The static website does not intentionally set application cookies, run advertising, or add product analytics. Infrastructure providers may process ordinary request data such as IP address, user agent, requested URL, timestamp, and security events to deliver and protect the site.

MCP service data

When an authorized owner uses the MCP service, it processes the repository URL and ref, workspace identifiers and lifecycle metadata, tool inputs, bounded outputs, task/process state, and operational logs needed to authenticate, execute, diagnose, and secure the request. Repository files are materialized in a time-limited workspace and removed when the workspace closes or expires.

Private-clone or Git transfer credentials, when configured by the operator, remain in the trusted broker and are not intended to persist in the executor checkout, remote URL, tool output, or logs.

Purpose, sharing, and retention

Data is used only to provide, secure, troubleshoot, and maintain the owner-operated harness. It is not sold or used for advertising. Necessary infrastructure and repository-host providers process data under the operator's configuration. Workspace files follow close/expiry cleanup; metadata, security events, backups, and provider logs follow the operator's configured retention and legal obligations.

Your controls

Do not send credentials, personal data, or repositories you are not authorized to process. The service owner can close a workspace, rotate access credentials, inspect configured retention, and handle lawful access or deletion requests for operator-controlled records.

Security and contact

No Internet service can guarantee absolute security. Report vulnerabilities privately through GitHub Security Advisories. For other privacy questions, open a non-sensitive request in GitHub Issues; never include tokens, private code, or personal data.