Security
Security & trust.
Plain English version: customer data, secrets, and production access are walled off by default. The five approval points are the only places they cross. Stripe handles payment. We never see card numbers.
Last updated May 25, 2026. This is a working shell. Final language pending legal review.
01.
Data isolation
Every customer gets a private AOS instance. Workspace and customer-boundary rules separate your missions, evidence, and operating memory from any other customer. No shared inference contexts.
02.
Approval points are real
The five approval points (money, public claims, customer data, system changes, audit trail) are enforced at the orchestration layer. Risky actions cannot ship without your sign-off. The hold trail is logged and exportable.
03.
Secrets and credentials
API keys, secrets, and credentials are encrypted at rest with AES-256, encrypted in transit with TLS 1.2+, and accessible only to the specific agent role configured to use them. Rotation is supported and audited.
04.
Payment security
Stripe handles payment. We use Stripe Payment Element with PCI-DSS SAQ-A scope. Card details never touch our servers.
05.
Compliance posture
Targeting SOC 2 Type 1 readiness within the first 90 days of public availability. ISO 27001 and HIPAA on the roadmap for enterprise customers. Current state: documented controls, internal audits, no third-party certification yet.
06.
Incident response
Incident Response role inside the Security and Infra department runs detection, triage, and root cause. Customer-facing incidents reported within 72 hours of confirmation, with full post-mortem within 14 days.
07.
Subprocessor change notice
We notify customers 30 days before adding a new subprocessor with access to customer data. List maintained on the trust page.
08.
Responsible disclosure
Security researchers welcome. Email security at our domain. Coordinated disclosure window is 90 days unless extended by mutual agreement.