security

What runs where.

Your code runs in a computer that belongs to one session. Here is what is inside it, what is not, and what we are still closing. We hold no security certifications today.

Privacy: no monitoring, no logging of your team

We take privacy seriously for productivity teams. Kojo does not monitor or log what your people do. There are no keystroke, screen or activity trackers, and no dashboards that rank or score individuals.

We only keep essential data for your user experience. This is a private environment for builders.

Isolation

computer     one per session
shared       nothing between sessions
lifetime     destroyed when its session is archived

Credentials

What	How it is handled
Your Claude key or subscription, other secrets	Stored encrypted per company. A run receives only the secrets attached to it, re-checked at every run.
GitHub access in the computer	A token limited to the session's repositories, minted per run and revoked at its end.
Pull requests	Opened by Kojo, not by a token in the computer.

Who can do what

Roles are listed on the product page. API keys are scoped and never more than automation. Removing a member takes effect on their next request.

Previews

One origin per preview; signed links that expire; viewers reach only the declared preview port.

Known limits

Code running in the computer can read the run's own tokens. This is a known gap; a per-request proxy is the planned fix. We publish it here rather than let someone find it.

Report a vulnerability

Email security@kojo.build.