Data Collection & Security
What data Konvu collects, how code is handled, what's shared with AI models, and our compliance posture.
Konvu minimizes data processing and storage. When data is required, it's securely stored and isolated. This page covers what Konvu collects, how your code is protected, and what's shared with AI models.
SOC 2 Type 2
Konvu is SOC 2 Type 2 compliant, certified by an independent audit firm. Security controls are continuously monitored through Vanta. A SOC 2 report is available upon request.
Trust Center: trust.konvu.com
Data storage: AWS us-east-2
Code privacy
Konvu never stores your code.
When you use Managed Analysis (GitHub App), source code is handled as follows:
The integration uses minimal read-only scope. No GitHub refresh or access tokens are stored -- authentication uses temporary tokens generated by the GitHub App.
The repository is cloned into a transient Lambda function using temporary credentials.
Stack analysis runs precompiled static code. Nothing beyond the analysis binary executes.
Only the identified stack information (see table below) is sent back to Konvu.
The Lambda is destroyed immediately.
For full on-premise control, use Self-Hosted Analysis -- your code never leaves your infrastructure.
What data Konvu collects
Repository names
Yes
--
Stack information (languages, frameworks, runtimes, OS, package managers, manifest locations, backend/frontend indication)
Yes
--
Dependency names and versions
Yes
--
App name from manifest file
Yes
--
Dependency reachability (boolean, file name, line number)
Yes
--
Vulnerable function reachability (boolean, file name, line number)
Yes
--
Small code snippets highlighting vulnerable code (typically 5 lines per match)
--
Yes
AI model data sharing
When Konvu's AI agents assess a vulnerability, the process works in a targeted loop:
1. Initial prompt
Konvu sends vulnerability metadata (CVE ID, dependency, version, enriched metadata) to the model. The model returns search patterns (grep, list file, read file). Source code analysis runs them on a temporary copy in an ephemeral environment.
None
2..n. Agentic loop
Search results and evidence (matching line + surrounding 2 lines + file path) are sent to the model. The model returns a new search pattern, which gets executed.
Up to 5 lines per match
n+1. End of analysis
Investigation steps, tools used, results, and evidence are persisted in the Konvu backend. The ephemeral environment is terminated and the temporary code copy is erased.
None
What is and isn't shared
Up to 5 code lines per match
Entire repository
File paths of matched files
Files unrelated to the vulnerability
Vulnerability metadata
Secrets, API keys, credentials
Dependency version info
Customer data or proprietary business logic
Training opt-out
Konvu has opted out of OpenAI's data sharing program. Your code is not used to train or improve OpenAI's models. Code snippets are processed for immediate analysis and not retained. See the OpenAI data usage policy.
Access controls
Read-only access -- the agent can only read code, never modify it
Targeted searches -- only patterns related to the specific vulnerability
Path restrictions -- cannot access files outside the repository
No execution -- code is analyzed statically, never executed
Ephemeral environment -- code stored only during analysis, deleted immediately after
Bring Your Own Keys
You can configure AI triage assessments to use your own OpenAI API keys or endpoint. Your OpenAI token is stored encrypted in Konvu's database. Configure this under Agents > Coverage in the Konvu dashboard.
On self-hosted deployments running controller image 0.21.23 or later, this key is also encrypted with your cluster's RSA public key and forwarded to your controller, which decrypts it with a private key that never leaves your cluster. It is used only when no OpenAI key is configured on the cluster itself. See LLM Key Resolution.
Secrets data handling
Secrets triage handles credential findings separately from the vulnerability metadata flow described above. Findings sent to the backend identify the credential with a hash and include its provider, repository, file location, commit, and available validation evidence. The finding record uses a masked representation rather than storing the raw credential as its identifier.
When provider validation is enabled, the analysis process can use the detected credential in live requests to its provider. This is separate from sending evidence to an AI model. Detection can continue with provider validation disabled; the organization-level policy defaults to disabled for on-premises workspaces and enabled for managed workspaces unless overridden.
The Secrets detail panel displays masked matches and available evidence, including check times and known identity facts. A cached result represents an earlier check, and validation receipts may omit the exact request or response.
Trust center
Review Konvu's security practices, request the SOC 2 report, and access compliance documentation at trust.konvu.com.
Last updated

