Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Telecom subscriber data protection governs how operators handle identity, traffic, and location data, which is regulated more tightly than ordinary personal data in both the UK and Turkey.

What Is Telecom Subscriber Data Protection?
An operator knows things about its customers that almost nobody else does: who they called, when, for how long, which websites their handset resolved, and roughly where they were at every moment the device was switched on. Telecom subscriber data protection is the regime governing that information, and it sits on top of general data protection law rather than inside it, because legislators decided long ago that communications data needed specific rules.
The categories matter, because different rules attach to each. Subscriber data identifies the customer and their account. Traffic data is generated by carrying a communication and includes the called number, duration, and routing. Location data describes where the terminal is. Content is the communication itself, which carries the strongest protection of all.
Turkey regulates the same ground through a sector regulation made by the telecoms regulator BTK, published in the Resmi Gazete in December 2020, covering the processing of personal data and protection of privacy in the electronic communications sector. It applies alongside Personal Data Protection Law No. 6698 rather than replacing it, and three features stand out for a UK reader.
First, localisation. The regulation requires operators to hold subscriber and traffic data inside Turkey. The UK imposes no such requirement, so a group that centralises its customer data platform in a European or American cloud region cannot apply the same architecture to its Turkish operation.
Second, retention. Turkish operators retain traffic data for defined periods under the telecoms framework, and separately, Law No. 5651 on internet publications imposes retention obligations on hosting and access providers. The UK approach is different in principle: there is no blanket retention duty, and retention arises from notices served under the Investigatory Powers Act on specific operators.
Third, enforcement is split. BTK supervises the sector regulation while the Personal Data Protection Board enforces KVKK, so a Turkish operator can face two authorities over one incident, with separate notification routes and separate administrative fines.
The exposure is not theoretical. Operator breaches have repeatedly exposed subscriber databases running into the tens of millions of records, and because the data combines verified identity with contact details and usage history, it feeds directly into smishing, account takeover, and number porting fraud against the same customers.
Our regulation and compliance services assess how subscriber data is actually segregated, retained, and accessed, against the obligations in each jurisdiction where the data sits.
Because PECR imposes a sector-specific duty that predates and sits alongside the UK GDPR. Regulation 5A requires notification to the Information Commissioner’s Office within 24 hours of becoming aware of a personal data breach, with an internal breach log maintained and subscribers notified where adverse effects are likely. The general 72-hour rule does not displace it for providers of public electronic communications services.
Traffic data is generated in order to carry a communication: numbers, duration, routing, and timing. Content is the communication itself. Both are protected, but content attracts the strongest safeguards and the narrowest grounds for access. The distinction has become harder to maintain as metadata grows richer, and regulators have repeatedly observed that detailed traffic data can be as revealing as content.
Yes. The sector regulation made by the telecoms regulator requires subscriber and traffic data to be held within the country, which is a localisation requirement with no UK equivalent. A group operating in both markets cannot run one consolidated customer data platform in a foreign cloud region for its Turkish subscribers, and that constraint should be settled before architecture is chosen.
Internal misuse rather than external intrusion. Retail and support staff looking up partners, relatives, celebrities, or people of local interest accounts for most reported cases. It is addressed through individual accounts rather than shared logins, logging of every lookup, proactive monitoring for same-surname and same-address queries, and making clear at induction that access is monitored.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.