Overview Of The European Union Artificial Intelligence Act And Effects On Turkish Companies

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 rapid expansion of artificial intelligence (“AI”) across multiple sectors has inevitably raised questions regarding its ethical and safety dimensions. The first concrete regulatory step in this field was taken by the European Union (“EU”) through the Artificial Intelligence Act (“the Act”)[1], which was adopted by the European Parliament on 13 March 2024, approved by the Council on 21 May 2024, published in the Official Journal on 12 July 2024, and entered into force on 1 August 2024. The Act constitutes the most comprehensive legal framework on AI adopted to date. This memorandum aims to examine the scope of the Act, its risk classifications, obligations, and implementation timeline in detail.

  1. What is the Artificial Intelligence Act?

The regulation adopted by the European Parliament in March 2024 and effective as of 1 August 2024 seeks to regulate the placing on the market and use of AI systems, ensuring that such technologies are trustworthy, transparent, and respectful of fundamental rights. It is considered the most comprehensive legal framework on AI introduced so far.

The Act defines an AI system as follows:
“ a machine-based system that is designed to operate with varying levels of autonomy and that may exhibit adaptiveness after deployment, and that, for explicit or implicit objectives, infers, from the input it receives, how to generate outputs such as predictions, content, recommendations, or decisions that can influence physical or virtual environments”.The regulation is largely based on the Ethics Guidelines for Trustworthy AI [2] published by the European Commission in 2019. The Guidelines emphasize that trustworthy AI must comply with existing law, adhere to ethical principles, and be robust from both a technical and social perspective. They also set out seven key requirements for the development of AI systems:

  • Human agency and oversight: AI systems should empower human decision-making and allow for meaningful human oversight.
  • Technical robustness and safety: Systems must be resilient and secure.
  • Privacy and data governance: Protection of personal data must be ensured.
  • Transparency: Operations of AI systems should be explainable and understandable.
  • Diversity, non-discrimination, and fairness: AI should be inclusive and accessible to all.
  • Societal and environmental well-being: AI should benefit society as a whole.
  • Accountability: Clear mechanisms must ensure responsibility for outcomes.
  1. To Whom and Under What Conditions Does the Act Apply?

Article 2 of the Act identifies six categories of actors subject to obligations: providers, importers, distributors, product manufacturers, authorised representatives, and deployers.

  • Providers: Natural or legal persons who develop an AI system or a general-purpose AI model, or place it on the market under their own name or trademark.
  • Importers: Entities placing on the EU market an AI system originating from a third country.
  • Distributors: Entities making AI systems available within the EU market.
  • Product Manufacturers: Entities manufacturing physical products with embedded AI systems.
  • Authorised Representatives: Persons mandated by providers established outside the EU to represent them within the Union.
  • Deployers: Natural or legal persons who use an AI system in the course of their activities.

It should be noted that, as stated in Article 2 of the Regulation, the obligations apply regardless of whether the actors listed therein are established within the EU. The Regulation will also apply in cases where an AI system is placed on the market or used within the EU. This demonstrates the broad and extraterritorial scope of the Regulation, showing that its impact extends beyond the borders of the EU and has a truly global effect.

In the context of Turkish companies, this means that entities established in Turkey which place AI systems on the EU market or use them within the EU must also ensure compliance with the Regulation. Adapting to these requirements is of great importance for Turkish companies engaged in commercial or technological activities connected to the EU.

  1. The Risk-Based Approach

The Act introduces obligations based on a risk-based classification of AI systems into four categories:

  • Unacceptable risk: Systems deemed to pose intolerable harm, strictly prohibited.
  • High risk: Systems with significant potential to cause harm in sensitive areas, subject to extensive requirements.
  • Limited risk: Systems with specific transparency obligations, e.g., informing users they are interacting with AI.
  • Minimal risk: Systems with negligible or no risk, not subject to regulatory obligations.

Unacceptable risk is regulated under Article 5 of the Act, entitled “Prohibited AI Practices.” AI systems that fall within the category of unacceptable risk have been prohibited as of 2 February 2025. Among the systems banned under this provision are those that impair individuals’ decision-making processes and cause harm through manipulative techniques. In addition, AI systems that collect facial images to create facial recognition databases, as well as AI systems that evaluate or classify individuals or groups based on social behavior or personal characteristics and result in adverse treatment against such persons through social scoring, have also been deemed to pose an unacceptable level of risk.

High-risk AI systems, on the other hand, include remote biometric identification, biometric categorisation and emotion recognition systems; AI systems used in the management of critical digital infrastructure such as road traffic, energy networks, or water distribution; AI systems employed in the fields of education and employment for candidate selection, student admission, or performance evaluation; and AI systems determining access to public benefits, calculating credit scores, or prioritising emergency calls. The high-risk category is the group subject to the most obligations under the Act. Providers of AI systems falling within this risk group must comply with the obligations set out in Article 16 of the Act. These obligations include, among others: implementing risk management, data governance, and transparency requirements; indicating provider identification details on the system; maintaining records; establishing a quality management system; issuing an EU declaration of conformity; and affixing the CE marking to the system.

  1. General-Purpose AI Models (GPAI)

Title V of the Act specifically regulates General-Purpose AI Models (“GPAI”). According to Article 3(63), a GPAI model means:

“An AI model, including where such a model is trained with large amounts of data using self-supervision at scale, that displays significant generality and is capable of competently performing a wide range of distinct tasks, regardless of the way it is placed on the market, and that can be integrated into a variety of downstream systems or applications, except AI models used solely for research, development, or prototyping prior to being placed on the market.”

The Regulation allocates a separate section to GPAI models and imposes additional obligations on AI systems that make use of such models, beyond the general provisions applicable to other AI systems. The Regulation categorizes GPAI models into two distinct risk groups: non-systemic risk and systemic risk.

For both risk groups, compliance with copyright requirements and transparency constitute common obligations. However, for GPAI systems posing systemic risks, such as ChatGPT, Article 55 of the Regulation introduces further obligations. These include model testing, assessment and mitigation of systemic risks, reporting of serious incidents, and ensuring adequate cybersecurity protection. These additional obligations entered into force as of 2 August 2025.

  1. Sanctions

As of 2 June 2025, administrative fines for non-compliance with the obligations set out in the Act have also entered into effect. The applicable fines are as follows:

  • Up to EUR 35 million or 7% of annual global turnover (whichever is higher) for violations of Article 5 (prohibited practices).
  • Up to EUR 15 million or 3% of annual global turnover (whichever is higher) for non-compliance with obligations for high-risk systems.
  • Up to EUR 7.5 million or 1% of annual global turnover (whichever is higher) for providing incorrect, incomplete, or misleading information to authorities.
  1. Expected Developments

As we have stated, the Act entered into force on 1 August 2024. However, since a phased implementation has been adopted, the Act has not yet entered fully into effect. The provisions on prohibited practices entered into force on 2 February 2025, while the rules concerning general-purpose AI models and sanctions became applicable on 2 August 2025. The next development is expected, according to the published timeline[3], on 2 February 2026. Namely, by that date, the European Commission is required to publish guidelines explaining the practical application of Article 6 on the classification of high-risk systems. The timeline further provides that the remaining provisions of the Act (except Article 6(1)) will apply as of 2 August 2026. Through this phased timeline, a two-year transition period has effectively been granted for compliance.

Conclusion

The Artificial Intelligence Act adopted by the European Union stands as a pioneering regulation that shapes the direction of AI governance not only within Europe but also on a global scale, owing to its comprehensive, risk-based, and systematic structure. As stated earlier, the Regulation applies not only to companies operating within the borders of the European Union but also to entities from third countries that place products or services on the EU market or use AI systems within the EU. Therefore, it is evident that Turkish companies maintaining commercial or technological ties with the European Union will also be subject to the obligations set out under the Regulation.

In Turkey, the “Artificial Intelligence Law Draft” was introduced to the public on June 25, 2024; however, a legally binding regulation has not yet entered into force. Accordingly, there is currently no domestic legislation requiring local compliance. At this stage, only Turkish companies operating in the EU market or maintaining EU-based business partnerships are directly subject to compliance obligations. Although this process may present certain technical, legal, and financial challenges for Turkish companies, it is anticipated that those aligning with the Regulation will gain a significant advantage in terms of reliability, transparency, and competitiveness in the EU market.

The Regulation aims to ensure that AI systems are developed in a trustworthy, transparent, and human-rights-respecting manner, while safeguarding individuals and society from potential technological risks. By addressing ethical, legal, and technical standards within a holistic framework, it adopts a multi-layered approach that emphasizes not only technical conformity but also social responsibility and respect for fundamental rights. For Turkish companies, adopting this approach and aligning their strategies with the standards introduced by the Regulation will be crucial for both sustaining their presence in the EU market and preparing for potential national regulations expected to come into force in Turkey in the near future.

In conclusion, the EU Artificial Intelligence Act serves as more than just a regional regulatory instrument it provides a guiding reference for public authorities, the private sector, and academia in Turkey. It is expected to shed light on the national legislative efforts currently at the draft stage and contribute to the establishment of a trustworthy, ethical, and human-centric AI ecosystem in Turkey.

References

  1. The AI Act Explorer. AI Act Explorer. Accessed 30 September 2025,
    https://artificialintelligenceact.eu/ai-act-explorer/
  2. European Commission. (8 April 2019). Ethics Guidelines for Trustworthy AI. Accessed 30 September 2025,
    https://digital-strategy.ec.europa.eu/en/library/ethics-guidelines-trustworthy-ai
  3. Software Improvement Group. (August 2025). A Comprehensive EU AI Act Summary. Accessed 30 September 2025,
    https://www.softwareimprovementgroup.com/eu-ai-act-summary/#elementor-toc__heading-anchor-4
  4. Bird & Bird LLP. (December 2024). European Union Artificial Intelligence Act – A Practical Guide. Accessed 30 September 2025,

    https://www.twobirds.com/-/media/new-website-content/pdfs/capabilities/artificial-intelligence/european-union-artificial-intelligence-act-guide.pdf