Security
Security
Security practices, isolation, and data handling
StarSling is built with security as a core principle. Your code and secrets are protected at every layer.
Security FAQ
Direct answers to common security-review questions
Data Handling
What data we access and retain
Compliance
Certifications and practices
GitHub App Permissions
What permissions we request and why
Security Highlights
- Secrets never touch StarSling - Passed directly from GitHub to runner
- One single-use machine per job - Every job gets its own dedicated VM, destroyed when the run finishes, with a virtual-machine boundary between customers
- Encrypted everywhere - TLS 1.3 for all communications
- Your data works only for you - Job logs are retained to optimize your own CI, never pooled across customers and never used to train models