Data Use

Purpose

This Data Use statement explains how Clevis processes customer content and related data so the product can coordinate work, keep boundaries, and support agents without treating project data as free training material for unrelated systems.

Customer content

Project records, files, messages, permissions, and connected-system context remain your organization’s content. Clevis processes that content to provide the service you configure—including search, grounding answers, notifications, and agent runs.

Administrators control who can invite members, which projects exist, and which integrations are connected.

Agents and automation

Agents only operate with the tools and scopes allowed in their configuration and membership boundaries. High-impact actions can pause for approval so a person can review before changes land.

Run history may retain the records read, tools called, approvals, and outputs so teams can inspect what happened.

Model and service improvement

We may use aggregated or de-identified product signals to improve reliability, quality, and safety of Clevis. Customer project content is not sold.

Where external model providers are used for agent or chat features, prompts and outputs are sent under contractual terms that restrict use to providing the requested generation service. Specific subprocessors will be listed for enterprise reviews.

Retention and deletion

Content stays available while your workspace is active under your plan. After account closure or a verified deletion request, we remove or de-identify content according to operational backup windows and legal holds if any.

Your controls

Use membership, project scope, integration settings, and notification preferences to limit who sees what and how they are contacted. Contact support or [email protected] for data subject or deletion assistance.