# Security (/security)



StarSling is built with security as a core principle. Your code and secrets are protected at every layer.

<Cards>
  <Card title="Security FAQ" href="/security/faq" description="Direct answers to common security-review questions" />

  <Card title="Data Handling" href="/security/data-handling" description="What data we access and retain" />

  <Card title="Compliance" href="/security/compliance" description="Certifications and practices" />

  <Card title="GitHub App Permissions" href="/configuration/github-app-permissions" description="What permissions we request and why" />
</Cards>

## 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