Clawdio Your AI assistant.

Privacy policy

How Clawdio handles data.

Effective April 3, 2026. This is the operational privacy baseline for Clawdio SaaS. It is not a sector-specific notice for HIPAA, FERPA, or other regulated deployment programs.

Minimum neededWe should only collect the account, workspace, billing, and runtime data needed to run the service.
Tenant-scopedWorkspace content, browser state, files, and configuration stay tied to the tenant that created them.
Provider paths matterConnected model providers, channels, and payment processors may process data under their own terms.

What we collect

Core categories

  1. Account data such as name, email, user identifiers, and session state.
  2. Workspace data such as tenant names, settings, prompts, files, audit records, and usage metadata.
  3. Billing data needed to activate, maintain, or cancel service through payment providers.
  4. Operational telemetry such as health, quota, runtime, worker, and recovery events.

How we use it

Product operation, security, and support

  1. To authenticate users, provision workspaces, and keep tenant access separated.
  2. To run Clawdio features, connected model routes, browser actions, and workspace recovery flows.
  3. To bill, prevent abuse, monitor health, investigate incidents, and support customers.
  4. To improve reliability and product quality using operational data appropriate to the service.

Important limits

What this page does not promise

  1. This page does not by itself make Clawdio HIPAA, FERPA, GLBA, or CJIS compliant.
  2. Regulated-sector deployments may require stricter providers, retention controls, contracts, and isolation than the default SaaS path.
  3. Customers remain responsible for the data they choose to enter or connect, especially in regulated workflows.
Read terms Read fair use