Phone system

Secure data transmission

Encrypted end to end with HTTPS, SIP TLS, and secure WebRTC.

Every call your business makes carries real information: customer details, pricing, internal decisions, personal conversations. That information deserves to travel securely, and with Voxbi it does. The platform is built around encryption in transit at every layer of the communication stack, so neither your signalling nor your media is exposed to interception on the network.

The Voxbi Cockpit (your admin web interface) is served over HTTPS, so all configuration, user management, and reporting you do in the browser travels over an encrypted connection. When a call is set up between a SIP device (such as a desk phone or softphone) and the platform, the signalling uses SIP TLS, which encrypts the call-setup messages that establish who is calling whom. When calls happen through the browser using WebRTC, both the signalling and the media stream are encrypted. Voxbi's infrastructure is hosted in the European Union, which means your data is subject to GDPR and the full weight of European data protection law.

When you'd use secure data transmission

  • A regulated business (a financial services firm, a healthcare practice, a legal office) needs to demonstrate that its phone communications meet data-in-transit security requirements.

  • An IT manager is evaluating cloud phone systems and needs to confirm that no voice traffic travels unencrypted over the public internet before approving deployment.

  • A compliance officer is reviewing the organisation's communication tools against frameworks such as GDPR, NIS2, or DORA, and needs to document how call data is protected.

How secure data transmission works in Voxbi

  1. HTTPS for the admin interface

    All access to the Voxbi Cockpit is encrypted in transit, protecting your configuration and user data as it travels between your browser and the platform.

  2. SIP TLS for call signalling

    When a SIP device registers or a call is set up, the signalling messages are protected by TLS, preventing eavesdropping on the call-setup process.

  3. Encrypted WebRTC for browser calls

    The Voxbi app and web-based softphone use WebRTC with encrypted media, so voice data is encrypted in transit between the browser and the platform.

  4. European Union data residency

    The platform runs in the European Union, keeping your communications data within GDPR jurisdiction and supporting your compliance obligations under frameworks including NIS2 and DORA.

Frequently asked questions

What does "encrypted in transit" mean in practice?

It means that while your call data or configuration is moving between your device and the Voxbi platform over the internet, it is encrypted so that a third party intercepting that traffic cannot read it. Encryption in transit is a distinct property from data being encrypted at rest on both endpoints (sometimes called true end-to-end encryption).

Does Voxbi support the encryption standards required for GDPR compliance?

Voxbi is built to meet European compliance standards including GDPR. The combination of HTTPS, SIP TLS, and encrypted WebRTC provides encryption in transit across all communication channels. For specific compliance documentation, contact the Voxbi team.

Does this apply to calls made from the mobile app as well?

Calls made through the Voxbi app on mobile devices use the same encrypted communication stack. For calls using fixed-mobile convergence over the mobile network, the signalling path differs, so contact Voxbi for specifics on that scenario.

See Voxbi in your business.

Talk to us or to a certified Voxbi partner.