---
title: "Security & Data Handling"
description: "Security and trust information for the EvalGate platform."
canonical: "https://www.evalgate.com/security"
last-updated: "2026-10-21"
---

# Security & Data Handling

How EvalGate protects your data and keeps AI release decisions auditable throughout the evaluation lifecycle.

## Assurance boundary

EvalGate is currently a controlled beta. This page describes implemented product controls; it does not assert a default uptime SLA, SOC 2 certification, universal data-residency commitment, or guaranteed support-response time. Governance templates are controls, not certifications. Contract-specific enterprise terms exist only when written in a signed agreement.

A public approved DPA, dated subprocessor roster and processing-region schedule are not currently published. Organization SAML/OIDC remains a source candidate pending live Okta/Entra acceptance; SCIM and single logout are unsupported.

[Independent service availability observations and probe history](https://evalgate.github.io/status/). A current probe does not establish workflow acceptance or an SLA.

[Review the production adoption checklist](https://www.evalgate.com/docs/platform/production-adoption)

## Release evidence

Gate results, baseline diffs, judge provenance, and reviewer actions stay attached to release decisions.

## Data boundaries

Org isolation, scoped API keys, PII policy, and retention controls define what data can move and for how long.

## Control plane

Configured provider policies, budget controls and audit evidence must be verified for the workflow. A universal default hard spending cap is not available.

## Release Evidence Checklist

EvalGate treats security and governance as artifacts reviewers can inspect at merge time, not as a separate spreadsheet after the fact.

### Baseline change

### Evidence

Diff against the run or baseline used for the gate

### Reviewer question

Did quality move, and was the movement intentional?

### Judge configuration

### Evidence

Model, rubric, parser, threshold, cost, latency, and retries

### Reviewer question

Can this score be reproduced and trusted?

### Promotion workflow

### Evidence

Candidate case status, approver, timestamp, and failure mode

### Reviewer question

Was production signal reviewed before becoming coverage?

### Org policy

### Evidence

Provider allowlist, PII setting, retention state, and audit entry

### Reviewer question

Did the gate follow the org's release policy?

| Control | Evidence | Reviewer question |
| --- | --- | --- |
| Baseline change | Diff against the run or baseline used for the gate | Did quality move, and was the movement intentional? |
| Judge configuration | Model, rubric, parser, threshold, cost, latency, and retries | Can this score be reproduced and trusted? |
| Promotion workflow | Candidate case status, approver, timestamp, and failure mode | Was production signal reviewed before becoming coverage? |
| Org policy | Provider allowlist, PII setting, retention state, and audit entry | Did the gate follow the org's release policy? |

## Encryption

- All data encrypted in transit via TLS
- Secrets encrypted at rest using provider-managed encryption
- API keys stored as SHA-256 hashes — never in plaintext
- Provider keys encrypted using AES-256 via application-managed encryption keys
- Model-backed workflows are BYOK; the connected provider bills inference usage directly

## Data Retention

- Traces and evaluation results: organization policy applies; the default retention window is 90 days.
- Share links expire when an expiry is specified. Without one, a link remains available until revoked.
- Revoking a share removes access. It does not delete the underlying evidence.
- Preservation holds and governed evidence can extend retention. Backup expiry is deployment dependent.

## PII Protection

- Automatic PII redaction in shared exports — emails, SSNs, phone numbers, credit cards, and API keys
- Redaction enabled by default; opt-out available for org admins
- Export size limits (10 MB) to prevent bulk data extraction

## Audit Trail

- Full audit trail for critical mutations
- Immutable audit log entries
- Admin-only read access to audit logs

## Access Control

- Multi-tenant architecture with organization-scoped data isolation
- Role-based access control: viewer, member, admin, owner
- Scope-based API key authorization with wildcard rejection

## Compliance Framework Support

- Governance policy templates available: BASIC, SOC2, GDPR, HIPAA, FINRA\_4511, PCI\_DSS

These are policy templates for evaluation governance, not certifications.

External assurance material is provided only when it exists and is covered by the applicable customer agreement.

## Rate Limiting

- Route- and plan-aware limits protect public and authenticated API traffic
- Machine-readable rate-limit headers let clients back off without guessing