Security

We never train on your data.

Amdahl holds a zero-retention agreement with every commercial LLM provider it queries. Your customer data is used to generate your outputs and nothing else.

At a glance
In transit
TLS 1.2+
At rest
AES-256
LLM retention
Zero
Training on your data
Never
Compliance
SOC 2 Type II audit in progress

Controls

Who can reach your data

Role-based access

Each person has a role, and admins set what each role can read and change. API and MCP calls are written to an audit log.

Tenant isolation

Each workspace is logically isolated from every other. A dedicated cloud is available for teams that need stronger separation.

Read-only connectors

Connectors only read from your tools by default. Write-back stays off unless you ask for it.

Rolling out

Workload identity

Keyless access with OIDC

GitHub Actions jobs and Vercel functions trade the short-lived OIDC token their platform issues for a short-lived Amdahl token. No long-lived API key sits in your CI.

Email usEarly access on request
  1. 01

    Your CI job

    GitHub Actions or Vercel

    OIDC token from the platform
  2. 02

    Amdahl token exchange

    RFC 8693, checked against your trust policy

    Amdahl token, one hour at most
  3. 03

    Amdahl API

    No API key stored in CI

Trust Center

Security, data practices and retention in one place

Visit the Trust Center (opens in a new tab)trust.amdahl.ai

Vulnerability disclosure

Found a vulnerability?

Email [email protected] or use the support page. We acknowledge every report within one business day.

Email [email protected]Report it
security.txt