What Auterim reads, what it keeps, what it refuses to keep, and where it stops.
Read the detailsEvery connection has one direction and one level of access.
Server-side authorization on every request, plus row-level security on every table.
AES-256-GCM encryption, bound to the workspace and provider it belongs to. Keys can be rotated.
GitHub access is read-only and scoped to the repositories you choose.
Capped reads held in memory. Secret-shaped content is redacted. Code is not kept.
Private and internal networks are refused, and the discovery browser cannot make an unchecked request.
Auterim prepares fixes for your team. It never merges and never deploys.
Auterim can prepare a fix. Everything after that is a decision your team makes.
A proposed change, with the evidence behind it. On plans that include it, a draft change on its own branch.
An engineer reads it, changes it, or closes it. Nothing moves without them.
You merge and deploy through your own process. Auterim never merges and never deploys.
Every request is authorized on the server against the workspace it belongs to and your role in it. Nothing relies on the browser to decide what you can see.
Underneath that, row-level security is enabled on every table, so a query can only return rows for its own workspace even if an application check were missed.
Credentials for Slack, Linear and Sentry are encrypted with AES-256-GCM before they are stored. Each one is bound to its workspace and its provider, so it cannot be decrypted in another context.
Encryption keys are versioned and can be rotated. Stored credentials are never sent back to the browser.
GitHub access is read-only and limited to the repositories you choose when you connect.
GitHub tokens are short-lived, held in memory for the duration of a check, and never written to storage.
Discovery reads your website the way a visitor would. Requests to private, local or reserved networks are refused, and redirects are checked at every step.
The browser used for discovery runs contained: every request it makes is checked before it leaves, and anything that fails the check is blocked.
Some steps use a language model provider. It receives a bounded packet of change evidence and workspace context, with secret-shaped content redacted, sent with storage disabled.
Raw repository contents are never sent. Reads from your code are capped, held in memory, and discarded once the finding is recorded.
Incoming webhooks from GitHub and the payment provider are verified by signature before they are processed. Unsigned or mismatched requests are rejected.
Connector activity, such as connecting, revoking and delivering alerts, is recorded in an audit trail for the workspace.
Card details go directly to the payment provider. They never pass through or rest on Auterim systems.
Auterim does not currently hold third-party security certifications. When that changes, it will be listed here.
If you believe you have found a security issue, email the details and steps to reproduce it. Please do not access other customers’ data or disrupt the service while testing.
support@auterim.com