Compliance and data
HIPAA, data residency, what data events carry, and retention for Trillet OEM partners.
Early access. Trillet OEM is built and in testing with design partners. Contact your account manager to have it enabled for your account. Details may still change.
HIPAA
Trillet supports HIPAA workloads. See our Terms of Use.
A call flow in HIPAA mode keeps call recording off. Call flow settings refuses recording.enabled: true on such a flow with 409 hipaa_recording_conflict.
Data residency
Each tenant is created in a region, us or au. Its call records, transcripts and recordings are stored in that region. Events are stored in the tenant's region too, and hold references rather than transcripts: webhook payloads are built from the tenant's regional data when they are delivered.
Data in events
Call events include transcripts, summaries, extracted data and variables by default. For each webhook endpoint you can:
- turn conversation data off (
includeConversationData: false), or - keep it and mask emails, phone numbers and card-like numbers (
redactPII: true). Masking is pattern based and best effort.
Recordings are never included in payloads. A payload carries a link to the recording download endpoint, which needs a partner key with resources:read. See Events.
The event log keeps events for 30 days.
Isolation
- Each tenant is a separate workspace. A partner key can reach only its own tenants, and a key can be restricted further to a list of tenants.
- Requests naming another partner's tenant return
404. - Partner keys are stored as hashes. Webhook signing secrets are stored encrypted.
- Tenant lifecycle changes (create, update, suspend, resume, delete, restore) and phone number purchases, registrations and releases made through Trillet OEM are written to the tenant's audit log with the ID of the key that made them.
Branding
When your account has white-label enabled, new tenants inherit your branding: company name, logo, colours and theme. Webhook requests are sent from Trillet to your servers and identify Trillet (for example in the User-Agent header); your customers do not see them.
Last updated on