Security

Built for teams that need proof, not promises. Here’s exactly how we protect your data, your credentials, and your spend.

AES-256-GCM encryption at rest

Every secret · API keys, connector credentials, MFA secrets, SSO client secrets · encrypted with a rotating master key. Master key lives in a separate key store; runtime access is audit-logged.

Tenant isolation by default

Row-level security at the DB. Cross-tenant reads are physically impossible, not just filtered in code. Every query carries a tenantId belt + a projectId braces where relevant.

Auditable per-call ledger

Every token burn has a double-entry ledger row keyed to the LLM call it paid for. Export as CSV / JSON for compliance. Merkle-chained so tampering is detectable after the fact.

Always inspectable audit log

Every compute decision, settings change, and admin action lands in an audit log. Browsable, searchable, exportable. Nothing is hidden from you, including from your own admins.

SSO + MFA + scoped API keys

OIDC SSO (Okta / Azure AD / Google Workspace / Auth0). TOTP MFA with one-time backup codes. API keys with per-key scopes + rate-limit overrides + IP allowlist. Optional enforced-SSO mode disables password login entirely.

Prompt-injection guard

Every LLM-proxy request passes through a 19-signature injection detector. Stacked jailbreaks blocked with a 400; suspicious prompts logged + surfaced via response headers. Optional Lakera Guard escalation for ambiguous cases.

Single-token-burn guarantee

You only ever see one charge · ours. Startup lint + runtime audit verify no code path leaks to a native provider's billing on your behalf. Multi-provider redundancy with per-provider circuit breakers keeps the promise intact during incidents.

Secret redaction + PII masker

AWS keys / GitHub tokens / Stripe keys / JWTs / credit cards · automatically detected + redacted in prompts before they leave our proxy. PII masker scrubs outputs before they return to your client.

Defence in depth

Our threat model assumes attackers will compromise one layer. Independent controls at each layer mean compromise of any single one doesn’t expose customer data.

Incident response

Compliance + audits

Product surfaces for security teams

Reporting a vulnerability

Email security@tokenone.io. We respond within one business day. PGP key on request. We do not pursue good-faith researchers who follow responsible disclosure (90-day coordinated disclosure window, no public proof-of-concept until fix has shipped).

We run a bug bounty for qualifying vulnerabilities; email us for scope + reward table.