Telephony Privacy Policy for Secure Calls
A call to support, contract negotiations via Microsoft Teams, or an employee’s voicemail: In business telephony, data is constantly being generated that reveals information about customers, projects, and internal processes. Data protection in telephony therefore involves much more than just recorded calls. Anyone who uses VoIP, cloud PBX, and mobile workstations must treat call content, connection data, phone numbers, and access rights as part of their IT security.
For Swiss companies, the following applies: A modern telephony solution can effectively balance data protection with day-to-day operations. The key factors are a well-designed architecture, clear rules, and ongoing support that doesn’t end with the initial implementation.
Why Telephony Data Is Particularly Sensitive
Even without call recordings, a phone system generates valuable information. Call logs show who called whom and when, how long a call lasted, and, in some cases, which location or extension the call was made from. When combined with CRM entries, Teams presence data, or tickets, this provides a detailed picture of customer relationships and workflows.
This becomes particularly critical with features such as call recording, voicemail-to-email, CTI integration, and call statistics. These features provide real benefits in everyday operations: quality assurance, traceable customer service, faster processing, and improved accessibility. At the same time, they expand the range of systems and people who can access telephony data.
Data protection, therefore, does not mean disabling these functions across the board. It means clearly defining their purpose, appropriately restricting access, and not retaining data longer than necessary. Whether it’s a small trust office or a company with multiple locations: the scope of the measures may vary, but the fundamental question remains the same. Who needs what data, for what purpose, and for how long?
Data Protection for Telephony Starts with a Data Card
Many risks arise not from a single technical error, but from unclear lines of responsibility. The phone system runs in the cloud, call logs are also stored in the CRM, voicemails are sent to personal inboxes, and an external IT partner has administrative access. Without a clear overview, it is impossible to reliably handle either security measures or information requests.
A data map helps keep things organized. It should document what data is processed in the PBX, SIP trunk, SBC, Microsoft Teams, end devices, and connected applications. This includes, in particular, phone numbers, call data, voice recordings, voicemails, presence information, and contact data from LDAP or CRM.
Data flow is equally important. Are voicemails forwarded via email? Is call data transferred to a help desk system? Are backups located in Switzerland, the European Economic Area, or elsewhere? Especially with cloud services, it must be clear which processors are involved and what contractual and technical safeguards apply.
This overview is not just a paper exercise. It facilitates error analysis, the removal of entries that are no longer needed, and migration planning. It also quickly reveals whether a seemingly simple additional feature is inadvertently distributing sensitive data to multiple systems.
Using Records and Analyses in a Legally Compliant Manner
Call recordings are useful in sales, customer service, or when placing binding orders. However, they are not a standard practice that should be enabled as a precaution for all calls. Before recording a call, there must be a clear purpose, such as training, quality control, or documenting an explicit agreement. Those involved must be clearly informed before the call begins.
In Switzerland, the Data Protection Act and labor law regulations apply. When communicating with individuals in the EU, the GDPR may also apply. The specific legal assessment depends, among other things, on the nature of the communication, the group of individuals involved, the purpose, and the location. For special cases such as financial services, health data, or customer files requiring special protection, a legal review is recommended.
In practice, proportionality is what matters most. Not every call needs to be recorded, and not every recording needs to remain available for six months or longer. Define a retention period, establish access controls, and document who is authorized to listen to, export, or delete recordings. An automated announcement at the beginning of the call ensures transparency, but it is no substitute for a well-thought-out policy.
Call logs also deserve attention. Aggregated analyses are often sufficient for capacity planning. If a department only needs to know how many calls were answered and how long the wait time was, it does not necessarily need the complete call data for individual employees.
Technical Security Measures for VoIP and Cloud PBX
Secure telephony is based on several coordinated layers. The PBX alone cannot guarantee security if access credentials are distributed without proper controls or if the network does not have clearly separated voice traffic.
The first step is to implement a consistent authorization model. Employees need their own direct extension and the functions required for their role. Administrative privileges should be limited to a small number of specifically designated individuals. Shared administrator logins make it difficult to maintain accountability and should be avoided. Where possible, multi-factor authentication should be used to secure portals, softphones, and administrative interfaces in particular.
SIP credentials must be treated the same as passwords for business-critical systems. Secure passwords, regular reviews of extensions, and the deactivation of unused accounts reduce misuse. This isn’t just about data protection—it’s also about cost protection: Compromised SIP accounts can result in expensive unauthorized international calls.
A session border controller plays a central role at the boundary between the internal network and the service provider. It manages SIP connections, reduces the attack surface, and supports the secure interconnection of sites, SIP trunks, and Microsoft Teams. Complemented by Firewall Rules, separate voice VLANs, and a monitored Internet connection create an architecture in which voice traffic does not run unchecked on the corporate network.
Encryption protects the transmission, but not necessarily every instance of data processing. SIP signaling and voice data should be transmitted in encrypted form, provided the environment supports it. Equally important are encrypted backups, controlled access to these backups, and a recovery test. A backup that cannot be restored in an emergency does not serve its purpose.
Embedding Data Protection in Day-to-Day Operations
Even the best configuration loses its effectiveness if it isn’t adjusted following a personnel change. A clear onboarding and offboarding process is therefore an essential part of telephony. New employees are assigned defined roles. When an employee leaves, softphone access, Teams calling, voicemail forwarding, mobile devices, and any remote access privileges are promptly deactivated or transferred.
Personal availability also requires rules. Including a personal cell phone number in a business call forwarding setup can be convenient, but it blurs the lines between personal and professional data and responsibilities. It’s better to use central business numbers, clearly defined call groups, and controlled call forwarding. This ensures that employees remain reachable even when they’re on vacation or leave the company.
Regular audits are useful without overburdening operations. Active extensions, administrative rights, call forwarding, and recording rules can be reviewed on a quarterly basis. In larger environments, audit logs and managed services help ensure that changes remain traceable. It is crucial to have a dedicated point of contact who can coordinate technical changes with operational requirements.
Integrate Microsoft Teams without multiplying data paths
Microsoft Teams is becoming the central hub for chat, meetings, and phone calls in many companies. However, this integration should not result in the same phone call data ending up in multiple siloed systems. A centrally managed cloud PBX with a direct connection to Teams simplifies the management of phone numbers, IVR, groups, business hours, and permissions.
With Winet, the Ayrix PBX can be natively integrated with Microsoft Teams without the need for separate Teams add-ons or additional SBC components that require licensing. For businesses, this means fewer interfaces, clear lines of responsibility, and a telephony architecture that can scale from individual workstations to multiple locations.
Before implementing this feature, it’s worth taking a moment to assess the situation: Which Teams users need an external phone number? Which calls need to appear in the CRM? Should voicemails be available in the email inbox or directly in Teams? The right answer depends on processes and security requirements, not just on a list of features.
Data-protection-compliant telephony doesn’t have to be complicated. It is achieved when phone numbers, the PBX, the network, access, and collaboration are planned as an integrated infrastructure. By taking these points into account during the next upgrade of your phone system, you’ll reduce risks, avoid future setbacks, and create a communication solution that both employees and customers can rely on.