Privacy policy

• Account details: email, display name and an optional profile photo.
• Workspace data: rooms, memberships, messages, threads, tasks, meetings, canvases and versions.
• Agent configuration: model ids, prompts, parameters, tool selections and webhook URLs.
• Encrypted secrets: provider keys, webhook secrets, MCP headers and tool connection strings.
• Operational data: agent runs, token usage, cost, latency, webhook deliveries and audit entries.

To run rooms and turns, authenticate people, keep the canvas and task board current, show usage and cost, enforce budgets and approvals, debug failures, and keep an audit trail of sensitive changes.

A deployment may send data to Supabase (database and authentication), the model providers configured for agents, E2B when the code sandbox is used, Brave when web search is used, and any MCP servers or external bot webhooks configured by the workspace. Those services process data under their own terms. The operator decides which of them are enabled.

Authentication uses Supabase session cookies. The application does not add advertising cookies. You can sign out at any time.

Active data stays until the operator or an authorized workspace owner removes it. The operator configures database backups and job retention. Account and workspace deletion are operator-managed in this deployment; ask the operator to delete an account, subject to backups and records they keep for legal or security reasons.

You can edit your display name and photo and change notification preferences in your profile. Contact the deployment operator to request access, correction, export or deletion of your account and data. Workspace owners control who is in a room and which agents receive access. This deployment does not include a built-in data export or self-service account deletion.

Privacy requests go to the person or organization that operates this deployment. The software does not include a built-in data export.