How we handle your credentials and data

What we read

Configuration and metadata only: projects, workspaces, members and roles, API key metadata (names, dates, owners, never the key values), gateway settings, and aggregate usage by model. We never read prompts, responses, or any customer content.

How credentials are stored

Each organisation has its own data key. Credentials are encrypted with AES-256-GCM under that key; the data key is wrapped by a master key held as a Worker secret and rotated on demand. Plaintext exists only in memory during a verification run. Dashboards show the last four characters only.

Revoking access

Delete the admin key or API token in the provider's console. The next verification run fails closed and your page shows the facts as unverified.

Infrastructure

Everything runs on Cloudflare (Workers, D1, R2, KV, Queues, Workflows, Email Service). Billing runs on Stripe. No other sub-processors.

Reporting a vulnerability

Email security@cloudaisecurity.com. We acknowledge within two business days.