GDPR applies to any organisation processing personal data of EU and UK residents, regardless of sector. Telecommunications organisations face a specific configuration of obligations shaped by the personal data they collect, the regulatory environment they operate in, and the systems they use to do it.
This page covers the GDPR obligations specific to Telecommunications, the lawful bases that apply, and the implementation approach that survives supervisory authority scrutiny.
Regulatory context
Supervisory authority: BEREC (EU) / Ofcom (UK)
Key personal data categories: traffic data, location data, communications metadata, CDRs, billing records
Special category data present: Typically no — standard Article 6 lawful bases apply
Primary lawful bases: Contract (billing), Legitimate Interests (fraud prevention), Consent (marketing)
The ePrivacy Directive imposes additional obligations on telecoms beyond GDPR. Traffic data and location data generated through the use of electronic communications services are subject to stricter confidentiality requirements and require explicit consent for secondary uses (e.g. analytics, targeted advertising).
The hard part
Reconciling legal retention obligations for CDRs with GDPR erasure requests. A legal-hold mechanism must suspend erasure where national telecoms law mandates retention — and this must be documented in the ROPA.
This is the implementation decision that most Telecommunications GDPR programmes get wrong. It is also the issue most likely to appear in a supervisory authority audit or a data subject complaint.
Required controls
- Separate consent streams for communications metadata vs. marketing data
- Automated CDR retention and purge schedules with legal-hold override
- DSAR workflow querying billing, network, and CRM systems
- ePrivacy-compliant cookie and tracking model for customer portals
- Processor agreements with network infrastructure vendors
GDPR gap assessment framework for Telecommunications
A gap assessment for a Telecommunications organisation covers five areas:
1. Data inventory and ROPA
Map every system that holds personal data specific to Telecommunications operations: traffic data, location data, communications metadata, CDRs, billing records. Document the purpose, lawful basis, retention period, and third-party recipients for each. The ROPA must be current — a snapshot taken at implementation and not updated is not compliant.
2. Lawful basis audit
For each processing activity, confirm the lawful basis is documented and appropriate. Telecommunications organisations frequently find that processing that was assumed to be covered by legitimate interests has not had a Legitimate Interests Assessment completed. Where special category data is present, Article 9 requires a separate documented basis.
3. Consent management
Where consent is the lawful basis, verify that consent records meet GDPR Article 7 requirements: freely given, specific, informed, unambiguous, and withdrawable. Legacy consent from before the current privacy notice version should be assessed for adequacy.
4. DSAR readiness
Test the DSAR workflow with a synthetic request. The test should cover: intake, identity verification, data discovery across all systems identified in the data inventory, response assembly, and delivery within the 30-day deadline. Most Telecommunications DSAR gaps are discovered at the data discovery stage — systems that hold personal data but are not connected to the DSAR workflow.
5. Breach preparedness
Verify the incident log, the severity classification matrix, and the 72-hour notification workflow. The Telecommunications-specific question is: which data categories, if breached, trigger notification to individuals (not just to the supervisory authority)? Notification to individuals is required where the breach is likely to result in high risk to their rights and freedoms.
Implementation priority order
For Telecommunications organisations starting a GDPR programme:
- Data inventory — identify all systems holding personal data before configuring any controls
- Lawful basis documentation — stop processing for which there is no documented basis
- DSAR workflow — rights requests can arrive at any time; the workflow must be operational before launch
- Consent remediation — address legacy consent before running any marketing to the affected population
- ROPA — live, connected to source systems, reviewed quarterly
- Breach procedure — tested annually; DPO and legal team both trained on the 72-hour obligation