Controlled access
We are building toward clear control over who can begin and manage sessions in each environment.
Security and responsible deployment
Phontus is being designed around privacy-conscious workflows, thoughtful session handling, and secure architecture goals. We’ll be clear about what’s available, what’s in progress, and what your organization should consider before deployment.
Our approach
These are product and architecture directions—not claims of completed certification.
We are building toward clear control over who can begin and manage sessions in each environment.
Product decisions should reduce unnecessary data collection and keep each session focused on its purpose.
Our architecture direction includes encrypted transport and careful separation of product services.
Session state, transcript behavior, and retention choices are treated as deliberate security decisions.
Security practices mature alongside the product through review, testing, and implementation work.
Organizations need guidance about kit access, headset handling, phone use, physical placement, and appropriate use.
Deployment considerations
Kit placement, headset handling, phone use, audio levels, staff access, physical privacy, network configuration, and escalation policies all shape how an interpretation service behaves in practice. We work with organizations to understand those realities without assuming every access channel has identical operational considerations.
Discuss Your EnvironmentQuestions and review
For security, privacy, or architecture questions, contact hello@phontus.live. We’ll respond with the level of detail appropriate to the current product stage.
A closer look at Phontus
Tell us where language barriers show up. We’ll tailor the demo and explore the right mix of Clinical Kits, Frontline Kits, and phone access for your setting.