Trust Center

This Trust Center summarizes the public-facing operational posture for Telovix. It is intended to help operators understand the product boundary, control-plane trust model, and supporting legal and privacy resources around the platform.

Telovix is built for telecom runtime visibility and controlled enforcement. That makes trust, renewal safety, revocation clarity, and operator-visible lifecycle state core parts of the product rather than add-on material.

• Sensor private keys are generated locally on the Sensor side and are not created by Console
• Post-enrollment Sensor traffic uses issued identity over mutual TLS rather than reusing the bootstrap token
• Renewal, overlap, manual renew-now, and revocation are first-class product workflows with operator visibility
• Public trust, privacy, legal, and service documents remain available from the website footer and this page
• The product boundary stays explicit: Console is the control plane, Sensor is the runtime boundary

Telovix is designed to keep runtime and trust operations visible to the operator. Observe is the default state, and supported enforcement only happens after explicit operator advancement.

Operators should expect to use trust-health views, alerting, and fleet triage to decide when a Sensor needs renewal, manual intervention, or revocation.

Customers remain responsible for their own rollout governance, deployment standards, and telecom operational context when moving from observe into stronger runtime action.

• Privacy Policy for data handling, website processing, and retention expectations
• Service Agreement for the commercial relationship and service commitments
• Legal Notices for corporate and website notice details
• Contact page for trust questionnaires, procurement, privacy, and legal routing