Security & Trust

Clio is a Management Loop Operating System. Its security and trust model starts by limiting what can create management work, what users can see and what the product is allowed to claim.

Core product safeguards

Organization scope

Application data access is scoped by organization. Customer Success and executive metrics are further limited to the approved Success Plan scope when that plan defines a narrower boundary.

Human confirmation

Work Evidence may create a Possible Loop. A human must confirm it before it becomes management work or activates a management intervention.

No employee scoring

Work Modes are interaction context. They do not create Loops, set priority, score performance or make employment decisions.

Evidence-based closure

Operational closure requires the Loop's required Closure Evidence. KPI movement and financial value realization are tracked separately.

Financial separation

Financial Context can be attached to confirmed work but never creates a Loop. A closed Loop is not automatic proof of recovered value.

What data categories can appear

Depending on the features a customer enables, Clio may process account and organization identifiers, configured Work Evidence, operational Loop state, Management Actions, Closure Evidence, KPI values supplied by the customer, and optional interaction context. The exact enabled sources and contractual data categories should be reviewed in the applicable agreement.

Source minimization

Clio's public product commitment is to observe only the work evidence needed by an enabled feature and to avoid turning personal context into a source of management truth. For example, a Work Mode self-assessment may calibrate how an intervention is phrased, but it cannot create a Possible Loop.

Claims we do not publish without current evidence

Hosting provider or processing region as a universal claim.
Exact retention periods that have not been verified against the enabled service and agreement.
Universal LLM provider, model-training or provider-retention claims.
Compliance certifications without current supporting evidence.
Numeric RTO, RPO, penetration-test cadence or control commitments that are not part of the current customer-specific baseline.

For procurement, the applicable DPA and technical annex should be completed from the current operational evidence before signature.

Current public documents

Privacy

Terms

DPA

Model Data Processing Agreement → — draft / customer-specific completion required before signature.

Enterprise security review

Need the current provider inventory, enabled-source map or customer-specific DPA package? Contact clio@cliocircle.com.

Request a security review