Skip to content
KurrentDB

How kcap handles your data

The full account is Data security and privacy in kcap. This is the page to read before your first session

When a session is stored, kcap sends the transcript and lifecycle events: your prompts, the agent’s replies, every tool call with its input and result, thinking text when the agent exposes it, token usage, subagent transcripts, the repository and branch, and the commits the agent makes. Not your repository: file contents and diffs appear only where a prompt or a tool result contained them. A plan document the agent declares is sent in full, up to 256 KB

Treat a transcript as sensitive by default. If a prompt or a command’s output contained a secret or a confidential discussion, it is in the transcript

  • Exclusions and allow lists decide, on your machine, which repositories and folders are stored at all. Nothing excluded is sent, live or on import
  • Redaction removes recognised secret patterns such as API keys and tokens before upload, from transcripts and from commit messages. It cannot recognise a confidential conversation
  • Records over 4 MiB are replaced by a capture-loss marker rather than sent

Your default audience, then whatever you set per session. Admins can see that sessions exist and how many; they read content only where the audience allows. Agents read through kcap’s tools only what their user could read in the web app. Kurrent and its employees do not have access to your workspace’s data; Access by Kurrent says what that means in practice

A cloud workspace runs on infrastructure Kurrent operates, one workspace per organisation, encrypted at rest. The local edition keeps everything on your own machine and listens only on the loopback interface; its server sends no telemetry, though the CLI and desktop app still do until you turn it off. Data location has the specifics

Your identity from sign-in, your sessions’ metadata, pseudonymous usage reports from the CLI and the desktop app that you can turn off, and the web app’s product analytics. Telemetry lists it and the switches

The desktop app’s usage reports say which screens and features you use and how setup goes, never file paths, prompts or transcript content; they can be associated with your workspace and the person who created it. They are separate from your sessions and go to Kurrent’s product analytics, not to your workspace

The setup wizard asks once, on Help improve kcap: Share usage data or Don’t share. Don’t share stops sending from the app and from the kcap command on this computer straight away. The page appears only if nothing on this computer has asked yet; a kcap command that already showed its own notice counts. If the choice cannot be saved, the wizard says so: the app stops sending until it quits, but kcap commands keep sending

The desktop setup wizard asking whether to share usage data, with Share usage data and Don't share
The wizard's usage-data step: Share usage data or Don't share

Change it any time with Send usage data under Settings → Usage data. It is the same switch as kcap config set telemetry on|off, so turning it off in either place turns it off for both on this computer. Turned back on, it starts sending the next time the app opens. KCAP_TELEMETRY (1 or 0) and DO_NOT_TRACK outrank the switch: when either is set in the app’s own environment, the page names the variable, the switch is greyed out, and the wizard step only shows the notice. A variable exported in your shell profile reaches kcap in a terminal, not an app opened from the Dock

The desktop app's Settings on the Usage data page, with Send usage data on
Settings → Usage data: the Send usage data switch, shared with the kcap command line

Send feedback in the desktop app sends your message, the email address replies go to, and the app, daemon and macOS versions to Kurrent support; it attaches no session. Crash logs from the app and the CLI are written to your kcap configuration folder and stay there

ToDo
Keep a repository outNever record under Settings → Privacy in the desktop app, kcap ignore <path> or excluded_repos
Store only some repositoriesOnly record under Settings → Privacy in the desktop app, kcap allow <path> or allowed_repos
Make new sessions privateOnly me under Who can read new sessions in the desktop app’s setup or its Settings → Privacy, in the web app’s setup, or kcap config set default_visibility private
Keep imported history privateOnly me for the repository under Customize on the desktop app’s history page, or kcap import --private
Hide one sessionShare → Private in the web app, kcap hide, or ask your agent
Delete one sessionDelete session in the web app, kcap disable <id>, or ask your agent
Remove a local edition and its sessionsUninstall kcap… in the desktop app menu, or kcap local uninstall --purge
Turn telemetry offDon’t share in the desktop app’s setup, Settings → Usage data → Send usage data, kcap config set telemetry off, KCAP_TELEMETRY=0 or DO_NOT_TRACK=1; a KCAP_TELEMETRY=1 in the environment outranks the others until unset