Compliance
Assistant operations need clear boundaries and reviewable signals.
This page summarizes Thalovant's compliance posture for private hubs, public hub publishing, BYOS, accounts, access control, telemetry, and operational review.
Product Boundaries
Thalovant separates public hub discovery from private workspace operation. Users can keep hubs private, expose public hubs to the world, and bring their own skills while retaining responsibility for the content, sources, and services they publish or connect.
Security And Access Controls
The product is designed around tenant ownership, scoped access, hub and client specifications, RBAC posture, ACL policy, protected authentication flows, and auditable workspace actions.
Operational Signals
Thalovant surfaces telemetry, watcher events, status history, billing posture, GitOps context, runtime health, and connection state so assistant infrastructure can be reviewed instead of treated as a black box.
Compliance Review
Enterprise deployments may require security questionnaires, procurement review, data processing terms, deployment architecture review, SSO, SLA commitments, or additional controls. This page is a product baseline and should be reviewed before formal compliance reliance.