Trust
Identity before
any ring.
A Dials request without a scoped session can't search a number, dial a line, or send a message. Every accepted request writes a signed event you can hand to an auditor, a partner, or a regulator.
At a glance
What Trust enforces on every action.
Scoped sessions
Who. What. From where.
Every Dials session resolves to a subject, a scope set, and an issuing audience. In local mode the session resolves on your machine. In cloud mode it resolves through the platform identity service. Either way, no scope, no action.
- Subject + scope + audience
- Token replay protection
- Per-tenant key material
- Fail-closed by default
Audit ledger
Forward-only.
Forever-readable.
Usage events on Dials carry the operator, the seat, the carrier, the DID, the duration, the disposition, the consent state, and the trace. We don't rewrite events. We don't delete them silently.
- Hash-chained events
- Trace ID per request
- Per-region storage
- Exportable on request
The integrity check
Every accepted action.
Every recorded reason.
Every accepted action writes a signed, hash-chained usage event.
No event is rewritten. Replays mark themselves explicitly.
The audit ledger only ever grows. Exportable any time, any region.
Open the trust center.
Inspect controls, certifications, and the audit ledger format on the trust center page.