Security and data

Scanners run on your agents. The workspace stores results and decisions, not your source code.

What is stored

Findings: engine, rule, severity, repository, file path and line. For secrets the location is stored, not the value.
Run details: repository, commit, pull request, the engines that ran, the gate decision and the login of who ran the build.
Exceptions with owner, approver, reason and expiry, and your gate settings.
An audit log of exception approvals, gate policy changes, SARIF uploads and ingest token changes, with who made them and when.

The audit log can only be appended to. Each entry is chained to the one before it, so a removed or changed entry can be detected. The console does not show the audit log yet.

Where it is stored

Every customer gets a dedicated environment. An order without trial days gets its own Postgres database in the region chosen at purchase. A trial, or a card order that starts with trial days, gets its own schema in the shared EU project (Paris), and nothing moves it to its own database on first payment yet.

The regions are the EU (Frankfurt), UK (London), US (N. Virginia), Canada (Montréal), Asia–Pacific (Singapore) and Latin America (São Paulo). Middle East and Africa is hosted in the EU. The default is the EU. Trials run in the EU whatever the region. Guardrail Ledger is operated by Spot Cloud B.V.

Access

Sign-in uses Spot Suite with Microsoft Entra. Guardrail Ledger keeps no separate username database. Data is scoped to your workspace and not shared across customers.