KCC is local-first, with hosted services only where coordination requires them.

Local terminal execution, worktrees, and most workflow activity happen on the machine where KCC is installed. Hosted features such as account validation, approvals, audit, machine identity, and chat ingress only apply when those product surfaces are configured and used.

Payments, support, and contact flows may route through Koydo-operated systems or trusted providers such as Stripe and GitHub, depending on the action you take.

For enterprise privacy requests, data-processing questions, or procurement review, use the support or sales contact path so Koydo can provide the current policy and documentation.