Introduction
This work was written in Turkish. The summary on this page is a translation; the citation gives the original title in parentheses.
The “Regulation on the Sharing of Confidential Information” (the “Regulation”) was published in the Official Gazette No. 31501 of 4 June 2021, to enter into force on 1 January 2022, in order to determine the scope, form, procedures and principles for the sharing and transfer of information that constitutes bank secrets and customer secrets. What does this mean, first of all? It means that everyone who falls within the scope of the Regulation must be in compliance with its provisions as of 1 January 2022!
I will explain below who has to comply with what.
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*
In order to determine the scope, form, procedures and principles governing the sharing and transfer of information constituting bank secrets and customer secrets, the “Regulation on the Sharing of Information Constituting Secrets” (the “Regulation”) was published in Official Gazette No. 31501 of 4 June 2021, to enter into force on 1 January 2022. What does this mean, first of all? It means that everyone falling within the scope of the Regulation must, as of 1 January
2022, have brought themselves into compliance with the provisions of this Regulation!
Below I shall explain who must comply, and with what.
On the other hand, given the close relationship of the subject with the legislation on the protection of personal data, it is also extremely important and necessary to examine the Regulation together with the data protection legislation in order to determine what obligations it imposes, and on whom.
Before doing so, it is worth recalling, for a better understanding of the Regulation, an amendment made a short while ago. Article 10 of Law No. 7222 “Amending the Banking Law and Certain Other Laws”, published in Official Gazette No. 31060 of 25 February 2020 to enter into force on the date of its publication, had introduced certain amendments to the Banking Law No. 5411. These amendments, however, had been criticised, in particular for not being clear and precise. The fact that the subject has this time been addressed in a Regulation is welcome, since it provides more detailed explanations of the personal data processing activities carried out in the banking sector. It must be pointed out, however, that the Regulation also raises many new questions.
Finally, it should be noted that the Regulation was issued by the Banking Regulation and Supervision Board (“BDDK”), and that the body responsible for implementing its provisions is likewise the BDDK. I shall come back later to certain confusions in this respect as well.
* Academic / Attorney
In this article I shall try to explain who must do what as a result of this Regulation. Where it cannot be clearly determined what must be done, I shall set out my own view and proposal.
I. Some Basic Concepts
For the provisions of the Regulation to be fully understood, the basic concepts it contains must undoubtedly be clear and definite, since the meaning of these concepts is needed in order to determine the scope of who must comply with these provisions. At this point, the first criticism must be directed at the fact that some of the concepts in the Regulation are not directly defined, since this causes confusion in understanding its provisions.
Let us try to clarify some of the basic concepts in the Regulation by reading them together with the banking legislation and the legislation on the protection of personal data.
1. The Distinction between Customer Secret and Bank Secret
What first strikes one in the Regulation are the concepts of “bank secret” and “customer secret”. These concepts appear in Article 1 of the Regulation, entitled “Purpose and scope”, but, although they are important enough to explain the purpose of the Regulation, they are not explained in the definitions article. Yet these concepts are both very broad and closely related to other legislation. Since the Regulation governs the sharing and transfer of information constituting secrets, these concepts ought to be explained in more detail.
The first point to be addressed in this respect concerns what the word “secret” denotes. In its general sense, a secret is a matter that carries the danger of harming the personality rights of its owner and whose remaining confidential is of importance both personally and socially; and since it may contain confidential information about any situation, the types and classifications of secrets are also very numerous.1 Indeed, our legislation contains many provisions dealing with the concept of secret. On this basis, the word secret may be defined as “information that is generally not known to everyone and that cannot or is unlikely to become generally known to everyone unless disclosed by those who know it”.
The concept of customer secret, for its part, is regulated in Article 4(3) of the Regulation in the same way as in Article 73(3) of the Banking Law No. 5411 (“Law No. 5411”): “Data belonging to natural and legal persons that come into existence, specifically in connection with banking activities, after a customer relationship has been established with banks become customer secrets”.
In the remainder of the paragraph we see that the concept of customer secret is explained somewhat further, and that “any information showing that a natural or legal person customer is a customer of the bank” is also included within the scope of customer secret. To explain these provisions with an example:
The moment Bank X establishes a customer relationship with a third party, Y, a natural or legal person, all data belonging to Y are customer secrets for Bank X. Any information serving to show that Y is a customer of Bank X is likewise included in the concept of customer secret. Furthermore, information relating to Y that arises from transactions carried out within the framework of this relationship after the customer relationship between Bank X and Y has been established also falls within this scope.
It must be underlined, however, that the scope of the obligation of confidentiality is not limited to
the concept of customer secret. I shall set out the scope of this obligation below.
Another point to note here is that data belonging to legal persons have also been included in this concept. Under the provisions introduced by Law No. 6698 on the Protection of Personal Data (“KVKK”), only the data of natural persons are regarded as personal data. The data of legal persons fall outside the concept of personal data, and hence outside the scope of the KVKK, unless they contain information relating to a natural person.2
As to the question at what point personal data may come into play, it will be possible to speak of personal data only where there is a customer secret relating to a natural person. This means that data belonging to natural persons will in any event be subject to the provisions of the KVKK, since they are regarded as personal data whether or not a customer relationship is established. Data constituting customer secrets that relate to natural person customers will therefore be customer secrets in addition to being personal data. By contrast, customer secrets belonging to legal persons do not fall within the scope of the KVKK, but are solely customer secrets and fall within the scope of the Regulation.
Another type of secret in the Regulation is the bank secret. This concept, however, is not directly defined and is more vague than that of customer secret. Before the Regulation, there was no consensus in legal scholarship on what this concept means. While a large majority regarded the bank secret as a superset that includes the data of legal and natural persons with whom no customer relationship has been established, as well as customer secrets and sensitive data, others define the bank secret as information relating to the bank’s own internal structure. Although the Regulation does not provide a direct definition, Article 5(5), entitled “Cases exempted from the obligation of confidentiality”, offers some guidance. The expression used there, “Information constituting bank secrets that does not constitute customer secrets and contains only information belonging to the bank…”, gives the impression that the bank secret contains only information belonging to the bank. From the general usage of the Regulation, too, I take the view that the bank secret refers only to information relating to the bank’s own internal structure. This concept, however, needs to be clarified directly rather than by mere impression.
2. Pseudonymisation, Processing and Aggregation
The concepts of pseudonymisation and aggregation contained in Article 3 of the Regulation, entitled “Definitions", are not concepts frequently encountered in Turkish legislation. Let us look at the definitions of these concepts, which we know mainly from the European General Data Protection Regulation (“GDPR”), and of the concept of processing.
a. Pseudonymisation
In the GDPR, this concept (kimliksizleştirme) appears as “Pseudonymisation”. In Turkish legislation, this concept was first regulated in the Regulation on Personal Health Data of 21 June 2019. Pseudonymisation, a technical term that now appears for the second time, means stripping personal data of their explicit identifiers and generalising them by means of technologies such as blurring, encryption, key coding and data sharing, thereby removing the features that make the person identifiable.
In the Regulation at hand, the concept of pseudonymisation is defined, similarly to its earlier definition, as “the processing of data relating to the customer in such a way that they cannot be associated with the identified or identifiable natural/legal person customer concerned, provided that technical and administrative measures are taken to that end, and without being combined with other data kept in a different environment”, that is, in such a way that they cannot be associated with the customer concerned.
This concept differs from anonymisation, a method frequently used within the scope of the KVKK. Although the two methods are similar, and are confused with each other, in that both mask a person’s data such as name, address or card number by removing or encrypting them, the difference between them is that pseudonymisation is reversible. In the pseudonymisation method, when it becomes necessary to re-attribute the data to the person, the data making the person identifiable can be retrieved again by converting this information by means of separately kept information, such as an encryption key.3 This method offers a temporary solution rather than placing the data in the category of non-personal data. Indeed, as can be understood from Recital 26, owing to developing technologies re-identification is possible even after this method has been applied. For this reason, pseudonymised personal data continue to be personal data under the GDPR.4
Indeed, looking at the Regulation’s definition given above, the obligation to take technical and administrative measures stands out. In parallel with the obligation imposed by the EU on processors to take technical measures, this obligation is in the nature of a precaution against the possibility of re-identification.
A problem that may arise with the Regulation’s definition is that it is limited to the concept of customer. Starting from such a limitation, the question arises whether pseudonymisation needs to be applied when the data of persons who have not yet become customers are shared.
b. Data Processing
Another concept dealt with in the definitions article is data processing. In that article this concept is defined, similarly to the definition of processing of personal data in Article 3 of the KVKK, as “any operation performed on data, such as obtaining, recording, storing, keeping, altering, reorganising, disclosing, sharing, transferring, taking over, making available, classifying or preventing the use of data” .
Unlike the KVKK, however, it is not specified by what means these operations performed on data must be carried out for there to be data processing. In the KVKK, processing of personal data exists only if the activities mentioned in the definition above are carried out “by fully or partially automated means or by non-automated means provided that they form part of a data filing system”. As far as can be understood from the definition, there is no such requirement for data processing within the meaning of the Regulation. Moreover, Article 4(2) of the Regulation includes every kind of data processing within the obligation of confidentiality. Since no limitation has been made, it is therefore understood that the performance by any means whatsoever of the activities mentioned in the definition is regarded as data processing within the framework of the Regulation.
Considering that the concepts of a data filing system and of partially automated means, which are controversial under the KVKK, are not included in the Regulation, and that every kind of operation performed on data, regardless of the means used, is included within the scope of the obligation of confidentiality, it would not be wrong to say that the Regulation takes a broader approach to the concept of data processing and is therefore, in this respect, more protective than the KVKK’s approach to personal data.
c. Aggregation
The concept of aggregation, likewise contained in the definitions article of the Regulation and not previously encountered by us, is defined as “the processing of data relating to the customer by combining them with data relating to other customers for statistical purposes such as grouping, summarising and aggregate presentation, in such a way that they cannot be associated with an identified or identifiable natural/legal person customer”. Under the provision of the Regulation, this method must be preferred wherever it is possible to apply it.
Although this concept resembles anonymisation, it differs from it in certain respects. First, the subject matter of aggregation is not personal data but “data relating to the customer”. I explained the differences between these above. Moreover, whereas personal data can only be data that identify or can identify a natural person, the customer data subject to aggregation include data relating to both natural and legal persons. The aim was therefore to avoid conceptual confusion by using the concept of aggregation in respect of customer data as the counterpart of the concept of anonymisation in respect of personal data. I must say that this is an appropriate way of thinking and an appropriate method.
II. The Obligation of Confidentiality
The Regulation essentially concerns the obligation of confidentiality. Some basic concepts have been explained above. Those explanations concerned what is to be kept secret. Let us now look at how, and in what manner, it must be kept secret.
1. What Is the Obligation of Confidentiality?
The main rule on the obligation of confidentiality is laid down in Article 4 of the Regulation, entitled “Obligation of confidentiality”, which repeats Article 73 of Law No. 5411. Accordingly, under the obligation of confidentiality, “those who learn secrets belonging to banks or their customers by reason of their capacity and duties may not disclose such secrets to anyone other than the authorities expressly empowered by law in this respect”.
Moreover, this obligation will continue after leaving office.
2. The Scope of the Obligation of Confidentiality under the Regulation
The remainder of Article 4 of the Regulation contains explanations concerning the scope of the obligation of confidentiality.
First, as mentioned above, the Regulation does not limit the activity of data processing with regard to the methods used, since, unlike the KVKK, no wording to that effect is used in the definition of the concept. Compared with the Regulation, the definition of processing of personal data in the KVKK contains the additional wording “of personal data by fully or partially automated means or by non-automated means provided that they form part of a data filing system”. The fact that this wording is not included in the Regulation suggests that, for the purposes of engaging in data processing under the Regulation, it is of no importance by what means the operations performed on data are carried out.
Indeed, in Article 4(2) of the Regulation the obligation of confidentiality is framed so as to apply also where information constituting customer secrets is obtained and learned by methods that are not automated or do not form part of any data filing system. What does this mean? Even a bank’s writing down information constituting a customer secret on an ordinary piece of paper is processing within the meaning of the Regulation and is subject to the obligation of confidentiality. It should therefore be noted that the scope of the obligation has been drawn very broadly in this respect.
Article 4(3) of the Regulation governs the position of data relating to persons with whom no customer relationship has been established: “Even where no customer relationship has been established, obtaining and learning information constituting customer secrets held by another bank is also subject to the obligation under the first paragraph.”
The position of information that does not constitute a customer secret of another bank either is governed by Article 4(3) of the Regulation: “Data relating to natural and legal persons, including personal data, that exist before a customer relationship is established with banks and that do not constitute customer secrets of another bank, although not falling within the scope of secrets on their own, become customer secrets when they are processed, alone or together with the data arising after the establishment of the customer relationship referred to in the third paragraph, in such a way as to show that the person concerned is a bank customer.”
In the light of these explanations, let us examine through an example how customer secrets and the scope of the obligation of confidentiality are determined:
Example: Bank A has, as of this moment, established a bank–customer relationship with B A.Ş. The natural person C is a customer of Bank D. Bank E is holding talks with F A.Ş., which is, however, currently a customer of Bank A. The natural person G has customer status with no bank.
Accordingly, whether the following concrete examples constitute customer secrets or fall within the obligation of confidentiality is as follows:
| Situation | Customer Secret | Obligation of Confidentiality | |||
|---|---|---|---|---|---|
| Data belonging to B A.Ş., for Bank A | ✓ | ✓ | |||
| Data belonging to the natural person C, for Bank D | ✓ | ✓ | |||
| Data belonging to F A.Ş., for Bank D | × | ✓ | |||
| Data belonging to F A.Ş., for Bank A | ✓ | ✓ | |||
| Data arising after the establishment of the customer relationship between Bank A and B A.Ş. | ✓ | ✓ | |||
| Any information showing that the natural person C is a customer of Bank D | ✓ | ✓ | |||
| Data belonging to the natural person C, for Bank A | × | ✓ |
| Data of the natural person G, as regards Banks A, D and E | × | × |
|---|---|---|
| Where certain pre-existing data of the natural person G are used together with data arising after the establishment of a customer relationship with Bank A, the pre-existing data, for Bank A | ✓ | ✓ |
| Where certain pre-existing data of the natural person G are used together with data arising after the establishment of a customer relationship with Bank A, the pre-existing data, for Banks D and E | × | ✓ |
3. Exceptions to the Obligation of Confidentiality
Article 5 of the Regulation deals with the exceptions to this obligation in a clear, systematic and comprehensive manner.
First of all, under Article 5(1), sharing information constituting bank secrets or customer secrets with the authorities expressly empowered by law in this respect will not constitute a breach of the obligation of confidentiality.
Under Article 5(2), provided that a confidentiality agreement is concluded and that the sharing remains limited to the specified purposes, sharing information constituting bank secrets or customer secrets in the situations listed in that paragraph will not constitute a breach of the obligation of confidentiality. The situations that will not constitute a breach of the obligation of confidentiality include banks and financial institutions exchanging any kind of information and documents among themselves, either directly or through the Risk Centre or through companies to be established by at least five banks or financial institutions; work on preparing consolidated financial statements; risk management and internal audit practices; and the provision of information and documents in valuation work carried out for the purpose of selling shares representing 10% or more of a bank’s capital.
I do not think it necessary to explain here, one by one, all the exceptions contained in the Regulation. Since the concept of customer secret is clearly defined in the Regulation and the activity of processing is framed so as to cover every kind of processing, it is entirely appropriate that the exceptions to this obligation have been drawn broadly. Otherwise, a result would ensue that goes beyond its purpose and cannot be applied in practice, which is an extremely dangerous situation for legal regulations. Moreover, it must be underlined that banks are in any event already subject to the KVKK and to the other banking legislation, and have now additionally become subject to this Regulation. For banks, therefore, the customer secret and other obligations still apply; above all, there is no exception whatsoever as regards their being subject to Article 6, which I discuss below. I must therefore state that I consider it appropriate that the exceptions to the obligation of confidentiality have been regulated so broadly and in such detail, in order to keep the banking and financial sector functioning while secrets are kept.
III. General Principles on the Sharing of Information Constituting Secrets
Article 6 of the Regulation, entitled “General principles on the sharing of information constituting secrets”, lays down the rules to be observed when such information is shared. Looking at the provisions of this article, they can be seen to be consistent with the principles set out in the KVKK.
1. The Principle of Proportionality
Although proportionality is a contested concept, the principle of proportionality is explained in the Regulation. Accordingly, this principle is to be understood as meaning that the stated purpose cannot be achieved without some of the data shared.
The article in question sets out the minimum elements that must be present in order to conclude that the principle of proportionality is satisfied:
i. the sharing must contain only as much data as is required by the stated purposes with which it is associated, ii. it must be demonstrable that all the data or data sets contained in the sharing are necessary for achieving the stated purposes,
iii. if those purposes can still be achieved when the data to be shared are aggregated, pseudonymised or anonymised, these methods must be applied, iv. if the customer whose information is to be shared is not also a joint customer of the parent company, the controlling shareholder or the group company, the information constituting secrets relating to the natural/legal person customer concerned that is to be shared with those parties must not be of such a nature as to render that customer identified or identifiable, and the methods mentioned above must be used, v. the parties with whom information is to be shared and the methods of sharing must be designed so as to create the fewest possible copies of the data.
However, in order to be able to say that this principle, which is defined in detail in the Regulation, is satisfied, it must be checked that all the conditions listed above are met. This check, which must be carried out because the principle of proportionality has to be applied, may cause a functional problem in the business processes of banks.
2. Sharing of Data Relating to Natural Person Customers
Article 6(2) of the Regulation governs the sharing of information constituting secrets that relates to natural person customers, and states that such sharing must comply with Article 4 of the KVKK. Since banks are in any event subject to the KVKK, it is appropriate that no conflict has been created in this respect and that consistency has been achieved by referring to the KVKK.
3. Active Request or Instruction of the Customer
Article 6(3) of the Regulation governs the customer’s request or instruction for the sharing of information. The phrase “even if explicit consent has been obtained”, which was added to Article 73(3) of Law No. 5411 by the amendment of 25 February 2020 mentioned above, has been subjected to much criticism, including by ourselves, for instance that explicit consent has been rendered ineffective and that the concept of explicit consent has lost its credibility in the eyes of the legislature. The main reason for these criticisms is that, despite the existence of explicit consent, a separate request or instruction is expected from the customer. Accordingly, even if the customer has given explicit consent to the sharing, the transfer cannot take place unless he has communicated a request and instruction to that effect to the bank concerned. Article 6(3) of the Regulation maintains this position unchanged, excluding only the cases exempted from the obligation of confidentiality.
On the other hand, through the wording “the customer’s giving explicit consent to the sharing of his information or giving a request or instruction may not be made a precondition for the services to be provided by the bank” in that paragraph, explicit consent is prevented, in line with the KVKK, from being made a condition of service.
Another point that needs to be addressed here again concerns the distinction between natural and legal persons. Under Article 6(3) of the Regulation, explicit consent and the customer’s request or instruction are kept separate from each other. One of the questions that comes to mind is whether, while explicit consent under the KVKK applies to natural persons, the customer’s request and instruction alone will suffice for legal persons, since legal persons do not fall within the scope of the KVKK. If that is to be the position for legal persons, the conclusion is that, where data belonging to natural persons are transferred, the conditions both of explicit consent and of the request and instruction must be met. But in that case, what conditions must the explicit consent to be obtained from legal persons satisfy, and by reference to what are they to be determined? These matters remain unclear under the Regulation; in our opinion, the reason why this question exists at all is that, instead of regulating on the basis of the main principles contained in the Law on the Protection of Personal Data, the BDDK – rightly – approached and regulated the subject solely from the perspective of the banking and financial sector. It is precisely this that creates these contradictions and, as a result, gives rise to numerous problems in practice. Yet what those affected by such regulations and practitioners expect is that such regulatory bodies come together, take all sensitivities into account and adopt regulations that do not create contradiction, uncertainty and confusion.
The provision on the form of the customer’s request or instruction is contained in Article 6(4) of the Regulation. Accordingly, the request or instruction:
• May be obtained in writing or, provided that it is provable, by means of a permanent data storage medium. The definitions article explains a permanent data storage medium as follows: any instrument or medium, such as a text message, e-mail, the internet, a CD, a DVD or a memory card, which enables information sent by or to the customer to be recorded in a way that allows it to be examined for a reasonable period in accordance with the purpose of the information and to be copied without alteration, and which allows access to that information in unaltered form. It is appropriate that, in addition to the written form, such an alternative method suited to electronic environments has been introduced.
• May cover more than one transaction, and a request or instruction relating to transactions of a continuing nature may be of indefinite duration, provided that it can be cancelled or amended by the customer at any time by the same methods by which the request or instruction was obtained. At this point, where the bank obtains a request or instruction for only a single transaction, the question comes to mind whether it must be cancellable or amendable by the customer
or not. Reading the provision a contrario, it is not mandatory for a request or instruction obtained for a single transaction to be cancellable and amendable.
• As a rule, must be capable of being queried and viewed by the customer through the distribution channels for electronic banking services.
Article 6(6) of the Regulation is likewise a provision involving the customer’s active request or instruction. Accordingly, with regard to transactions for which the sharing of information constituting customer secrets is mandatory, it is provided that the initiation of the transaction concerned by the customer, or the entry of an order by the customer through the distribution channels for electronic banking services, will take the place of the customer’s request or instruction. In this way, by adapting to the digital world, the requirement of an active request needed for data sharing under the Regulation, in addition to explicit consent under the KVKK, is fulfilled through transactions initiated by the customer and through order entry, without impairing the user experience.
4. Transfer of Data Abroad
Article 6(11) of the Regulation deals with transfer abroad. The BDDK has been given the power to prohibit the sharing of any data constituting customer secrets or bank secrets with third parties abroad. This power has brought the BDDK, in addition to the Personal Data Protection Board, into play as regards the transfer of personal data. It remains unclear here which institution will have competence where the sharing and transfer of the personal data of bank customers is concerned.
In addition, under the same provision, the principle of reciprocity is taken as the basis for sharing. Accordingly, where data are shared with parties located in a country that does not observe the principle of reciprocity, the Board will be able to restrict, suspend or prohibit such sharing. Considering all these provisions, it would not be wrong to say that the scope of these powers conferred on the BDDK in relation to transfer abroad is very broad. Indeed, it should be pointed out that the Board is empowered not only to prohibit, but also to supervise whether the principle of reciprocity required for transfer abroad is being observed. I must state that, while the transfer of personal data abroad still constitutes one of the most unclear and most controversial aspects of the subject under the KVKK, I do not consider it appropriate to introduce such a provision on top of that. The power to determine the principles and procedures for the transfer of personal data abroad has been conferred on the Personal Data Protection Board (“KVK Board”), and the KVK Board has published many regulations and explanations on the subject, including the criteria to be taken into account. Nevertheless, the matter of transfer abroad still remains unclear and constitutes a major problem in practice. While, on the one hand, all practitioners in this field wish the matter to be resolved as soon as possible in the way most workable in practice, it was not appropriate to introduce a new provision on the subject, to empower a new institution and, by laying down a criterion, to give rise to the question of what becomes of the criteria previously determined by the KVK Board. I therefore anticipate that, rather than being beneficial, this provision will make the subject more complicated, particularly with regard to the competent institution.
IV. The Information Sharing Committee
Under Article 7 of the Regulation, entitled “Information Sharing Committee”, banks are obliged to set up an Information Sharing Committee. The responsibility of this committee is to coordinate the sharing of information constituting customer secrets and bank secrets, including sharing under Article 5 of the Regulation, taking into account the principle of proportionality referred to in Article 6, and to assess the appropriateness of incoming requests for sharing and record these assessments.
Since banks are institutions that process and transfer personal data intensively, it is important that they have set up committees in their KVKK compliance projects. With this new provision, it will be useful for banks to establish a structure in which the information sharing committees they set up draw on the members of the KVKK committee, are selected from among those members, and in which the two committees work in cooperation.
Conclusion
In the light of all the explanations given above concerning the Regulation, I must state that, in general, it is a Regulation that needed to be issued and that I consider it appropriate that this regulation has been adopted. However, I regard it as a major shortcoming and drawback that some of the concepts I have mentioned above are either not defined at all or not sufficiently defined, and that the different regulatory bodies dealing with the same subject do not, by coordinating among themselves, issue joint legislation.
Under the amendment made in February and the Regulation concerned, an administrative (semi-autonomous) body such as the BDDK has been granted powers with regard to its own sector. As is well known, in our developing and changing world, information technologies are also advancing day by day. It is likely that similar powers will in future be granted to many more sectors as well. How the regulations adopted will affect one another, however, is ambiguous. For this reason, because of these sector-specific powers, it will become difficult to determine who is responsible for the legal problems that arise. Because of this ambiguity, and in order to avoid problems for banks in practice, the publication by the BDDK in the coming period of a guide on how, and in what manner, the provisions of the Regulation are to be applied, containing concrete examples of the obligations imposed under the Regulation, would make a positive contribution to resolving the problems likely to arise.
On the other hand, the Regulation also brings with it many problems concerning transfer abroad. This is because, in the transfer of information constituting customer secrets, the confidentiality provisions contained in the Banking Law No. 5411 following its amendment by Law No. 7222 will, being special and later law, be treated as special statutory provisions vis-à-vis the KVKK. Indeed, the Regulation that forms the subject of this article was also issued pursuant to this amendment. This means that, in the transfer of data constituting customer secrets to third parties, a request and instruction will also have to be obtained from customers even where explicit consent has been obtained. Requiring the customer’s request and instruction virtually disregards the concept of explicit consent as dealt with under the KVKK.
Finally, although there is nothing objectionable about adopting sector-specific regulations, care must be taken that these regulations are not of such a nature as to damage the principle of the unity (integrity) of the law. Otherwise, there will be a danger of legal certainty being undermined. Moreover, if a holistic approach to protection is not taken as the basis for sector-based regulations that may be introduced in future, it will be inevitable that many more problems are encountered in practice.
Footnotes
- Hilal Üçüncü, Medeni Yargılama Hukukunda Kişisel Verilerin ve Sırların Korunması, İstanbul, Onikilevha Yayıncılık, 2019, s. 21 vd. ↑
- KVKK Rehberi, “Tanımlar”, Erişim Tarihi: 05.06.2021, https://www.kvkkrehberi.com/tanimlar ↑
- Termsfeed, Pseudonymization, Anonymization and the GDPR, Erişim Tarihi: 05.06.2021, https://www.termsfeed.com/blog/gdpr-pseudonymization-anonymization/ ↑
- ICO, What is personal data?, Erişim Tarihi: 05.06.2021, https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/what-is-personal-data/what-is-personal-data/ ↑
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.

