Security
Last updated May 14, 2026
This page describes how Arbiter handles your data and secures the platform. It reflects current practice during the closed beta — concrete, not aspirational. If something here is unclear or you want detail beyond what’s written, reach out.
Your prompts are not training data
Prompt and response content is processed to fulfil a request and to populate the features you explicitly use — conversation history, memory entries, artifacts. It is never used to train models, never sold, and never mined for analytics. Usage metering operates on token counts, not token content.
Encryption
All traffic to arbiter.run is served over TLS. Data at rest — account records, conversations, memory, artifacts — is stored on encrypted volumes. Production deployments are expected to sit behind TLS-terminating infrastructure; the runtime binds to loopback by default and is not meant to face the public internet directly.
Authentication and access
The hosted API authenticates with per-tenant bearer tokens. Tokens are stored as SHA-256 hashes, never in plaintext, so a database read alone does not yield usable credentials. Administrative endpoints sit behind a separate admin token.
Every tenant’s data — conversations, memory graph, artifacts, schedules, run history — is scoped to that tenant. A leaked identifier never surfaces another tenant’s data; cross-tenant reads return as if the record did not exist.
Tenant isolation
Tool execution that runs code (/exec) is disabled by default and, when enabled, runs inside a per-tenant container sandbox rather than on shared infrastructure. Outbound fetches enforce SSRF guards — private, loopback, and link-local addresses are rejected — so an agent cannot be steered into probing internal networks.
Responsible disclosure
If you believe you have found a security vulnerability, please report it privately to security@arbiter.run before disclosing it publicly. Include enough detail to reproduce the issue. We will acknowledge your report, keep you updated on remediation, and credit you if you would like.
The open-source runtime ships a SECURITY.md with its in-scope / out-of-scope policy and operator-hardening notes; the same disclosure address covers both the hosted platform and the runtime.
Beta posture
Arbiter is in closed beta. We take security seriously and build with isolation and least-privilege in mind, but we are not yet making formal compliance certifications. As the platform matures, this page will be updated to reflect concrete audit and certification status.