Explanation
Data governance
What codingassist sends to third parties during a review, what it stores, and how secrets are protected.
This page lists the data codingassist reads from your Azure DevOps organization, where that data goes, and what is kept afterwards.
What is sent where
| Data | Sent to | Kept by codingassist |
|---|---|---|
| Diff, changed files at the head commit, pull request title and description, linked work items | The model provider: Platform AI, or your own with BYOK | No |
| Comment threads you reply in | The Platform AI model provider | No |
| Changed files (up to 25 per review) | The analysis sandbox, an isolated container on Azure | No |
| Source code of the default branch, split by symbol | The embedding provider, then the vector store, to find similar code | Yes, in a vector collection for your organization |
| Findings, acceptance criteria results, fix attempts, sandbox run records | The codingassist database | Yes |
The providers are listed in Subprocessors.
Training
codingassist does not train models on your code. Code sent to a model provider is processed under that provider's API terms.
Secrets
| Secret | Protection |
|---|---|
| Azure DevOps personal access token | Encrypted with AES-256-GCM before it is stored. Never returned to the web app |
| BYOK API key | Encrypted with AES-256-GCM before it is stored. Never returned to the web app |
The encryption key is kept in Azure Key Vault. It is one key for all organizations, not a key per organization.
Isolation
Every organization's data is separated from the others. See Multi-tenancy & isolation.
Certifications
No SOC 2 or ISO 27001 certification has been issued.
Related
Was this page helpful?