Principles for Regulating Clarification and Explicit Consent Texts in Light of the Personal Data Protection Board’s Principle Decision Dated 18.02.2026

Contributors

همکاران

Партнер / Юрист (адвокат)

I. Legal Framework for Electronic Signatures in Turkey The main legislation regulating the legal and technical aspects of electronic signatures and the principles regarding their use in Turkey is the Electronic Signature Law No. 5070 (“ESL”), which entered into force after being published in the Official Gazette dated 23/1/2004 and numbered 25355. The purpose of the Law is to regulate the legal structure of electronic signatures, the activities of Electronic Certificate Service Providers (“ECSP”) and the usage areas of electronic signatures. In order to implement the practices in the field of electronic signature, the “Regulation on the Procedures and Principles Regarding the Implementation of the Electronic Signature Law” and the “Communiqué on the Processes and Technical Criteria Related to Electronic Signature” have been put into effect. The administrative and supervisory authority in this field is the Information and Communication Technologies Authority (“ICTA”), which is authorized to supervise the activities of ECSPs. There are also special regulations regarding electronic signatures in our basic laws: The consequences of electronic signature in Turkish law in terms of substantive and procedural law are regulated in our basic laws with an academic integrity that will complement each other. In this context,  pursuant to Article 14/II of the Turkish Code of Obligations (“TCO” ), unless there is a contrary regulation in the law, texts that can be sent and stored through a secure electronic signature meet the written form requirement; Pursuant to Article 15/I of the same law, a secure electronic signature contains all the legal consequences of a handwritten wet signature. In terms of procedural law discipline, Article 199/I of the Code of Civil Procedure (“CCP”) defines data stored electronically as legal “documents”, however, under Article 205/II of the CCP, it is clearly regulated that electronic data duly issued using a secure electronic signature will have the force of a “conclusive document”. Within the scope of the registration and operation of commercial relations, under the provisions of Article 1526 of the Turkish Commercial Code (“TCC“), electronic transactions and the exercise of the power of representation in relation to company law and negotiable instruments have been brought to a special legal framework. II. Electronic Signature, Secure Electronic Signature and Qualified Electronic Certificate Concepts 1. Electronic Signature (Simple/Standard Electronic Signature) Pursuant to Article 3/b of the ESL, an electronic signature is electronic data that is attached to another electronic data or has a logical connection with electronic data and is used for authentication purposes. This definition is a technology-independent broader concept. A name written at the end of the e-mail, a scanned wet signature image, or simple verified signatures made on foreign platforms fall within this scope; However, such signatures do not offer an absolute legal guarantee of the integrity or identification of the document. 2. Secure Electronic Signature (“SES”) Pursuant to Article 4 of the ESL, a secure electronic signature is an electronic signature that is exclusively connected to the signatory, created with a secure electronic signature creation tool that is only at the disposal of the signatory, provides identification based on a qualified electronic certificate and enables the determination of whether the signed data has been changed later. In terms of its legal consequences, it has the same legal effect as the signature made by hand. 3. Qualified Electronic Certificate (“QES”) An electronic certificate is an electronic record that links the signature verification data and identity information of the signatory. In order for a certificate to be “qualified”, in accordance with Article 9 of the ESL; It is obligatory to include the statement that the certificate is qualified, the identity information of the ECSP and the name of the country where it was established, the identity information of the signatory, signature verification data, validity period, serial number and the secure electronic signature of the ECSP. A secure electronic signature can only be created based on a valid QES obtained from an ECSP authorized by the ICTA. III. Foreign Electronic Signature Platforms (DocuSign, Adobe Sign , etc.) Working Model and Comparison Platforms like DocuSign, Adobe Sign, and HelloSign (Dropbox Sign) operate on a “Software as a Service” (SaaS) based business and revenue model. All of these platforms use similar mechanisms in terms of technical and legal infrastructure:
  • Technical Process: The user uploads the contract to the system and specifies fields such as signature/date. The system sends an access link to the other party and, if necessary, provides verification via SMS OTP (one-time password).
  • Cryptographic Encryption: A unique hash algorithm (Hash) is generated from the current state of the document as soon as the signature is made. If a subsequent change is made to the document, this encryption is broken and tampering can be detected.
  • Audit Trail: At the end of the process, a “Certificate of Completion” is created, which records the signatory’s email address, IP address, timestamp, and device information.
There is no difference in the level of validity between platforms such as DocuSign and Adobe Sign in terms of technical or Turkish law. Both platforms are subject to the ESIGN Act in the US and eIDAS regulations in the EU. However, in Turkish positive law, pursuant to Article 8/I of the ESL, it is obligatory to be an Electronic Certificate Service Provider established in Turkey and to be authorized by notifying the ICTA in order to produce a Qualified Electronic Certificate. In addition, pursuant to Article 18 of the ESR, ECSPs are obliged to create their own signature creation data and certificates within the borders of the Republic of Turkey. Since these foreign platforms  are not in the position of an ECSP that has completed its notification before the ICTA in Turkey and their certificates are not accepted and guaranteed by an authorized ECSP established in Turkey in accordance with Article 14/II of the ESL, they cannot produce a valid QES within the borders of Turkey and therefore a SES that has legal consequences equivalent to a handwritten signature within the meaning of Articles 4 and 5/I of the ESL. Pursuant to Article 14 of the ESL, in order for certificates issued by an ECSP established in a foreign country to be considered as qualified electronic certificates in Turkey, they must have international agreements or be accepted by an ECSP established in Turkey. Since these two conditions are not met for Adobe Sign and DocuSign, signatures produced through these platforms do not qualify as SES in terms of Turkish law and have the status of “simple electronic signature”. IV. The Validity of Contracts Signed Through DocuSign in Terms of Turkish Law 1. Transactions Subject to Freedom of Form (Contracts That Can Use DocuSign) Pursuant to Article 12 of the Turkish Code of Obligations, the validity of contracts does not depend on any form unless otherwise stipulated by law. Contracts that are not subject to any form of validity by law, and therefore can be concluded even orally (e.g., ordinary purchase and sale agreements, service agreements, confidentiality agreements), are considered valid under substantive law, even if they are signed through DocuSign or Adobe Sign. The use of these platforms in cross-border contracts that have foreign elements and are subject to foreign law is sufficient and valid in accordance with international standards. 2. Transactions Subject to the Ordinary Written Form Requirement (Cases Where DocuSign is Not Sufficient) Pursuant to the legislation, the use of a wet signature or secure electronic signature is required for the validity of transactions whose validity is based on “written form”  (TCO Art. 14/II and Art. 15/I). If transactions subject to ordinary written form, such as transfer of receivables, non-compete agreements, and employment contracts, are signed with DocuSign, there is a violation of the form of validity. The legal consequence of this situation is that the contract is null and void due to the lack of form in accordance with Article 12/II of the TCO. 3. Official Form, Special Ceremony and Guarantee Agreements (Transactions That Cannot Be Made Even with a Secure E-signature) Pursuant to Article 5/II of the ESL, there are exceptional transactions that cannot be carried out even with a secure electronic signature:
  • Transactions subject to official form: Transactions such as the sale of real estate, the establishment of a mortgage on real estate or an official will.
  • Transactions subject to special ceremony: Marriage or oral/handwritten will.
  • Guarantee agreements: Personal and guarantees and collateral agreements guarantee contracts such as surety and pledge, except for bank letters of guarantee and surety bonds issued by insurance companies residing in Turkey.
Since, by law, these transactions cannot be made with a secure electronic signature, making them through DocuSign is strictly subject to nullity in terms of substantive law. These transactions must be carried out in the presence of an public officer (notary, land registry officer, etc.) and with a wet signature. V. Evaluation in Terms of Proof Law in Terms of Turkish Courts
  • Secure Electronic Signature (SES): Electronic data duly created with SES are in the form of a “conclusive document” pursuant to Article 205/II of the CCP and constitute conclusive evidence until proven otherwise. In case of denial, the judge examines ex officio whether the conclusive document was created with SES (CCP Art. 205/III).
  • Simple Electronic Signature (DocuSign/Adobe Sign): Documents signed with these platforms do not have the quality of “conclusive document”, which is conclusive evidence. Within the scope of Article 199 of the CCP, they are only “documents” and are considered as “discretionary evidence” in court.
  • Beginning of Proof: If the other party denies the signature, the e-mail records and Audit Trail obtained through DocuSign can be considered as the “beginning of proof” that shows the legal transaction in question as probable in accordance with Article 202 of the CCP. If the document is considered as the beginning of proof, it becomes possible as a rule to hear witnesses in court to prove the legal transaction.
VI. Practical Advice for Implementation and Risk Analysis The risk analysis and measures to be taken regarding the use of foreign e-signature platforms in practice are as follows:
  1. Form Requirement Analysis: When designing contract processes, the legal form requirements to which the contract is subject according to its type should be analyzed in advance. In transactions subject to form,  Qualified Electronic Signature infrastructures offered by domestic ECSPs such as Kamu SM, E-Tuğra, TürkTrust, which have direct e-Government integration or are authorized by ICTA, should be preferred instead of foreign platforms.
  2. Management of Probative Risk: Since contracts established through DocuSign will not constitute conclusive evidence in case of dispute, identity verification security should be increased even in commercial contracts subject to freedom of form. In-platform SMS verification (“OTP”) and two-step verification options must be activated to strengthen the quality of the beginning of proof.
  3. Retention of the Audit Trail: The “Audit Trail” created when the contract is completed; Since it contains the IP address, verification logs and time stamp of the signatory, it should be meticulously stored in the digital archive for the applicable statutory limitation periods in order to prove the document nature and identity in the event of a dispute.
For more information about the electronic signature regime, you can contact our lawyer team.
Frequently Asked Questions (FAQs)
Are contracts signed with electronic signature valid in Turkish Law?
Answer: Yes. Signatures made with a SES in accordance with the ESL have the same legal consequences as a handwritten wet signature in accordance with the Turkish Code of Obligations (Article 14/II and Article 15/I of the TCO) and fully meet the written form requirement.
Do e-signatures made with foreign platforms such as DocuSign or Adobe Sign replace wet signatures in Turkey?
Answer: No. E-signatures made through foreign platforms such as DocuSign, Adobe Sign, or HelloSign generally fall under the category of “Simple/Standard Electronic Signature” in Turkish law. They are not considered equivalent to a wet signature unless they are based on a QES obtained from an authorized ECSP in Turkey within the scope of ESL.
Can documents signed with foreign e-signature platforms be used as evidence in Turkish courts?
Answer: Yes. Pursuant to Article 199/I of the CCP, data stored electronically is a “document”. Although signatures made through foreign platforms (DocuSign, etc.) are not considered “conclusive documents” in the equivalent of wet signatures, they can be presented as discretionary evidence/document showing the declaration of will and commercial relationship between the parties in Turkish courts.
Can company representatives use e-signatures under the Turkish Commercial Code (“TCC”)?
Answer: Yes. Pursuant to the provisions of Article 1526 of the TCC, authorized representatives in transactions related to corporate law and negotiable instruments can exercise legally valid representation and signature powers electronically by using Secure Electronic Signature (SES).
What is the difference between a Secure Electronic Signature (SES) and a Simple Electronic Signature?
Answer: Simple E-Signature (Article 3/b of the ESL): These include a name typed at the end of an e-mail, a scanned wet signature image, or signatures created via foreign platforms; it does not guarantee identity and document integrity. Secure E-Signature (Article 4 of the ESL): It is a signature that is strictly at the disposal of the signatory, provides identification with a Qualified Electronic Certificate (QES), shows whether the data has been changed later, and is exactly equivalent to a wet signature. References Karabel, E. G. (2015). Written form requirement [Thesis, Marmara University]. ProQuest Dissertations & Theses Global. (Publication No. 32712215). Erbayraktar, B. (2011). Legal Liability of the Certificate Provider to Third Parties According to the Electronic Signature and Electronic Signature Law [Master’s/PhD thesis, Istanbul University]. https://nek.istanbul.edu.tr/ekos/TEZ/48075.pdf Information and Communication Technologies Authority. (2026, January 16). Links – Electronic Signature. Information and Communication Technologies Authority. (2017, December 15). Frequently asked questions about e-signature.

The principles of transparency and accountability, which constitute the fundamental principles of the data protection law, are practically shaped through the data controllers’ obligation to inform and the concepts of explicit consent of the data subject. However, in practice, it has been observed that these two (2) independent principles are frequently confused by data controllers or combined under the same approval mechanism.
The Personal Data Protection Board (“Board”), addresses this frequently encountered issue in data protection practices with its principle decision numbered 2026/347, published on 18.02.2026 (“Principle Decision”), This principle decision published in the Official Gazette dated 04.03.2026 and numbered 33203, states that the obligation to inform and explicit consent mechanisms must be strictly separated from each other and foresees critical structural changes for data controllers.

1. Summary of the Decision

In accordance with Article 15, Paragraph 6 of the Personal Data Protection Law with numbered 6698 (“DPL”), the Board is authorized to adopt and publish a principle decision in cases where a violation is determined to be widespread, whether as a result of a complaint or an ex officio investigation.
The Board has commonly identified in practice that data controllers have been merging the texts used to fulfill their statutory obligation to inform with the explicit consent texts, which serve as a legal basis for data processing, under a single document or a single approval button. The Board stated that this practice prevents the public from fully understanding what they are consenting to and leads to the vitiation of intent. In accordance with the authority granted under the DPL, the Board has clearly established in the said Principle Decision that these two concepts are independent processes.
In line with the explanation of the Board, the following basic points are explained;

  • The obligation to inform is a statutory requirement that must be fulfilled prior to any data processing activity, regardless of the legal basis upon which such processing relies. Privacy notices must not request consent from data subjects; instead, they should only obtain feedback acknowledging that the information has been provided.
  • Explicit consent is merely one of the data processing conditions set forth in the Law and possesses its own distinct legal nature. If personal data is being processed based on legal grounds other than explicit consent, no consent should be sought; instead, only the obligation to inform must be fulfilled. Furthermore, data controllers must refrain from using verbatim copies of notices belonging to other institutions and must instead draft bespoke notices tailored to their specific activities.
  • Therefore, in data processing activities conducted based on explicit consent, the information notices and explicit consent texts must be prepared separately; even if they are presented on the same page, their contents and declarations must be strictly decoupled, and the simultaneous execution of both processes through a single approval must be prevented.

2. Legal Assessment and Recommendations

The basis of the Board’s Principle Decision is directly derived from the mandatory provisions of the DPL. Article 10 of the DPL imposes an obligation on the data controller to inform the data subject during the collection of personal data regarding the controller’s identity, the purpose of processing, transfer conditions, the method and legal basis for data collection, and the rights stipulated under Article 11. This process constitutes a unilateral declaration of information.
On the other hand, in subparagraph (a) of the 1st paragraph of Article 3 of the DPL, explicit consent is defined as: “consent regarding a specific subject, based on information and expressed with free will.” Pursuant to Article 5 of the DPL, as a rule, personal data cannot be processed without the explicit consent of the data subject. However, in the event of the existence of one of the conditions listed in the 2nd paragraph of Article 5, such as being clearly prescribed by law, the performance of a contract, or the fulfillment of a legal obligation, it is possible to process data without seeking explicit consent.
The legal basis of the Principle Decision rests exactly at this point, on the systematic interpretation of Articles 3, 5, and 10 of the DPL. If the clarification text and the explicit consent text are linked to a single approval mechanism, “free will,” which is one of the elements of consent, is impaired. The data controller’s fulfillment of the obligation to inform does not mean that the data subject consents to it, and its presentation as a text forced for approval is legally meaningless.
The principles of “Being in compliance with the law and honesty rules” and “Being processed for specific, clear and legitimate purposes” in Article 4 of the DPL necessitate that clarification texts be simple, understandable, and prepared in a way that is far from being ready-made copy-paste texts. Designing the texts separately in line with the Principle Decision can also be evaluated within the scope of “administrative measures” ensuring the compliance of the data processing activity with the law.
If it is mandatory to have both texts on the same page (for example, on the same form on a website) in line with the Principle Decision, the texts should be presented under different headings one below the other, and separate declarations should be obtained from the data subject for both texts. It should be noted with importance that clarification texts are not a contract to be approved. For this reason, only feedback should be received from the data subjects that the clarification text has been read and information has been obtained. Requesting approval or consent from the data subject for the statements in the clarification text should strictly be avoided.
Singular approval boxes such as “I have read the clarification text and I consent to the processing of my data,” which have been encountered on many websites, mobile applications, and physical stores until today, have become contrary to the law. Data controllers must immediately update all digital and physical data collection interfaces, business processes, and legal texts to reflect this distinction.

3. Conclusion and Sanction

With this Principle Decision, the Board has established a definitive rule regarding the separation of the concepts of obligation to inform and explicit consent on physical or digital documents. The Board has categorized the requirement to prepare separate notices for explicit consent and information, as well as the necessity to comply with the aforementioned rules, as part of the ‘administrative and technical measures’ within the scope of Article 12, Paragraph 1 of the DPL.
Consequently, data controllers who fail to comply with this principle decision shall be deemed to have failed in fulfilling their obligations regarding data security; and in accordance with the provisions of Article 18 of the DPL, administrative fines and relevant sanctions shall be imposed upon them.
Data controllers must urgently revise all clarification and explicit consent processes, digital and physical forms in light of this decision in order not to face a legal sanction.

Frequently Asked Questions

  • Can the clarification text and explicit consent text be located on the same page or screen?

Answer: Yes, they can. However, pursuant to the Principle Decision, even if these texts are presented on the same page, the content and declarations must be completely segregated from each other, presented under different headings, and the two processes must not be carried out together with a single approval mechanism.

  • Do I have to get approval from the data subject for clarification texts?

Answer: No, the obligation to inform is a unilateral information process. Pursuant to the Principle Decision, approval should not be obtained for the statements in the clarification text; it should be preferred to receive only a feedback (such as read/understood) regarding the provision of information to the data subject.

  • What path should be followed if our data processing activity is based on a legal condition other than explicit consent, such as the performance of a contract?

Answer: In case personal data is processed based on other legal grounds other than the condition of explicit consent within the scope of DPL Article 5/2 (for example, performance of a contract or legal obligation), explicit consent should not be obtained from the data subject; only the obligation to inform should be fulfilled.

  • Can I use a clarification text carefully prepared by another company by copying it on my own website?

Answer: This would not be a correct use. The Principle Decision states in a clear language that data controllers must prepare the texts they use specifically for their own activities, data processing purposes, and legal reasons, and that texts belonging to other institutions should not be copied and used exactly.

  • What kind of legal sanctions are encountered if explicit consent and clarification texts are not separated duly?

Answer: Not segregating the texts in accordance with the rules is evaluated as not taking the administrative measures within the scope of DPL Article 12, and in case of violation, data controllers may face administrative fines pursuant to DPL Article 18.

For a free initial assessment and consultation:

nazli@npartners.com.tr | info@npartners.com.tr | oyku@npartners.com.tr | alikaan@npartners.com.tr

www.npartners.com.tr | +90 507 604 23 25