Introduction
Cross-border technology transfer agreements in Turkey are essential for international companies, Turkish manufacturers, software developers, research institutions, start-ups, industrial groups, defense and aerospace companies, healthcare technology providers, fintech businesses and investors seeking to commercialize technology across borders. These agreements may involve patent licensing, software licensing, know-how transfer, source code access, technical assistance, R&D cooperation, manufacturing technology, trademark use, industrial designs, data sharing, cloud infrastructure, artificial intelligence tools, engineering documentation or training.
Turkey is a strategically important jurisdiction for technology transfer because it combines industrial production capacity, a large domestic market, a growing technology ecosystem, university-industry cooperation, manufacturing exports and an increasing demand for digital transformation. However, technology transfer is legally complex. A poorly drafted agreement may cause ownership disputes, royalty tax exposure, data protection violations, export control problems, competition law risks, trade secret leakage, software misuse, unauthorized sublicensing and difficult post-termination disputes.
The legal framework is not found in one single “technology transfer law.” Instead, cross-border technology transfer agreements in Turkey are governed by a combination of contract law, intellectual property law, industrial property law, copyright law, unfair competition rules, data protection law, competition law, tax law, export control rules and dispute resolution mechanisms. The Industrial Property Code No. 6769 protects trademarks, geographical indications, designs, patents and utility models, while Law No. 5846 on Intellectual and Artistic Works is the main copyright statute relevant to software and copyrighted materials.
A technology transfer agreement should therefore be treated as a multi-layered legal instrument. It is not merely a license. It is a framework for ownership, permitted use, payment, compliance, confidentiality, data flow, liability, improvements, audit, termination and enforcement.
1. What Is a Cross-Border Technology Transfer Agreement?
A cross-border technology transfer agreement is a contract under which one party transfers, licenses, discloses, permits use of, develops, customizes or commercially exploits technology for or with another party in an international context. The foreign element may arise because the licensor is outside Turkey, the licensee is a Turkish company, the technology is used in Turkey, royalties are paid abroad, data is transferred outside Turkey, software is hosted internationally, or technical assistance is provided across borders.
Technology transfer may include registered rights such as patents, utility models, designs and trademarks. It may also include unregistered assets such as know-how, trade secrets, source code, algorithms, manufacturing processes, formulas, technical drawings, databases, documentation, industrial methods and business processes.
In practice, technology transfer agreements in Turkey appear in many forms:
Patent license agreements.
Software license agreements.
SaaS and cloud service agreements.
Know-how transfer agreements.
Manufacturing technology agreements.
Technical assistance agreements.
R&D cooperation agreements.
University-industry commercialization agreements.
Joint development agreements.
OEM and private label manufacturing agreements.
Source code escrow agreements.
Technology assignment agreements.
Franchise and industrial system transfer agreements.
Each structure creates different legal consequences. A patent license is not the same as a software development agreement. A know-how disclosure agreement is not the same as an assignment of IP ownership. A cloud service contract may involve data protection obligations that do not exist in a pure patent license.
2. Legal Framework under Turkish Law
Technology transfer agreements are generally innominate or mixed contracts under Turkish law. This means they are not regulated as a single named contract type but are formed through the parties’ agreement under the Turkish Code of Obligations. They may combine elements of license, sale, service, lease, mandate, partnership, confidentiality and continuous performance contracts.
For intellectual property, the relevant statutes depend on the transferred asset. Industrial property rights such as patents, utility models, trademarks and designs are protected under Industrial Property Code No. 6769. WIPO notes that Law No. 6769 entered into force in January 2017 and covers industrial property matters including patents, industrial designs, geographical indications and trademarks.
Software and copyrightable materials are generally governed by Law No. 5846 on Intellectual and Artistic Works. WIPO identifies Law No. 5846 as Turkey’s main statute on copyright and related rights.
Technology transfer may also be reviewed under competition law. Law No. 4054 aims to prevent agreements, decisions and practices that prevent, distort or restrict competition in goods and services markets. In addition, the Turkish Competition Authority lists the Block Exemption Communiqué on Technology Transfer Agreements, Communiqué No. 2008/2, among its competition-law communiqués.
Where personal data is transferred with the technology, the Turkish Personal Data Protection Law No. 6698, known as KVKK, becomes relevant. KVKK Article 9 on transfer of personal data abroad was amended by Law No. 7499 in 2024.
3. Licensing versus Assignment
A central drafting issue is whether the technology is being licensed or assigned.
A license gives the licensee permission to use the technology under agreed conditions. Ownership remains with the licensor unless the contract clearly says otherwise. A license may be exclusive, non-exclusive, sole, limited by territory, limited by field of use, limited by product category or limited by duration.
An assignment transfers ownership of the relevant right. Once assigned, the assignee may become the owner of the technology right, subject to statutory formalities and registration requirements where applicable.
The distinction is critical. If a Turkish manufacturer receives a “license” to use foreign patented technology, it does not own the patent. If a foreign software company “licenses” a platform to a Turkish client, the client generally receives use rights, not ownership of source code. If the parties intend transfer of ownership, the agreement should expressly provide assignment language, transfer scope, registration obligations, consideration and post-transfer rights.
Ambiguous wording such as “the technology is provided to the Turkish party” is dangerous. The contract should state whether rights are licensed, assigned, sublicensed, disclosed for evaluation, used only internally, used for manufacturing, used for resale or used for integration into another product.
4. Patent and Utility Model Licensing
Patent and utility model licensing is common in manufacturing, pharmaceuticals, medical devices, machinery, chemicals, electronics, automotive parts, energy technologies and industrial processes. A patent license allows a Turkish company to use protected technology, produce patented goods, sell licensed products or incorporate patented components.
A patent license should define:
Licensed patents and application numbers.
Territory.
Field of use.
Exclusivity.
Right to manufacture.
Right to sell or export.
Sublicensing.
Improvements.
Patent maintenance responsibility.
Infringement enforcement.
Royalty structure.
Quality control.
Termination effect.
If the licensee will export products made with licensed technology, the contract should clarify whether export sales are permitted and whether royalties apply to export revenue. If the licensee will supply products to affiliates, transfer pricing and royalty calculation should be considered.
Patent license registration may also be relevant for third-party effectiveness and recordkeeping. The parties should review whether the license should be recorded before the Turkish Patent and Trademark Office depending on the right, commercial structure and enforcement strategy.
5. Software Licensing and Source Code Access
Software licensing is one of the most important forms of technology transfer. It may involve on-premise software, SaaS platforms, API access, embedded software, firmware, source code, object code, maintenance, updates, cybersecurity obligations and cloud infrastructure.
Software rights in Turkey are generally analyzed under copyright law. WIPO identifies Law No. 5846 as Turkey’s copyright statute, and copyright protection covers works such as computer programs in the general copyright framework.
A software license should define:
Permitted users.
Permitted devices.
Territory.
Hosting location.
Source code or object code access.
Reverse engineering restrictions.
API usage.
Data ownership.
Updates and patches.
Service levels.
Cybersecurity obligations.
Audit rights.
Open-source components.
Maintenance fees.
Termination and data export.
Foreign licensors should be careful when granting broad “use” rights to Turkish customers. If the customer needs only access to a platform, the license should not accidentally grant modification, redistribution, sublicensing, reverse engineering or source code rights.
For Turkish licensees, the key concern is business continuity. If critical software is used in manufacturing, banking, healthcare, logistics or e-commerce, the licensee should negotiate service levels, data portability, escrow, transition assistance and termination support.
6. Know-How and Trade Secret Transfer
Many technology transfer agreements do not involve registered rights. Instead, they involve know-how. Know-how may include formulas, manufacturing methods, engineering practices, testing protocols, quality standards, algorithms, technical drawings, recipes, industrial methods, process parameters, training materials or troubleshooting knowledge.
Know-how is valuable because it is secret. Once disclosed without control, it may lose its commercial value. Therefore, know-how transfer agreements must include strong confidentiality, limited-use obligations, access restrictions, employee confidentiality duties, non-circumvention provisions and post-termination return or destruction duties.
Turkish Commercial Code unfair competition rules protect production and business secrets. Article 55 treats unlawful disclosure or exploitation of production and business secrets as conduct contrary to good faith. Since the direct citation reference is not available from the latest search, the safer legal basis is that the Turkish Commercial Code contains unfair competition provisions in Articles 54–63 and WIPO confirms that Law No. 6102 includes unfair competition rules.
For know-how transfer, the contract should describe the know-how in an annex without over-disclosing it in a public or registrable document. Technical information should be shared through controlled channels, preferably with document tracking, watermarking and access logs.
7. Confidentiality and NDA Structure
A technology transfer agreement should include a detailed confidentiality regime, even if the parties have already signed a separate NDA. The confidentiality clause should cover technical information, business information, software architecture, source code, pricing, manuals, designs, drawings, customer data, product roadmaps, test results, prototypes and derivative materials.
The clause should define:
What is confidential.
Who may access it.
Permitted use.
Prohibited use.
Permitted disclosures.
Security standards.
Employee and consultant access.
Return or destruction.
Survival period.
Trade secret survival.
Injunctive relief.
A fixed confidentiality period may be insufficient for trade secrets. The agreement may provide that ordinary confidential information is protected for five years, but trade secrets remain protected as long as they are not lawfully public.
8. Improvements and Derivative Technology
One of the most disputed issues in technology transfer agreements is ownership of improvements. A Turkish licensee may improve the licensed technology during local adaptation. A foreign licensor may incorporate feedback into its global platform. Engineers from both sides may jointly develop a new version.
The agreement should answer:
Who owns improvements made by the licensee?
Who owns improvements made by the licensor?
Who owns jointly developed technology?
Does the licensor receive a grant-back license?
Does the licensee receive rights to use global upgrades?
Are improvements royalty-bearing?
Can improvements be patented?
Who pays patent filing costs?
Can either party commercialize improvements outside Turkey?
Without clear drafting, the parties may later dispute whether a new process, module, design or algorithm belongs to the licensor, licensee or both.
9. Competition Law and Technology Transfer
Technology transfer agreements may promote innovation by spreading technology, reducing duplicated R&D costs and enabling new products. However, they may also restrict competition if they include market allocation, price fixing, output restrictions, customer restrictions, exclusive grant-backs, no-challenge clauses or excessive non-compete obligations.
Law No. 4054 prohibits agreements that prevent, distort or restrict competition. For technology transfer agreements, Communiqué No. 2008/2 is the key block exemption framework listed by the Turkish Competition Authority.
Technology transfer competition analysis usually considers whether the parties are competitors, their market shares, substitutable technologies, substitutable products, exclusivity, duration, territorial restrictions and whether hardcore restrictions exist. Commentary on Turkish technology transfer competition rules notes that Communiqué No. 2008/2 regulates compatibility of IP license agreements with competition law and provides block exemption where conditions are satisfied.
The agreement should be reviewed carefully if it includes:
Exclusive licensing.
Territorial restrictions.
Customer restrictions.
Minimum resale prices.
Output restrictions.
Non-compete obligations.
No-challenge clauses.
Exclusive grant-back obligations.
Restrictions on R&D.
Restrictions after patent expiry.
If market shares exceed applicable thresholds or the agreement contains sensitive restrictions, individual exemption analysis may be necessary.
10. Data Protection and Cross-Border Transfers
Technology transfer often involves data. This may include employee data, customer data, user data, telemetry, machine data, health data, device logs, CRM data, training datasets, cloud backups, support tickets and analytics.
If personal data is involved, KVKK applies. Article 9 on cross-border transfer was amended in 2024, and the official KVKK text now sets out the revised legal framework for transferring personal data abroad.
This is especially important where:
A Turkish customer uses foreign-hosted SaaS.
Support teams outside Turkey access personal data.
A foreign licensor receives user logs.
Cloud servers are located outside Turkey.
AI training data includes personal data.
A Turkish licensee transfers employee data to a foreign parent.
The agreement should include a data protection annex regulating controller/processor roles, processing purposes, security measures, breach notification, cross-border transfer mechanism, retention, deletion, audit and data subject requests.
A technology license is not enough to legalize personal data flows. Data processing must be separately structured under KVKK.
11. Cybersecurity and Technical Compliance
Technology transfer agreements should address cybersecurity. If the technology is software, cloud-based, connected to industrial systems, embedded in medical devices, used in finance, or integrated into critical operations, cybersecurity obligations become essential.
The agreement should regulate:
Security standards.
Access controls.
Encryption.
Vulnerability management.
Patch obligations.
Incident notification.
Penetration testing.
Backup and disaster recovery.
Business continuity.
Audit rights.
Data segregation.
Subprocessor approval.
Cybersecurity failures may cause data breaches, production shutdowns, liability to customers, regulatory exposure and reputational damage. In international technology transactions, cybersecurity should be treated as a contractual obligation, not merely an IT issue.
12. Royalty Payments and Turkish Tax Issues
Royalty taxation is a major issue in cross-border technology transfer agreements. If a Turkish company pays royalties to a foreign licensor, Turkish withholding tax may apply. PwC’s Turkey corporate tax summary states that royalty payments to non-residents are generally subject to 20% withholding tax, which may be reduced under double tax treaty provisions, commonly to 10% depending on the treaty.
The contract should therefore state whether royalties are gross or net of withholding tax. It should also regulate tax residency certificates, treaty benefit documentation, gross-up clauses, VAT reverse charge where applicable, invoice requirements and audit rights.
Tax characterization matters. A payment described as “service fee” may be re-characterized as a royalty if it economically relates to IP use. KPMG commentary notes that embedded IP royalties in payments for goods or services may raise Turkish withholding tax issues.
Before signing, parties should tax-review:
Royalty rate.
Payment currency.
Withholding tax.
Double tax treaty relief.
VAT or reverse charge VAT.
Transfer pricing.
Stamp tax.
Permanent establishment risk.
Embedded royalty risk.
Failure to address tax may change the economics of the deal.
13. Transfer Pricing and Intra-Group Technology Licensing
Many cross-border technology transfer agreements occur within multinational groups. A foreign parent licenses software, trademarks, patents or know-how to a Turkish subsidiary. These arrangements must be commercially justified and priced at arm’s length.
Transfer pricing documentation should support the royalty rate, benefit received, comparable licenses, cost allocation, DEMPE functions, ownership of intangibles and local exploitation rights. If the Turkish subsidiary pays excessive royalties, tax authorities may challenge deductibility or re-characterize the arrangement.
For intra-group agreements, legal drafting should match tax reality. If the Turkish subsidiary only receives limited software access, the agreement should not describe a broad transfer of know-how. If the subsidiary performs R&D, the agreement should state who owns resulting IP and how the subsidiary is compensated.
14. Export Controls, Sanctions and Dual-Use Technology
Technology transfer may trigger export control and sanctions issues. Export controls do not apply only to physical goods. They may also cover software, technical assistance, encryption technology, engineering data, defense-related know-how and dual-use technology.
The Turkish Ministry of Trade states that strategic goods are subject to permissions by different authorities: military items require Ministry of Defense permission, dual-use items require Ministry of Economy/Trade permission, and nuclear or nuclear dual-use items require the relevant atomic energy authority permission.
This matters for cross-border technology transfer where a Turkish company receives or exports controlled technology. It also matters where foreign-origin technology subject to U.S., EU, UK or other export controls is transferred to Turkey or re-exported from Turkey.
The agreement should include:
Export control compliance warranties.
Sanctions screening.
End-use and end-user restrictions.
No military use clause, if relevant.
No re-export without authorization.
Controlled technology handling rules.
Audit and termination rights.
Notification of government inquiries.
Technology transfer in defense, aerospace, encryption, advanced electronics, machine tools, AI, cybersecurity, nuclear, chemicals and biotechnology requires special caution.
15. Field-of-Use and Territory Restrictions
Technology licenses often limit use by field and territory. For example, a patent may be licensed only for medical devices, not industrial products. Software may be licensed only for internal use in Turkey. Manufacturing know-how may be licensed only for products sold in the Middle East.
Field-of-use restrictions can be commercially useful, but they should be checked under competition law where they affect market access. The agreement should define the permitted field precisely. Vague restrictions such as “industrial use” or “commercial use” may create disputes.
Territory should also be clear. If the Turkish licensee can manufacture in Turkey and export worldwide, royalties and compliance obligations should reflect that. If exports are prohibited or limited, the restriction should be enforceable and competition-law compliant.
16. Sublicensing and Affiliates
Sublicensing is often disputed. A Turkish licensee may want affiliates, subcontractors, distributors, manufacturers or customers to use the technology. A foreign licensor may want strict control.
The agreement should state:
Whether sublicensing is allowed.
Whether prior written consent is required.
Whether affiliates are covered.
Whether subcontractors may access technology.
Whether cloud users count as sublicensees.
Whether distributors may use trademarks or software.
Whether sublicenses survive termination.
The licensor should require the licensee to remain liable for sublicensees and ensure they comply with confidentiality, export control, IP and data protection obligations.
17. Technical Assistance, Training and Documentation
Technology transfer often requires more than documents. The licensor may provide training, installation, commissioning, testing, engineering support, troubleshooting, updates and on-site assistance.
The agreement should define:
Training scope.
Language.
Location.
Travel costs.
Training materials.
Number of trainees.
Technical support hours.
Service levels.
Acceptance tests.
Documentation updates.
Remote access.
On-site safety rules.
If technical assistance is provided in Turkey by foreign personnel, work permit, tax presence and permanent establishment issues may arise depending on duration and structure.
18. Warranties and Performance Commitments
Technology agreements often fail because expectations are unclear. The licensee expects guaranteed results; the licensor only intended to provide technology “as is.” The contract should define warranties carefully.
Possible warranties include:
Ownership or right to license.
Non-infringement.
No known third-party claims.
Functionality.
Compliance with documentation.
Security standards.
No malicious code.
Regulatory compliance.
Performance metrics.
Compatibility.
For early-stage technology, the licensor may limit warranties and state that the licensee assumes implementation risk. For critical industrial technology, the licensee may require performance testing, acceptance criteria, warranty remedies and indemnity.
19. IP Infringement and Indemnity
If the licensed technology infringes third-party rights, the licensee may face lawsuits, injunctions, business interruption and damages. Therefore, IP indemnity is critical.
A well-drafted indemnity clause should define:
Covered claims.
Defense control.
Notice requirements.
Settlement approval.
Excluded claims.
Remedies for infringement.
Replacement or modification rights.
Refund or termination.
Liability cap.
The licensor may exclude liability where infringement results from unauthorized modification, combination with non-approved products, use outside the license scope or failure to install updates.
20. Audit Rights and Compliance Monitoring
Technology licenses often require audit rights. The licensor may need to verify user numbers, royalty calculation, manufacturing output, sublicensing, export restrictions, cybersecurity controls or confidentiality compliance.
Audit clauses should be balanced. They should define frequency, notice, auditor independence, confidentiality, scope, cost allocation and consequences of underreporting.
For software, audits may involve license keys, access logs, server records, user accounts and deployment counts. For manufacturing technology, audits may involve production records, sales data and inventory. For cross-border arrangements, audit rights should also respect data protection and trade secret concerns.
21. Termination and Post-Termination Obligations
Termination is a critical stage. The agreement should define termination for cause, termination for convenience, termination for insolvency, termination for export control breach, termination for non-payment, termination for confidentiality breach and termination for IP misuse.
Post-termination obligations should include:
Stop using technology.
Stop manufacturing licensed products.
Return or destroy confidential information.
Delete software and source code.
Return documentation.
Terminate sublicenses.
Transfer data.
Pay outstanding royalties.
Sell-off period, if allowed.
Continue confidentiality.
Continue audit rights for past royalties.
If the licensee has built a business around the technology, termination may be commercially disruptive. Therefore, transition rights, cure periods and escrow may be important.
22. Source Code Escrow and Business Continuity
For critical software, source code escrow may protect the Turkish licensee. The source code is deposited with an escrow agent and released only if defined events occur, such as licensor insolvency, failure to maintain software or discontinued support.
The escrow agreement should define:
Deposited materials.
Update frequency.
Release conditions.
Verification rights.
Permitted use after release.
Confidentiality.
Dispute procedure.
Escrow fees.
Source code escrow is not necessary for every SaaS deal, but it may be valuable for banks, factories, healthcare systems, logistics operators and critical infrastructure users.
23. Dispute Resolution
Cross-border technology transfer disputes may involve royalty claims, IP ownership, confidentiality breach, software failure, data breach, unauthorized sublicensing, export control breach, infringement indemnity or termination. Arbitration is often preferred for international technology contracts because it offers confidentiality, technical expertise and enforceability.
However, Turkish courts may be necessary for interim injunctions, evidence preservation, IP infringement actions, unfair competition claims, customs measures or urgent misuse of trade secrets. The dispute resolution clause should preserve the right to seek interim measures from competent courts.
The agreement should specify:
Governing law.
Arbitration institution or court.
Seat of arbitration.
Language.
Number of arbitrators.
Confidentiality of proceedings.
Interim measures.
Expert determination for technical disputes.
For Turkey-related contracts, ISTAC arbitration may be considered, but ICC, LCIA, Swiss Arbitration Centre or ad hoc arbitration may also be appropriate depending on the parties and transaction value.
24. Practical Drafting Checklist
A cross-border technology transfer agreement involving Turkey should include:
Clear definition of technology.
License or assignment structure.
Licensed rights.
Territory and field of use.
Exclusivity.
Sublicensing.
Ownership of improvements.
Confidentiality and trade secrets.
Software access rules.
Source code rights.
Data protection and KVKK clause.
Cybersecurity obligations.
Export control and sanctions clause.
Royalty structure.
Tax and withholding provisions.
Transfer pricing support.
Technical assistance scope.
Warranties and disclaimers.
IP indemnity.
Audit rights.
Termination and post-termination obligations.
Dispute resolution.
Interim measures.
Language priority.
This checklist should be adapted to the technology type. A patent license, SaaS contract, AI data agreement and manufacturing know-how transfer do not carry the same risks.
Conclusion
Cross-border technology transfer agreements in Turkey require careful legal structuring because they combine licensing, intellectual property, software, know-how, trade secrets, data protection, competition law, tax, export controls and dispute resolution. The legal framework is fragmented: Industrial Property Code No. 6769 protects patents, trademarks, designs and utility models; Law No. 5846 governs copyright and software-related rights; KVKK regulates personal data; Law No. 4054 and Communiqué No. 2008/2 address competition law issues in technology transfer; and tax rules affect royalties and service payments.
For foreign licensors, the main risks are unauthorized use, sublicensing, disclosure of know-how, non-payment of royalties, tax gross-up disputes, reverse engineering, competition law invalidity and difficulty enforcing termination. For Turkish licensees, the main risks are weak usage rights, lack of source code access, poor performance warranties, sudden termination, data transfer non-compliance, export control restrictions and dependency on foreign support.
The best protection is precise drafting. The agreement should define the technology, scope of rights, ownership, improvements, permitted use, confidentiality, data flows, royalty tax treatment, compliance obligations, audit rights, termination effects and dispute resolution. In technology transfer, ambiguity is expensive. A clear agreement protects both innovation and commercial value.
Frequently Asked Questions
What laws govern technology transfer agreements in Turkey?
Technology transfer agreements in Turkey are governed by contract law, Industrial Property Code No. 6769, Law No. 5846 on Intellectual and Artistic Works, Turkish Commercial Code unfair competition rules, KVKK, Law No. 4054 on competition, tax law and export control rules depending on the technology and transaction.
Are technology transfer agreements specifically regulated as named contracts?
No. They are generally treated as mixed or innominate contracts under Turkish law. Their legal effect depends on the contract wording and the type of technology transferred.
Can patents and industrial property rights be licensed in Turkey?
Yes. Patents, utility models, trademarks and designs are protected under Industrial Property Code No. 6769 and may be licensed under proper contractual structures.
Is software protected under Turkish law?
Yes. Software is generally protected under Turkey’s copyright framework, Law No. 5846 on Intellectual and Artistic Works.
Does KVKK apply to technology transfer agreements?
Yes, if personal data is processed or transferred. KVKK Article 9, amended in 2024, governs cross-border personal data transfers.
Do technology transfer agreements raise competition law issues?
Yes. Technology transfer agreements may be reviewed under Law No. 4054 and the Block Exemption Communiqué on Technology Transfer Agreements No. 2008/2.
What tax applies to royalties paid from Turkey to foreign licensors?
Royalty payments to non-residents are generally subject to 20% Turkish withholding tax, which may be reduced under an applicable double tax treaty.
Can technology transfer trigger export control issues?
Yes. Strategic goods, dual-use items, military items and nuclear dual-use items may require permissions from relevant Turkish authorities.
What is the biggest risk in know-how transfer?
The biggest risk is uncontrolled disclosure. Know-how should be protected through confidentiality, limited use, access controls, employee obligations, audit rights and post-termination destruction duties.
What should every technology transfer agreement include?
It should include clear license scope, ownership rules, confidentiality, improvements, data protection, export control, royalties, tax allocation, warranties, IP indemnity, audit rights, termination effects and dispute resolution.
Yanıt yok