Purpose
Why record? Orders, quality, security, proof of a request: the purpose comes before the feature.
TELEPHONY · CALL RECORDING
Switching recording on in 3CX takes minutes. Defining the purpose, the access rights, the retention period and the safeguards is the work that has to come first.

BEFORE SWITCHING RECORDING ON
Why record? Orders, quality, security, proof of a request: the purpose comes before the feature.
Which extensions, queues or flows need to be recorded? There is no need to record the whole system.
Who may listen, download or delete? Technical privileges must mirror roles that are genuinely authorised.
How long is the audio really needed? The period must be decided and documented up front, not left at the default.
01 · FRAMEWORK
Recording a business call is not just a phone system feature. It means processing personal data and, where employees are involved, it can also engage the Italian rules on remote monitoring.
The GDPR and Article 4 of the Italian Workers’ Statute answer different questions. The first concerns lawfulness, transparency, security and retention; the second concerns the safeguards that apply when a tool can enable remote monitoring of employees’ activity.
The practical point: before deciding how to configure 3CX you have to settle the purpose and the context. Only then do you define recording, access, retention and storage.
02 · PRIVACY
A recorded conversation contains personal data belonging to the people on the call. The controller must therefore identify a specified purpose and an applicable legal basis under Article 6 GDPR. Legitimate interest may be one of the available bases, but it is not automatic and has to be assessed case by case.
In an employment relationship consent is usually a problematic basis, because the employee’s position can make it hard to treat it as freely given. Where the processing presents a high risk — for instance because of its nature, scale or monitoring capability — the need for a DPIA under Article 35 must also be assessed.
Notice must be given both to employees and to external parties, in a way consistent with the processing. Retention must likewise be defined in advance and limited to what the purpose requires: there is no single period valid for every company and every use.
03 · EMPLOYMENT
Article 4 distinguishes tools from which remote monitoring may arise from tools the employee uses to perform their work. The fact that a phone system is a work tool does not, on its own, settle the question.
If the recording function introduces further processing that can be used to reconstruct or monitor an employee’s activity, it must be assessed in concrete terms whether the safeguards of the first paragraph apply: a collective agreement or, failing that, authorisation from the national labour inspectorate.
The third paragraph also ties the usability of the information collected to adequate notice to the employee about how the tools are used and how checks are carried out, as well as to compliance with data protection law.
There is no technical shortcut: a PBX setting does not by itself make the processing lawful. The configuration has to reflect decisions already taken at organisational, privacy and employment level.
04 · 3CX
Once the scope is defined, 3CX lets you apply it granularly. This is where the technical design has to match what the company has stated and documented.
SCOPE
Recording can be governed per user and, in queues, through dedicated options: the same rule need not apply to every call.
MODE
Rights can allow or prevent starting and stopping a recording during the call, depending on the process chosen.
ACCESS
Visibility, deletion and operations on recordings depend on roles and permissions. They should be granted only to those who genuinely need them.
NOTICE
Phone system announcements can be placed in the call path to support informing the other party before recording starts.
RETENTION
Storage and retention policies must reflect the period the company has decided and allow predictable management of recordings.
STORAGE
Recordings can sit on the instance or be archived on supported remote storage, such as SMB, SFTP, SharePoint, Google Storage or AWS S3.
WHERE MY WORK ENDS
I start from the purpose the company has defined and translate that scope into the phone system configuration: users and queues, recording mode, announcements, permissions, storage, retention and technical documentation of the installation.
I do not choose the legal basis for the company, I do not draft the privacy notice and I do not handle union agreements or labour inspectorate authorisations. Those sit with the data controller and, where needed, with the lawyer, the employment adviser or the DPO.
The references below are there to orient you in the legal and technical framework. How they apply depends on the specific case.
TECHNICAL REVIEW
We start from the purpose and from how calls actually flow. That shows which parts of the system to configure and which decisions need to be settled first with your own advisers.
Let’s review your setup ↗