Security

Explicit boundaries, inspectable execution.

Runovio uses server-resolved workspace authorization, encrypted workspace credentials, immutable versions, bounded tools, and deliberately limited operational telemetry.

Private workspace isolation

A verified Clerk user receives one empty private workspace. Clients cannot select or submit workspace identity, and sharing, invitations, and organizations are not part of the current product.

Credentials and provider data

OpenAI keys are write-only, workspace-scoped, and AES-256-GCM encrypted at rest. There is no global key fallback. OpenAI requests set store: false; secrets, complete prompts, and provider bodies are excluded from logs and traces.

Read-only GitHub tools

Short-lived GitHub App installation tokens are never persisted. Repository and tool identity are pinned server-side, requests are GET-only, and Runovio cannot comment, merge, modify files, or rerun workflows.

Report a concern

Send security reports to [email protected]. Do not include credentials, private prompts, or sensitive repository content.