Data handling
Sensitive data stays under the workflow boundary you choose
The local FixBugs workflow is designed so code, issue context, logs, and traces can be processed on the user's machine or team-controlled infrastructure. Cloud and GitHub App workflows use different paths, so the data flow should be evaluated by deployment mode.
FixBugs privacylocal data boundaryZero Data Retentionsecurity review
Core insight
The security question is not answered by one slogan. Buyers need to know the deployment mode, the selected providers, the selected model endpoint, and where the final artifacts are posted.
Data privacy guarantees for VSCode and CLI mode
| Data category | Where it is processed | Where it is stored |
|---|---|---|
| Repository code | Local to the user's machine in VS Code and CLI workflows. | Local workspace. |
| Issues, comments, tickets, and alerts | Local to the user's machine in VS Code and CLI workflows. | Local workspace. The original record stays in GitHub, GitLab, Jira, or the connected provider. |
| Logs, traces, metrics | Local to the user's machine in VS Code and CLI workflows. | Local workspace. |
| Generated artifacts | Local to the user's machine in VS Code and CLI workflows. | Local workspace. Artifacts are posted to GitHub only when the user or configured workflow chooses that action. |
| Modulo account data | Modulo Control Plane. | Modulo Control Plane. |
| Model prompt and response context | Zero data retention third party LLM APIs. Local and customer-controlled backends can keep this inside the user's environment. | Depends on the selected model backend. Local and customer-controlled backends can keep this inside the user's environment. |
Continue reading
Ready to evaluate FixBugs?
Start with the workflow surface your team already uses, then use this architecture resource for the technical review.