Security
How we handle your systems and data
The honest version, including what we do not have yet.
Hosting and data residency
Arrox hosts its own components, including arrox.ai itself, on Hetzner, in the EU. Depending on the build, a client's agent may instead run on Anthropic's cloud infrastructure (the Claude platform) rather than on Arrox's own servers. Which of the two applies is documented per engagement.
Subprocessors
Arrox uses two model providers, and no others, as subprocessors: Anthropic (Claude models) and OpenAI (GPT models). Each receives only what the specific step it is running requires, not the full workflow context. Client data sent to either is not used to train third-party models, consistent with the NDA and DPA on every engagement.
Access control
Every agent gets the narrowest access it needs for its one job, not the access the system as a whole needs. In our production Slack content system, only the retrieval agent has read access to the data source, Notion; the drafting and validation agents that follow it never touch it directly. One named agent role holding data-source access is the default in every Build, not an exception.
Secrets handling
Credentials Arrox needs during a Build, API keys, service accounts, workspace access, live in the deployment environment's own secrets store, scoped to the systems that engagement touches. Arrox keeps no separate central store of client credentials. Fred, as founder and the only person who works client engagements, is the only person with access.
Encryption
Traffic between a client's systems, the agent, and the model providers runs over TLS. At rest, Arrox-hosted components rely on Hetzner's own disk encryption; Arrox adds no separate layer on top of it. For builds running on Anthropic's infrastructure instead, at-rest handling is Anthropic's, as part of the Claude platform.
Credential lifecycle
Credentials are scoped at the start of a Build to only the systems it needs, and revoked at project completion. The revocation is recorded in the credential list prepared for the handover package and confirmed to the client in writing.
Backups and incident response
Arrox operates no separate backup infrastructure of its own. Workflow data lives in the client's own systems, Slack, Notion, the client's CRM, which carry their own durability. Arrox-hosted components are redeployable from version control rather than restored from a backup, and agent runtime state on Anthropic's infrastructure relies on Anthropic's durability. There is no formal incident-response SLA today: clients get a direct line to Fred, the founder, rather than a support queue, and there is no committed response time attached to it yet.
What we do not have
No SOC 2 report. No ISO 27001 certification. No formal incident-response SLA. What is standard today is an NDA and a DPA on every engagement, regardless of size. Certifications are not in place because Arrox is a small, single-founder practice; they will be revisited as the company grows.