Kuboo
Proposed baseline

This is Kuboo's proposed baseline policy as of October 2026. The specific tools, logging requirements, and data handling rules for your engagement are defined in your contract.

Last updated: October 2026

AI Usage Policy

Kuboo's AI usage policy defines how engineers use AI coding tools on client work: which tools are permitted, how client data is handled, who reviews AI-generated code, and what is available for audit.

1. Tools permitted

By default, Kuboo engineers use the AI tools your organization has already approved. If you have no AI tools policy, we will propose a short list before the engagement starts and will not use any tool outside that list without your written approval.

2. Client data and code

  • Client code, credentials, internal documentation, and data are never entered into consumer AI tools.
  • Engineers use only client-approved enterprise accounts, or personal accounts on enterprise-grade plans with data processing agreements that exclude customer data from model training.
  • No AI provider trains on your code or data under these plans, per the provider's terms of service.

3. Secrets and PII

Engineers never include secrets, API keys, passwords, or personally identifiable information (PII) in AI prompts. Deliberately including sensitive data in a prompt is an eliminatory failure in Kuboo's engineer assessment and grounds for immediate removal from a client engagement.

4. Code review and accountability

All code contributed by a Kuboo engineer — written by hand or with AI assistance — goes through the same review process: pull request, peer review, and automated tests as a passing gate. The engineer who submits the code is accountable for it, regardless of how it was produced.

5. Logs and audit trail

If your organization requires a log of AI-assisted actions — for example, which files were modified using which tool — Kuboo engineers can maintain and provide this record. The format and retention period are defined in your contract.

Frequently Asked Questions