Introduction
This work was written in Turkish. The summary on this page is a translation; the citation gives the original title in parentheses.
At a time when new developments occur every day in the field of personal data protection, an important step has most recently been taken, again by the Board, in the form of a series of public announcements. I should point out that the formation of a branch of law is a matter that goes well beyond enacting legislation specific to the subject and developing a theory. For a branch of law to form, the enactment of norms of positive law is a necessary element, but it is not sufficient on its own. What is needed, rather, is for concrete cases on the subject to arise, for the legal norms that have been enacted to be applied to those cases and for decisions to be given on them. Accordingly, alongside the legislation on the subject, there must be a field in which that legislation is applied.
In this way the concept of case law, which is an indispensable and at the same time complementary element of law, will emerge. For only then can a branch of law be said to have formed. The field of personal data protection is at exactly this point. Since the publication of Law No. 6698 on the Protection of Personal Data (KVKK), the steps taken, particularly as regards statutory rules, have produced an extensive body of legislation. The decisions given by the Board on the complaints made to it and in the context of concrete cases are allowing practice and case law specific to the subject to develop. The publication of the applications, complaints and breach notifications made under the KVKK is also important, because it brings concrete examples to light.
Full text
This text is a translation of the Turkish original, prepared for this website. Numbers in square brackets are the page numbers of the original; sources in the footnotes are given as in the original. For citation, the original publication (PDF) is authoritative.
Assoc. Prof. Dr. Murat Volkan Dülger*
At a time when new developments in the field of personal data protection occur with each passing day, an important step has most recently again been taken by the Board, in the form of a series of public announcements. I should point out that the formation of a branch of law is a matter that goes far beyond enacting legislation specific to the subject and constructing a theory. Although the enactment of norms of positive law is an indispensable element for the formation of a branch of law, it is not sufficient on its own. What is needed, rather, is that concrete cases relating to the subject arise, that the legal norms enacted are applied to those concrete cases and that decisions are given on them. Accordingly, alongside the legislation on the subject, there must be a field in which that legislation is applied. In this way the concept of case law, which is an indispensable and at the same time complementary element of law, will emerge. For only then can one speak of a branch of law having come into being.
The field of personal data protection is at precisely this point. Since the publication of the Law on the Protection of Personal Data, comprehensive legislation has come into being as a result of the steps taken, in particular as regards statutory regulation. The decisions given by the Board following the complaints lodged with it and in the context of concrete cases are bringing about the practice and case law specific to the subject. Moreover, the publication of the applications, complaints and breach notifications made under the Law is important in that it brings concrete examples to light. For this reason, the growth of awareness of personal data protection, its becoming the subject of concrete cases and, finally, the giving of decisions on those cases under the relevant legislation are welcome, above all because a law of personal data protection is thereby taking shape step by step.
At this point, too, I shall avoid as far as possible giving theoretical information based on the legislation and shall try only to assess the decisions in question and to explain what needs to be borne in mind in practice. For to date I have tried to write, in the form of books, articles or commentaries, on the law of personal data protection and on almost every subject it touches upon. From now on, particularly in my assessments of concrete cases, I shall go straight to the decisions without entering into theoretical matters at all.
The two main points that form the subject of this paper may be summarised as follows:
• By its Decision No. 2019/9 of 24.01.2019, the Personal Data Protection Board published a Public Announcement. This announcement introduced rules on applications to the controller. In this context, an attempt was made to clarify the uncertain points concerning the time limits for applying to the controller.
• Secondly, by decisions of various dates and numbers, the Personal Data Protection Board published those of the data breach notifications made to it by controllers that it considered it necessary to publish.
I shall assess these two main points in turn.
1. Decision No. 2019/9 of 24.01.2019 of the Personal Data Protection Board
Article 13 of Law No. 6698, entitled “Application to the controller”, regulates the procedure and time limit for the data subject’s application to the controller. Under that provision, the data subject submits his requests concerning the application of the Law to the controller in writing or by other methods determined by the Board. The controller, for its part, must conclude the requests contained in the application within the shortest time, depending on the nature of the request, and within thirty days at the latest.
Article 14 of the Law, entitled “Complaint to the Board”, regulates the data subject’s lodging of a complaint with the Board. Under that provision, where the application made under Article 13 is rejected, the reply given is found insufficient or the application is not answered in time, the data subject may lodge a complaint with the Board within thirty days of the date on which he learns of the reply and, in any event, within sixty days of the date of the application.
At this point, however, questions arise concerning certain uncertain matters. These questions, and the answers given by the Board’s decision in question, are as follows:
• Where the controller replies to the data subject’s application within 30 days, from when does the period for complaining to the Board start to run, and how much time does the data subject have?
The data subject applied to the controller under Article 13 of the Law, and the controller replied to the data subject within 30 days in accordance with that article. In that case the data subject’s right to complain to the Board under Article 14 of the Law begins to run from the date on which the controller replied. Suppose that the controller replied to the data subject after 15 days: the thirty-day period within which the data subject may exercise the right to complain to the Board starts on the day following the date on which that reply was given. In such a case, therefore, the data subject’s total period is 45 days. Accordingly, there is no complaint period of 60 days in any event from the date on which the data subject applied to the controller.
Data subjects who are going to submit their requests to the controller must pay attention to this. In fact this is clear from the provision of the Law. However, the existence of a period of 60 days in any event has given rise to the mistaken impression that, whether or not a reply is given, the data subject has 60 days from the date of applying to the controller in which to apply to the Board. Although this is already apparent from the provision of the Law, an attempt has been made to dispel that mistaken impression by expressly underlining the point.
• Where the controller does not reply to the data subject’s application within the 30-day period allowed to it, how many days does the data subject have to lodge a complaint?
The data subject applied to the controller under Article 13 of the Law, and the controller did not reply within the 30-day period allowed to it by that article. In that case, since the data subject’s right to complain to the Board will begin at the end of the 30-day period, he has the right to lodge a complaint with the Board within 60 days of the date on which he applied to the controller.
I should point out that the situation in which the controller does not reply to the application made to it by the data subject is in no way determined by the provision of the Law. What is more, the article contains a plainly erroneous wording. Under the article, the case in which the controller does not reply is tied to the date on which the data subject learns of the reply. But how is the data subject to learn of the reply when no reply has been given? In administrative law there is in fact a rule, in particular in Law No. 2577 on Administrative Jurisdiction Procedure (İYUK), that where an application to the administration is met with silence for a certain period, the application is deemed to have been rejected and the relevant time limits for bringing an action start to run from the end of that period (Art. 10). Under the KVKK, however, the application is not always made to the administration; the addressee may be a natural or legal person having the status of controller, or a legal person governed by public law or by private law. Accordingly, it is not possible to apply the provisions of the İYUK here by analogy either.
It is therefore important that the Board has clarified this situation, as this removes the differences of interpretation that would arise. Nevertheless, in my opinion this clarification should not be considered sufficient, and the plain error of wording in the Law should be corrected.
• Where the controller replies to the data subject’s application after the 30-day period allowed to it has expired, how is the data subject to exercise the right to complain?
The data subject applied to the controller under Article 13 of the Law and the controller replied, but in the meantime the 30-day period allowed to it by the relevant article had expired. In that case the data subject’s right to complain is essentially parallel to the question above. Since the controller is allowed a period of 30 days in which to reply, there should be no difference between failing to reply and replying after that period has expired. For the data subject is under no obligation to guess when the controller will reply or to wait for the reply to be given. For this reason, a reply given after 30 days have passed has not been accepted as having any effect on the time limit. In this case too, the data subject’s right to complain to the Board is 60 days from the date on which he applied to the controller. The clarification of this situation in particular has been useful.
These rules of administrative law and of the law of administrative procedure on time limits are in fact very well known to lawyers. However, since this Law addresses every section of society and it is common for individuals to make applications without the assistance of a lawyer, the Authority has, rightly, taken a decision to this effect and chosen to announce it, both in order to be able to act lawfully and in order not to cause any loss of rights.
2. Public Announcement on Data Breach Notification
On 24 January, 6 February and 14 February the Board published, in the form of public announcements, nine of the data breach notifications made to it by controllers. All of the announcements concern data breach notifications. The controllers that made the notifications were also named in these announcements.
The controller’s obligation to notify data breaches is regulated as follows by paragraph 5 of Article 12 of the Law, entitled “Obligations concerning data security”:
“Where processed personal data are obtained by others by unlawful means, the controller shall notify the data subject and the Board thereof within the shortest time. Where necessary, the Board may announce this on its own website or by any other method it deems appropriate.”
Accordingly, where personal data lawfully processed by the controller are obtained by others, the controller is placed under an obligation to notify the data subject and the Board thereof. A controller’s failure to fulfil this obligation means that it has breached its obligations concerning data security and results in the administrative fine provided for in the Law. In addition, the Board is empowered to publish these notifications where it considers it necessary.
As stated above, all of these announcements concern data breach notifications. Rather than explaining each of these announcements one by one and repeating myself, I consider it more correct and useful to draw a distinction according to the matters which the Board took into consideration in the notifications it published. For the announcements in question are in any case available on the Board’s official website, and there would be no point in repeating them here1. For this reason, I shall not set out the announcements below but shall make an assessment by singling out the points that stand out in them. In this way I shall try to identify the matters to which controllers need to pay attention.
a. The criterion of necessity as to which data breach notification the Board will announce
By the provision of the Law referred to above, the Board is empowered to announce those of the breach notifications made to it that it considers necessary, and on the basis of that power it has published the notifications which it was satisfied were necessary. My first criticism at this point is that the criteria the Board takes into account in deciding which of the data breach notifications made to it to announce are not sufficiently definite. Having regard to the provision of the Law, it is understood that it considered the notifications it announced to be necessary, but it is unclear on what basis that conclusion as to necessity is reached. On what basis does the Board draw the distinction between “needs to be announced” and “does not need to be announced”?
That said, when one looks at the content of the announcements published, it is seen that they reproduce the notification made by the controllers. The features common to these notifications undoubtedly point to the data breach notifications which the Board finds important and thinks ought to be announced. Thus, although the provision of the Law does not expressly determine which notifications are to be announced and on what basis, it can be understood which ones are considered necessary when the notifications announced by the Board are taken together. I must nevertheless state that I am in favour of a brief clarification of the basis on which data breach notifications published in the form of a public announcement are considered necessary.
b. The number of persons affected by the data breaches contained in the notifications
When one looks at the notifications published, it is seen that some of them also state the number of persons affected by the data breaches in question. It may therefore be concluded that, in announcing the notifications made to it, the Board takes into account the scale of the data breach that has occurred. What is striking at this point is, in particular, that the number of data subjects whose data may have been obtained as a result of cyber attacks carried out against the controller is stated. In my opinion the Board, giving priority to data breaches that carry the danger of affecting more data subjects than others, considered it necessary to publish the notifications containing those breaches.
c. The nature of the personal data that are the subject of the data breaches contained in the notifications
Some notifications also set out what the personal data that were the subject of the data breaches in question consisted of. I should point out that the personal data unlawfully obtained do not consist solely of personal data that may be described as more general and basic, such as first name and surname. What is at issue is a breach extending from the data subject’s first name and surname to all of his identity and contact details. Beyond that, even a medical report containing special categories of personal data has been the subject of a data breach. The quantity, density and nature of the personal data that are the subject of data breaches have been another matter to which the Board attaches importance. I therefore think that the Board announces the breach notifications made where personal data of great number and importance are unlawfully obtained by third parties as a result of a cyber attack or leak.
It appears that the Board makes a public announcement having regard to a certain intensity and importance. However, I think it would be more appropriate for the Board to lay down and announce criteria known to everyone in this regard. For some examples we have seen in practice indicate that certain controllers refrain from making a data breach notification for fear of a public announcement and assume a possible risk in this respect. Ensuring certainty as regards public announcements will also be capable of preventing unlawful practices of this kind.
d. An attack on one of several companies that have a business relationship with one another
In my opinion the most striking common feature of the data breach notifications announced by the Board is the situation of controllers that have a business relationship with one another. The great majority of the notifications involve a cyber attack on a company. As a result of the cyber attack on that company, several controllers that have a business relationship with the company were naturally also affected.
Today, in order to conduct and develop their commercial relations, companies work in certain fields with other controllers that offer solutions specific to the matter concerned. This is as much a necessity of today’s commercial life as it is a need. In such a case, the personal data that are specific to the matter for which the business relationship is established and necessary for that matter will be shared with the company with which the business relationship is established. Suppose, for example, that online store X establishes a business relationship with courier company Y in order to manage its order tracking and delivery operations. In that case the contact and address details of the data subject who shops at store X will be shared with company Y. As a result of a cyber attack on company Y, the customers of store X, and hence store X itself, will also be affected.
In line with the concrete cases that are the subject of the notifications published, a car rental company, in order to manage the damage and accident processes of the vehicles it rents to its customers, entered with another company into a business relationship. The cyber attack on the company with which the business relationship was established also affected many of the controllers to which it provides solutions.
There is, however, a debate as to whether natural or legal persons who process data on behalf of the controller under the contract they have concluded with it, and who may even themselves be regarded as controllers, are required to make a data breach notification to the Personal Data Protection Board. By stating in its decision “that, where personal data held by the processor are obtained by others by unlawful means, the processor shall notify the controller thereof without any delay”, the Board has in fact clarified the matter at least to some extent.
Accordingly, processors are under no obligation to notify the data breach directly to the Board. As the Law also states, the addressee of all the obligations arising from the Law is the controller. The obligation to make a data breach notification therefore also lies with the controller; and the Board has stated that the processor’s obligation to notify is owed to the controller.
The only point that remains contentious here is what is to happen where the concepts of controller and processor coincide in the same person. In that case, it must be examined whether the person who bears both capacities at the same time holds and/or processes the personal data in the capacity of controller or in that of processor. The answer to this will also determine liability. It should not be forgotten, however, that many persons having the status of controller also act at the same time as processors for the same or other data sets. If, despite this distinction being drawn, the capacities of both controller and processor coincide in respect of the data sets that gave rise to the data breach, it must then be accepted that the capacity of controller prevails and that such persons are under the obligation to make a breach notification. However, an express regulation of the relationship between processor and controller and of their obligations, as in the GDPR (Art. 28), would be a more appropriate solution.
e. Making the data breach notification within 72 hours
As is well known, Law No. 6698 was drafted on the basis of the EU’s Directive 95/46/EC. Approximately two years after 7 April 2016, the date on which Law No. 6698 entered into force, the EU introduced a new instrument and repealed that Directive. The GDPR, which entered into force on 28 May 2018, introduced far more comprehensive and detailed rules than the Directive, its predecessor in the protection of personal data.
As regards data breach notification, Article 12(5) of Law No. 6698 provides that, where processed personal data are obtained by others by means not in conformity with the law, the controller is to notify the data subject and the Personal Data Protection Board thereof “within the shortest time”. However, there is no clarity as to what is to be understood by the notion of “the shortest time”. The GDPR, by contrast, lays down an express rule on this matter in Article 33, providing that the data breach notification must be made within 72 hours.
The Board, too, has taken the GDPR as its basis on this matter and decided along those lines. Accordingly, it decided as follows: “Considering that, in data breach notifications, the purpose of notifying the Board and the persons affected by the breach is to ensure that measures are taken which make it possible to prevent as soon as possible, or to minimise, the adverse consequences that may arise for those persons as a result of the breach; and that, on the other hand, the European General Data Protection Regulation, which repealed the European Union’s Directive 95/46/EC, the source of Law No. 6698, contains, unlike the Directive, detailed provisions on data breach notifications; in order that no inconsistency should arise among the decisions to be taken by the Board on this matter and that standardisation may be achieved in practice; by Decision No. 2019/10 of 24.01.2019 of the Personal Data Protection Board; that the expression ‘within the shortest time’ in the provision of Article 12(5) of the Law, ‘Where processed personal data are obtained by others by unlawful means, the controller shall notify the data subject and the Board thereof within the shortest time….’, be interpreted as 72 hours and that, in this context, the controller notify the Board without delay and at the latest within 72 hours of the date on which it learns of this situation”. Accordingly, in our country too, notification must now be made within 72 hours of the moment at which the data breach occurs.
However, preventing further attacks or leaks after a cyber attack or data leak, or gathering evidence of the attack or leak by digital forensic methods and taking the necessary measures, may require more than 72 hours. In fact this is a period that differs according to each specific situation. With this in mind, the GDPR includes in Article 33 the provision “Where the notification to the supervisory authority is not made within 72 hours, it shall be accompanied by the reasons for the delay.” Taking this provision as its basis, the Board likewise included in its decision the statement “that, where the controller is unable, for a justified reason, to notify the Board within 72 hours, the reasons for the delay shall also be explained to the Board together with the notification to be made,”.
In addition, the same decision provides that, after the controller has identified the persons affected by the data breach, the data subjects are also to be notified within the shortest reasonable time, directly where the data subject’s contact address can be reached and, where it cannot, by appropriate methods such as publication on the controller’s own website. As can be seen, no specific period is prescribed here and reference is made to a “reasonable time”. While reasonable time is an expression that must be assessed in relation to each case, I think that one should not wait too long after the notification made to the Board.
f. The form of the data breach notification
One of the most important innovations introduced by the decision is that the use of the “Personal Data Breach Notification Form” available on the Authority’s website has been made mandatory for the notification to be made to the Board. I think that this too is an appropriate step in that it facilitates the functioning of the Board, which receives notifications in a wide variety of forms and assesses them. The decision also states that, where it is not possible to provide the information contained in the form at the same time, that information must be provided in stages without delay. In addition, the controller is required to record the information on data breaches, their effects and the measures taken, and to keep these records ready for examination by the Board, which is likewise appropriate.
g. Data breach notification by controllers established abroad
It was decided that, where the data breach occurs at a controller established abroad, that controller too is to notify the Board in accordance with the same principles if the consequences of the breach affect data subjects resident in Türkiye and the data subjects benefit in Türkiye from the products and services offered. Thus, in a manner akin to the territorial scope laid down in Article 3 of the GDPR, an obligation to notify the Personal Data Protection Board has been introduced where those affected are in Türkiye, even if the breach occurs abroad. The scope of application of Law No. 6698 has thereby been extended in a sense. This aspect of the decision needs to be taken into account in particular by persons who are located abroad and process the personal data of persons living in Türkiye.
h. Preparing a data breach procedure
In the Board’s decision in question, it was decided “that a data breach response plan be prepared, covering matters such as to whom within its own organisation the controller will report in the event of a data breach and the determination of who within its organisation bears responsibility for the notifications to be made under the Law and for assessing the possible consequences of the data breach, and that this plan be reviewed at regular intervals”.
In this way, the requirement to lay down principles and procedures, previously introduced for matters such as the processing of personal data and their erasure, destruction and disposal, has also been introduced for the procedure to be followed in the event of a data breach. Controllers conducting a compliance process in particular, and those advising them in this regard, must now add this heading to their compliance processes as well. It is abundantly clear that this too is a step in the right direction. Making arrangements of this kind in advance ensures that swift and effective steps are taken at a moment of crisis and that the damage is kept to a minimum.
i. Uncertainty as to whether a data breach has occurred although a cyber attack has been carried out
In some of the data breach notifications made, while there was no doubt that a cyber attack had been carried out, it had not yet been possible to determine whether data had been copied as a result. Faced with these notifications, the Board stated that the examinations into the matter were continuing and decided to announce the data breaches in question at that stage.
Furthermore, is the controller also obliged to notify the Board at a stage at which it has established that a cyber attack has been carried out but has not yet been able to determine whether there has been a data breach? Although in two of the published notifications the notification was made when a data breach was not yet certain, does failing to make it mean that the obligations concerning data security have been breached? For the Law speaks of the case where there is a data breach; it does not speak of the case where a data breach is suspected. And is it right for the Board to open an examination upon complaint or of its own motion and to impose a sanction at the very moment when the controller is trying to understand whether there has been a cyber attack and a data leak?
In my view the answer to both questions is no. Indeed, depending on the features of the specific situation, even if 72 hours have passed, where the attack and its consequences have not yet been fully understood and no report on them could be produced, or where an ongoing attack is being fought, the Board should not impose a sanction. I should also state that, having regard to the Board’s present composition and its generally positive and constructive attitude, I think it would not impose such a sanction where there is no intentional omission on the part of the controller. This is, of course, entirely my personal opinion.
Conclusion
Above, the steps taken by the Board have been dealt with under two main headings. The first of these concerns the Board’s clarification of a matter which, having regard to the provision of the Law on the subject, is capable of giving rise to misconceptions and differences of interpretation. Under the second heading, the announcement, within the power conferred by the Law, of those of the data breach notifications made to the Board that are considered necessary was examined. In this context an attempt was made to understand why, among the notifications made, the Board published the notifications in question. The matters on which the Board dwells and to which it attaches importance in data breaches were thereby identified.
While both headings have been explained above in terms of their content, these developments show in general the Board’s efforts towards the formation and consolidation of the law of personal data protection. For this reason I confine myself, as regards the specific subjects dealt with, to the explanations I have given above. At this point I wish only to express my satisfaction that the Board is trying to resolve the debates arising from the errors made in the provisions of the Law and is exercising the powers conferred on it by the Law by assessing and announcing the data breach notifications made to it.
A further important conclusion to be drawn from this is that the Board is plainly taking the GDPR into account in giving its decisions. It is evident that, because of this approach of the Board, the work of harmonising our country’s personal data protection legislation with the GDPR has begun sooner than expected and that it would not even be surprising for this to be achieved within a short time. And it is abundantly clear that this is an extremely positive development for the law of personal data protection and for our country.
Footnotes
More publications on this topic
Dülger, Murat Volkan / Gümüş, Gülçin, “The Right to Be Forgotten” (Unutulma Hakkı), Essays in Honour of Prof. Dr. Yadigar İzmirli (Prof. Dr. Yadigar İzmirli’ye Armağan), Savaş Publishing, Ankara, 2024, pp. 1019–1141.
Dülger, Murat Volkan / Gümüş, Gülçin, “Assessment of the Amendments to the KVK Law on the Processing of Special Categories of Personal Data and the Transfer of Data Abroad” (KVK Kanunu’nda Özel Nitelikli Kişisel Verilerin İşlenmesi ve Yurt Dışına Veri Aktarımı Kapsamında Yapılan Değişikliklere İlişkin Değerlendirmeler), Academia.edu, 25 March 2024.
Dülger, Murat Volkan / Gümüş, Gülçin, “Our Assessment of the Decision Summaries Published by the Personal Data Protection Board on 18 July 2022” (Kişisel Verileri Koruma Kurulunun 18 Temmuz 2022 Tarihinde Yayınlanan Karar Özetlerine İlişkin Değerlendirmelerimiz), Dülger Law Office, 1 September 2022.
Dülger, Murat Volkan / Gümüş, Gülçin, “The Use of Personal Health Data as Evidence in Divorce Proceedings” (Kişisel Sağlık Verilerinin Boşanma Davasında Delil Olarak Kullanılması), Hukuk ve Daha Fazlası Dergisi (Law and More), No. 9, June 2022, pp. 76–84.
Dülger, Murat Volkan, “A Very Important Decision of the Personal Data Protection Board on Lawyers' Access to Enforcement Files Without a Power of Attorney” (Kişisel Verileri Koruma Kurulu’ndan Avukatların İcra Takip Dosyalarına Vekaletname Olmaksızın Erişebilmesine İlişkin Çok Önemli Bir Karar), Dülger Law Office, 15 August 2021.
Dülger, Murat Volkan / Gümüş, Gülçin, Personal Data Protection Law (Kişisel Verilerin Korunması Hukuku), 4th ed., Seçkin Publishing, Ankara, 2026.

