About these terms
These terms are an agreement between you and Procli covering your use of Procli Code — the web dashboard, the Cheat and Guard agent integrations, the Quality and Audit scanners, the command-line interface (CLI), and any related APIs (together, the “product”).
By creating an account, connecting a repository, generating an API key, or otherwise using the product, you agree to these terms. If you are using Procli Code on behalf of a company or team, you confirm that you are authorized to accept these terms for that organization.
What the product does
Cheat checks an agent's completion claims against what actually ran in a session — the commands executed, files changed, and results returned — and labels each claim Confirmed, Unconfirmed, Partial, or Contradicted. Guard inspects an agent's action before it executes: clearly destructive actions are blocked automatically, low-risk work proceeds, and the ambiguous middle is flagged for you to decide on.
The Quality and Audit dashboards scan repositories you connect through the Procli GitHub App and return prioritized findings with fixes and JSON output. The CLI runs the same Quality and Audit checks from your terminal (procli quality, procli audit, with --json for CI). All of these support your own judgment — you decide whether and how to apply any recommendation, fix, label, or finding.
Beta status and access
Procli Code is in beta and free of charge while it is being shaped with early users. Access is currently limited to allowlisted accounts, so creating an account does not by itself guarantee access. Features, availability, usage limits, and pricing may change as the product matures, and where a change would materially affect you we will aim to give reasonable notice.
Because the product is in beta, Cheat and Guard can produce false positives and can miss real issues, and some product areas are still being wired up. Nothing acts on your code automatically — every finding leaves the decision with you.
Your account, keys, and fair use
You are responsible for the security of your account, your connected GitHub repositories, your API keys, and any access you grant. API keys are shown once at creation and carry the procli_ prefix — keep them secret, treat them like passwords, and revoke any key you no longer use or suspect is exposed. You are responsible for activity that occurs under your account or keys.
You must only connect repositories and systems you own or are authorized to access, and you must have the right to submit any code you analyze. Usage is metered (for example, a default daily scan limit and other action limits) to keep the service reliable; do not attempt to bypass those limits or scan beyond the access you were granted.
Findings are decision-support, not guarantees
Reports, labels, scores, blocks, and fixes are decision-support outputs. They are not a guarantee that software is defect-free, secure, compliant, or ready for production, and a “Confirmed” or clean result does not certify that no problems exist.
Audit is scoped deliberately narrow: it targets the common mistakes fast-moving, AI-built applications tend to ship, and does not replace a dedicated security team, a formal code audit, or a real penetration test. Guard is not a hardened security boundary and a determined actor may be able to work around it.
Human review remains required before you ship, deploy, merge, or otherwise rely on any product output. You are solely responsible for decisions you make based on the product.
Acceptable use
Do not use Procli Code to access repositories, data, or systems you are not authorized to use; to attack systems, bypass security controls, or exfiltrate secrets; to reverse engineer, resell, or build a competing service from the product; or to violate the rights of others or any applicable law.
Do not attempt to disrupt, overload, or gain unauthorized access to the product or its infrastructure, and do not use automated means to abuse rate limits or scan beyond the access you have been granted.
Intellectual property
You keep all rights to your code and repositories. You grant Procli the limited permission needed to process that content in order to provide the product to you — for example, to run a scan, verify a claim, or generate a report.
Procli and its underlying software, models, checks, and branding remain the property of Procli. These terms do not transfer any ownership of the product to you.
Disclaimers and liability
The product is provided “as is” and “as available,” without warranties of any kind, whether express or implied, including fitness for a particular purpose and non-infringement. We do not warrant that the product will be uninterrupted, error-free, or that it will detect every issue.
To the maximum extent permitted by law, Procli will not be liable for indirect, incidental, special, or consequential damages, or for loss of data, revenue, or profits, arising from your use of or inability to use the product.
Changes and termination
We may update these terms as the product evolves. Continued use after an update means you accept the revised terms. The “Last updated” date above reflects the current version.
You may stop using the product and disconnect your repositories at any time. We may suspend or end access that violates these terms or that risks harm to the product, other users, or third parties.
Contact
Questions about these terms can be sent to procli.code@gmail.com.