Security

How the platform is built

Data in transit and at rest

All traffic runs over TLS 1.2 or better. Data at rest is encrypted with AES-256. Secrets and connector credentials are stored in a managed secret store, encrypted with keys we rotate, and are never written to logs.

Least privilege by default

A connector is granted the narrowest scope that completes the job. Agents that only read are provisioned with read-only credentials. Write access is separate, explicit, and revocable per workflow.

Human approval gates

Any write above the threshold you set pauses for sign-off. The agent shows what it intends to change, and the evidence behind it, before anything is committed.

Audit trail

Every run records its inputs, the model that handled each step, a reasoning summary, the approver where one was required, and the exact write performed. The trail is exportable and retained according to your plan.

Tenant isolation

Each workspace is logically isolated, with per-tenant encryption keys. No customer content is used to train shared models, and no content crosses between workspaces.

Availability

The platform runs across multiple availability zones with automated failover. Scale plans carry a 99.9% uptime commitment backed by service credits.

Reporting a vulnerability

Email support@voltaxstore.com with the details. We acknowledge within one business day and will keep you updated until it is resolved. We do not pursue researchers who report in good faith.