Permission-aware retrieval
Users only receive explanations referencing repositories and branches they explicitly have read access to in GitHub.
Security
How Atlas protects source code and organizational knowledge.
Atlas is early-stage. This page states what is built and what is only planned, and nothing here is a certification or a contractual guarantee.
Controls in the product design.
These describe how Atlas is designed to work. Deployment options and data residency are not final.
Repository access inheritance
Inherits repository permissions directly from GitHub access controls and organization rules.
Secret scrubbing & exclusions
Detect secrets and exclude configured sensitive files and source patterns before analysis begins.
Complete auditability
Detailed logging of every query, view inspection, and citation export to trace software understanding activity.
Tenant isolation & encryption
Dedicated tenant data isolation and encrypted transport for all code indices and semantic graphs.
Configurable model-provider controls
Control which source data may be sent to model providers and define provider-specific handling policies.
Compliance status, stated precisely.
Each framework carries one of four labels: implemented, planned, independently assessed, or certified. Atlas holds no certification today.
| Framework | Scope | Status |
|---|---|---|
| SOC 2 | Atlas serviceNo audit period has started and no date is set. | Planned |
| ISO/IEC 27001 | Atlas organizationNo date is set. | Planned |
Report a suspected vulnerability.
Send security reports privately. Do not post them publicly.
Report a security issue
If you believe you found a vulnerability, tell us how to reproduce it and what it affects.
- Include the steps to reproduce the issue.
- Access only the data needed to show the issue.
- Give us reasonable time to fix it before you share details.
A dedicated security address and response times are not published yet.