Security at Andora.

Provider key encryption

Real provider API keys use envelope encryption: a random data encryption key wraps the secret with AES-256-GCM, and that key is itself wrapped under a workspace master key (optional AWS KMS). Keys are decrypted only in memory at proxy forward time and are never returned after save (last four characters for display only).

Master-key rotation is supported for operators via authenticated admin tooling. Contact security@useandora.com for questionnaire detail.

Virtual keys

Customer-facing sk-andora-… keys are shown once at creation or rotation. At rest we store a SHA-256 hash plus a short suffix for masking. Instant revoke is supported by deactivating the key record.

Data handling

By default, proxy logs store metadata only (tokens, cost, latency, model, status). Prompt and response bodies are not stored unless a workspace opts in to request-body storage (required for response cache). Zero-retention mode disables cache and body storage. Configure via workspace data settings.

Retention purge runs daily. See the published sub-processor list.

Proxy controls

Per-key rate limits, request size limits, upstream timeouts, provider hostname allowlisting (SSRF protection), spend reservation against hard budgets, and optional fail-open / fail-closed when budget counters are unavailable. Streaming responses are supported with mid-stream budget cutoffs.

Access control

Product access uses NextAuth sessions with optional TOTP 2FA and Azure AD SSO. Workspace roles (Owner, Admin, Viewer, Developer) gate Shield and team APIs. Governance adds SCIM provisioning stubs for IdP onboarding.

Compliance roadmap

See our DPA summary and sub-processors. Third-party penetration tests and SOC 2 are on the compliance roadmap — contact us for questionnaire status.