Security

Autowind can read authorized context and prepare work, but outbound messages stay behind explicit human approval. Review is a product boundary, not a suggestion: you remain responsible for what leaves the office in your name, and the product keeps that decision in your hands.

Source references are retained with briefs, commitments, and drafts so important claims can be traced back to the connected record that produced them.

OAuth access and refresh tokens are encrypted with AES-256-GCM before database storage. The encryption key is held separately in the production environment, not stored alongside the encrypted token.

Production connections use TLS in transit. Other durable application data relies on managed infrastructure encryption at rest and access controls around the production environment.

Clerk provides authentication, and application routes protect workspace data behind an authenticated identity. Repository and integration operations are scoped to a workspace, and a connected integration account cannot be silently attached to another workspace.

Credentials are requested with integration-specific scopes and are decrypted only when the application needs to call the provider on the workspace's behalf.

We do not currently claim SOC 2, ISO 27001, or an independent penetration-test certification. Those are roadmap controls, not implied guarantees. We review dependencies and production access as the service matures.

No internet service can promise perfect security. If we confirm an incident that materially affects your data, we will investigate, contain it, and notify affected customers as required.

Send suspected vulnerabilities or security questions to hello@autowind.dev with enough detail to reproduce the issue. Please do not access data that is not yours or disrupt the service while testing.