Data access and scope
- Code access is explicit: Qodo Context Engine only analyzes the repositories you explicitly connect and tag. No code is accessed without user or admin configuration.
- Context is scoped: Tagged repositories define the scope of what Qodo Context Engine can see and reason about. You remain in full control of what’s included.
Data handling
- No training on customer code: Qodo Context Engine does not use your code for training any foundation models.
- Temporary retrieval only: Relevant code snippets are retrieved for context at query time and are not stored beyond session needs.
- No third-party sharing: Your code and metadata are never shared with external parties.
Storage and transmission
- Encrypted at rest and in transit: All data is encrypted using industry-standard protocols (TLS in transit, AES-256 at rest).
- Isolated indexing: Each organization’s code index is isolated and never mixed with other tenants.
Deployment and integration
- Flexible deployment: Available via cloud, hybrid, or MCP (Memory Code Provider) to support air-gapped or self-managed environments.
- Audit-ready: All interactions with Qodo Context Engine can be logged and traced, enabling compliance with internal policies and external regulations.
Trust and control
- You own your data: You choose what’s connected, indexed, and queried.
- Enterprise controls: Role-based access, tagging, and scoping controls help you define how Qodo Context Engine is used across your team.