Security
Security is a practice, not a claim.
Language access is part of your operations. So are the decisions about access, devices and data. Here is how Phontus supports those decisions.
Current capabilities
Specific controls.
Clear responsibilities.
The organization operating Phontus controls its sites, staff access and transcript settings.
- Session trafficEncryption in transit
- Session traffic is encrypted in transit between the kit, the Phone Line and the interpreting service.
- People & permissionsSite-level access controls
- Designated administrators manage staff accounts and access by site. Transcript access follows the organization’s settings.
- Sites & devicesManaged device enrollment
- Your administrators manage sites and device enrollment through the admin console, alongside staff accounts.
- Session handlingConfigurable transcript retention
- Transcript retention is set per site in the admin console. Your organization decides what is kept, for how long and who can read it.
Review your deployment
Get the detail
your team needs.
A security review should cover your actual data flow and requirements. Ask for the current security summary and discuss the details below before deployment.
Our privacy documentation identifies open questions about audio handling, retention defaults, deletion timing and subprocessors. Review those with us for your setting.
Request a security discussion →What to review togetherData flow for kit sessions and phone conversationsAudio processing and any audio retentionTranscript defaults and deletion requestsAdministrator roles and site access boundariesDevice enrollment and loss handlingSubprocessors and where data is processedRead the privacy documentation →
Let’s start a conversation