Security and data

Where your data lives, how work is sandboxed, what model providers see, runner-only workspaces, retention and the DPA.

kanman works on your source code. These pages explain plainly what that means for your data and your compliance work. For a security review, start with the Trust pack. The kanman trust center has the security whitepaper and short policies, and the status page shows uptime and incidents.

In this section

Trust pack for security reviews

What kanman is and is not, where data flows, who processes it, what is logged, how people stay in control, and how kanman aligns with ISO/IEC 42001 and the NIST AI RMF.

Read more

Hosting and data residency

Where kanman runs, where your data is stored, and how to keep code execution on your own infrastructure.

Read more

Privacy rules and audit

Decide what counts as sensitive in text from your connections, test your rules on sample text, and show auditors what was replaced.

Read more

EU-only processing

One switch that keeps every model call of your workspace inside the EU: kanman refuses any other route before a request leaves.

Read more

Masking before model calls

Personal data, call data and secrets never reach a language model: kanman replaces them with placeholders before every call.

Read more

Live view from your runner

Watch the coding tool work directly from your own runner: the stream stays in your network, nothing opens inbound, and it is off until a team admin switches it on. For security teams: ports, protocol, data flow and how to turn it off.

Read more

How team apps are hosted

Where team apps run, how they are isolated and limited, how their base images stay current with automatic rollback, how a scanner maps findings to an app, and how data, secrets and network access are handled. For IT and security teams.

Read more

Let people reach apps directly

Let people on your company network open team apps straight from your own runners, at a stable HTTPS address, with access control staying in kanman. For IT: settings, runner variables, TLS, load balancing and rollout.

Read more

Sandbox and secrets

How runs are isolated, what the coding tool may touch and reach on the internet, how kanman keeps secret values out of runs and treats outside text as data.

Read more

How kanman marks its work

Every commit, pull request, merge request and tracker comment kanman writes says that it was prepared by AI.

Read more

What model providers see

Which language model providers receive data during a run, what they receive, and how to use your own contract.

Read more

Retention and deletion

How long kanman keeps runs, activity and audit entries, and what happens when you delete a team or a workspace.

Read more

DPA and subprocessors

The data processing agreement for kanman, where to find the current list of subprocessors, and how changes are announced.

Read more