Trust
Security & data handling
Trivant is built multi-tenant from the ground up, with strict isolation across data, phone numbers, calls, prompts, billing and calendars.
Tenant isolation
Every tenant-owned record carries a tenant_id and is scoped at the service layer on every read and write. Calls, numbers, prompts, calendars and billing never cross tenant boundaries.
Encryption
TLS is enforced everywhere, including secure WSS for realtime call media. Provider secrets (Twilio, OpenAI, Stripe, email) are held in managed secret storage, never in application tables.
Payments
Stripe handles all raw payment credentials. Trivant stores only provider identifiers and non-sensitive display metadata (card brand, last 4) — never full card numbers.
AI actions are deterministic and audited
The realtime model never mutates your data directly. Every AI action — booking, texting, status changes, notifications — runs through typed, schema-validated backend tools with server-injected authorization and idempotency keys, and is written to an audit log.
Call recording
Calls the AI handles are recorded and transcribed automatically, with a spoken disclosure to the caller before the conversation starts. It's your responsibility to confirm this is compliant with the consent requirements in the jurisdictions you operate in.
Discovered data is never active until approved
Business information Trivant discovers from the public web is proposed with a source and a confidence score. It never becomes live knowledge on a call until you've explicitly reviewed and approved it.
Logging
Structured logs are PII-safe. Full audio payloads and card data are never logged. Retention policies apply to transcripts, tool events and messages.