---
title: Autter Security - How Your Code Is Protected
description: How Autter protects the code it reviews: ephemeral sandboxes destroyed after every run, no training on your code, least-privilege access, scoped expiring tokens, a full audit trail, and on-prem deployment for enterprises that need the review plane inside their own network.
url: https://autter.dev/security
site: Autter - Autter is your AI teammate for code review and testing: it reviews code, tests product impact, checks security, governs releases, and closes the loop from production failure to verified fix.
---

## The data path

The life of a pull request inside Autter, end to end. The only artifacts that outlive a run are the verdict, the findings, and the audit entry.

1. **Scoped read**: a native GitHub App with least-privilege scopes clones the pull request. Autter reads what it reviews and nothing more.
2. **Encrypted transit**: code moves over TLS and lands encrypted at rest, inside a sandbox built fresh for this one run.
3. **Isolated execution**: the suite runs against the base branch in full isolation. No shared state, no neighbors.
4. **Verdict posted**: findings land on the pull request pinned to file and line.
5. **Teardown**: the sandbox is destroyed the moment the verdict lands. Source does not outlive the run.

## Security posture, clause by clause

| Clause | Commitment |
| --- | --- |
| §1 Ephemeral execution | Every pull request runs in a sandbox built fresh for that run and destroyed the moment the verdict lands. Nothing lingers between runs, and no two customers ever share one. |
| §2 No training, ever | Your source is never used to train models. It exists inside the run, and then it is gone. |
| §3 Encrypted throughout | In transit and at rest, from the moment the sandbox clones to the moment the verdict posts. |
| §4 Least privilege | The GitHub App asks for the minimum scopes a review needs. Autter reads what it reviews and nothing more, through access you can revoke at any time. |
| §5 Tokens that expire | Personal access tokens carry narrow scopes (mcp:read, mcp:write, mcp:llm), expire on schedule, and revoke instantly from the dashboard. |
| §6 Everything audited | Every machine-facing call records actor, token, duration, result, and error code in the organization audit log. |
| §7 Rate limited per token | Runaway agent loops get slowed down instead of taking the org down. |
| §8 Isolation and SSO | Organizations are isolated from each other, and the Fleet plan adds SSO / SAML for centralized access control. |

## Data retention: what Autter keeps

| Data | Notes |
| --- | --- |
| Findings and verdicts | Pinned to file and line, they are the review record your team works from. |
| The map, not the territory | Product memory stores structure: APIs, routes, schema, owners, hotspots. A graph about your code, not a copy of it. |
| The audit log | Actor, token, duration, result, and error code for every machine-facing call. |
| Account and billing data | Covered end to end by the privacy policy. |

## Data retention: what Autter never keeps

| Data | Notes |
| --- | --- |
| Your source after the run | Code exists inside the ephemeral sandbox for exactly one review, then the sandbox is destroyed with it. |
| Training data | Your code never trains a model, ours or anyone else's. |
| Prompts from the CLI | Local-only mode never uploads a prompt. Attribution lives in your Git history, on your machine. |
| Standing credentials | Tokens are scoped and expire on schedule. There is no forever-key to steal. |

## Deployment models

| Model | Where the review plane runs | Notes |
| --- | --- | --- |
| Autter Cloud (default) | Autter-managed infrastructure | Live in minutes through the native GitHub App; ephemeral compute per pull request, destroyed after the run; SSO / SAML and audit logs on the Fleet plan |
| On-prem / self-hosted (Fleet plan) | Your cloud account or data center | Source never crosses your network boundary; your keys, your logs; updates ship as versioned releases you approve; scoped with your infrastructure team |

## Reporting a vulnerability

- Email support@autter.dev, or use the [contact form](https://autter.dev/contact.md) with the `Security` question type.
- Reports are read by the founders directly, and fixes ship through the same verified pipeline as every other change.

## Vendor security reviews

- Security questionnaires, data-handling walkthroughs, and detail behind every posture clause are available on request via [contact](https://autter.dev/contact.md) or by booking the founders at https://cal.com/sagnik-autter/30min.

## Related

- [Privacy Policy](https://autter.dev/privacy.md)
- [Terms of Service](https://autter.dev/terms-of-service.md)
- [MCP server: token scopes, audit log, rate limits](https://autter.dev/features/mcp.md)
- [Pricing: SSO / SAML, audit logs, and on-prem live on the Fleet plan](https://autter.dev/pricing.md)
- [Full product overview](https://autter.dev/index.md)