Executive Summary
International software vendors, enterprise SaaS providers, AI platform operators, and foreign technology investors transacting in Türkiye must navigate a distinct civil-law regime governing code ownership, licensing formalities, liability caps, cross-border cloud hosting, and tax withholding. Under Turkish law, computer programs are protected primarily as literary and scientific works under Law No. 5846 on Intellectual and Artistic Works (FSEK), while cloud-based Software-as-a-Service (SaaS) subscriptions are treated as sui generis mixed contracts under the Turkish Code of Obligations No. 6098 (TCO). Critically, standard US or UK enterprise templates frequently fail in Turkish courts on three fronts: generic IP assignment clauses lacking statutory right-by-right itemization under FSEK Article 52, broad limitation-of-liability caps invalidated by TCO Article 115 for gross negligence, and unaddressed royalty vs. business-profit withholding tax classifications under Turkish tax treaties.
I. Legal Protection of Software, Algorithms & Databases in Turkey
Under Article 2(1)(1) of Law No. 5846 on Intellectual and Artistic Works (FSEK), "computer programs expressed in any form together with their preparatory designs, provided that the latter result in a computer program at the next stage" are protected as scientific and literary works automatically from the moment of creation, without any mandatory registration requirement (although optional time-stamped registration before the Ministry of Culture and Tourism or notary/TÜBİTAK timestamping provides strong evidentiary presumption of authorship).
Law No. 5846 (FSEK), Article 2(1)(1):
"Ideas and principles underlying any element of a computer program, including those underlying its interfaces, are not deemed works. Computer programs expressed in any form and their preparatory design materials leading to a program are protected as literary and scientific works."
Foreign technology companies should understand four structural boundaries of Turkish IP protection for software and AI assets:
- Source Code vs. Algorithms & Interfaces: FSEK protects the literal expression of source code, object code, compiler outputs, and detailed architectural flowcharts. Underlying mathematical algorithms, business logic, API functional specifications, and programming languages per se are excluded from copyright—though Graphical User Interfaces (GUIs) may qualify for separate protection as fine art works (FSEK Art. 4) or registered industrial designs under Industrial Property Code No. 6769 (SMK).
- Patentability of Computer-Implemented Inventions (SMK Art. 82/2-c): Mirroring European Patent Office (EPO) doctrine, SMK Article 82 excludes "computer programs as such" and "business methods" from patentability. However, a software-driven invention is patentable before the Turkish Patent and Trademark Office (TÜRKPATENT) if it produces a "further technical effect" (ileri teknik etki) beyond normal physical interactions between software and hardware—such as optimizing industrial robotics, medical imaging signal processing, telecom packet routing, or cryptographic hardware security.
- Dual Database Protection (FSEK Art. 6 & Additional Art. 8): Databases exhibiting originality in the selection and arrangement of data enjoy full copyright protection under FSEK Article 6(1)(11). Independently, non-original databases reflecting a substantial qualitative or quantitative investment in obtaining, verifying, or presenting contents enjoy a 15-year sui generis database producer right under Additional Article 8 against unauthorized extraction or scraping.
- Trade Secret Protection (TCC Arts. 54–63): Proprietary AI model weights, training datasets, pricing algorithms, and undeployed source code repositories are protected against misappropriation through the unfair competition and criminal/civil remedies of the Turkish Commercial Code No. 6102.
II. Mandatory IP Assignment & Licensing Formalities (FSEK Arts. 18, 48 & 52)
Whether licensing enterprise software into Türkiye, commissioning bespoke software development from a Turkish agency, or conducting due diligence for a Turkish tech M&A acquisition, compliance with FSEK's strict formality rules is non-negotiable:
- Written Form & Explicit Enumeration of Economic Rights (FSEK Art. 52): Under FSEK Article 52, all contracts and licenses concerning economic rights (mali haklar) must be in written form (wet-ink signature or Law No. 5070 qualified electronic signature; click-wrap check-boxes suffice only for non-exclusive end-user right-of-use permissions, never for IP assignments or exclusive licenses!) and must separately specify by name each economic right being transferred or licensed:
- Right of Adaptation / Modification & Derivative Works (İşleme Hakkı — Art. 21);
- Right of Reproduction (Çoğaltma Hakkı — Art. 22);
- Right of Distribution, Rental & Resale (Yayma Hakkı — Art. 23);
- Right of Performance (Temsil Hakkı — Art. 24); and
- Right of Communication to the Public via Digital/Cloud Means (Umuma İletim Hakkı — Art. 25), alongside explicit duration, territory ("worldwide"), media, and sub-licensing/transferability authority (Art. 49).
- Employees vs. Independent Contractors (FSEK Art. 18): Under FSEK Article 18(2), the right to exercise economic rights over software created by formal payroll employees in the performance of their employment duties vests statutorily in the employer (further reinforced via employment clauses—see our Turkish Employment & Tech Talent Guide). Conversely, independent contractors, B2B dev shops, and company founders prior to incorporation retain 100% statutory authorship and ownership unless a FSEK Art. 52 compliant written assignment is executed!
- Future Works Trap (FSEK Art. 48/3) & Moral Rights (Arts. 14–17): Dispositions over not-yet-written code modules operate only as binding promises to assign; thus, agile sprint contracts must require signed Post-Completion IP Assignment Protocols upon final acceptance. Moreover, moral rights (paternity, disclosure, integrity) are inalienable under Turkish law; instead of unenforceable "moral rights waivers," contracts grant the client irrevocable authority to exercise moral rights, determine publication timing, and modify code without author attribution.
- Mandatory Interoperability / Decompilation Right (FSEK Art. 38): Mirroring the EU Software Directive, FSEK Article 38 renders void any contractual ban preventing a lawful software licensee from making a backup copy, observing/testing program behavior during permitted loading, or performing strictly necessary decompilation (reverse engineering) solely to achieve interoperability with an independently created program.
III. Structuring Enterprise SaaS, Cloud Subscriptions & AI Clauses
Unlike traditional on-premise perpetual or term software licenses—where object code is installed on the customer's servers and thus triggers copyright reproduction rights under FSEK—pure Software-as-a-Service (SaaS) and API-based AI platforms do not deliver a copy of the underlying software to the customer. Under Turkish legal doctrine, a SaaS subscription is categorized as an innominate / mixed contract (karma sözleşme) governed by the general provisions of TCO No. 6098, combining elements of service performance, lease-like remote access, and data hosting.
Robust Turkish enterprise SaaS and software contracts address four commercial pillars:
- Usage Metrics & Audit Clauses: Defining named users, concurrent seats, API call ceilings, tenant environments, affiliate access rights, and non-disruptive remote license verification mechanisms.
- Service Level Agreements (SLAs) & Service Credits: Specifying monthly uptime guarantees (e.g., 99.9% excluding scheduled maintenance), severity-tiered incident response times, and Service Credits. Under Turkish law, to prevent a customer from claiming full general damages on top of service credits (per TCO Art. 180/2), the SLA should state clearly whether service credits constitute the sole and exclusive financial remedy for non-catastrophic downtime, along with a termination trigger for chronic SLA failure.
- Mission-Critical Continuity & Source Code Escrow: For core banking, ERP, hospital, or industrial software, Turkish enterprise buyers frequently require tri-party Source Code Escrow (with international agents or Turkish notary/trustee structures) releasing build documentation and source code strictly upon vendor bankruptcy, cessation of support, or insolvency.
- Enterprise AI & Customer Data Isolation: Modern SaaS agreements incorporating generative AI features expressly stipulate that Customer Input Data and Customer-Specific Output remain the exclusive property/confidential data of the customer and shall not be used to train or fine-tune foundation models accessible to third-party tenants.
IV. Enforceability of Limitation of Liability Caps under TCO Article 115
Global SaaS vendors almost universally insist on capping aggregate contractual and tortious liability at "12 months' subscription fees paid prior to the claim" while excluding indirect, consequential, and lost-profit damages altogether. When such agreements are governed by Turkish law—or enforced before Turkish courts where public-policy mandatory norms intervene—Article 115 of the Turkish Code of Obligations sets an absolute statutory ceiling on liability exclusions:
Turkish Code of Obligations No. 6098, Article 115(1) & (3):
"Any prior agreement excluding liability for gross fault (intent or gross negligence) is strictly null and void... If a service, profession, or trade requiring specialized expertise can only be conducted under official authorization granted by law or competent authorities, prior agreements excluding liability even for slight negligence are null and void."
Accordingly, in Türkiye:
- Liability caps and consequential-damage waivers are fully enforceable for slight/ordinary negligence (hafif kusur) in standard B2B commercial software contracts between merchants, as well as for acts of auxiliary personnel/sub-processors under TCO Article 116 (unless operating under a state-licensed specialized franchise such as banking or telecommunications).
- However, no contractual cap or exclusion can shield a vendor from willful misconduct (kasıt) or gross negligence (ağır kusur)—for example, knowingly deploying unpatched critical security vulnerabilities or intentionally deleting production tenant databases—nor from personal injury/death or statutory third-party data-subject compensation under KVKK. Drafting the limitation clause with an explicit carve-out for intent and gross negligence preserves the validity of the 12-month cap for ordinary operational incidents instead of risking judicial invalidation of the entire clause.
V. Foreign Currency Rules & Cross-Border Software Withholding Tax (Stopaj)
1. Foreign Currency Denominations (Decree No. 32 Exemptions)
When a non-resident foreign SaaS or software company bills a Turkish corporate customer directly from abroad, the contract may be freely priced and paid in USD, EUR, or GBP. Even where a foreign vendor invoices through a Turkish-incorporated subsidiary (making both contracting parties Turkish residents), Ministry of Treasury and Finance Communiqué No. 2008-32/34 provides a crucial technology carve-out: licensing and service agreements regarding software produced abroad (as well as hardware manufactured abroad) are exempt from the Turkish Lira payment mandate and may legally be denominated in foreign currency! Conversely, software developed domestically in Türkiye and licensed between two Turkish residents must be priced in TRY.
2. Corporate Withholding Tax (Stopaj) & Reverse-Charge VAT2
Cross-border payments from a Turkish company to a non-resident software/SaaS vendor trigger two major tax compliance checkpoints—which enterprise SaaS agreements address via explicit "Gross-Up / Net of Withholding Tax" clauses:
- Reverse-Charge VAT (KDV2 — 20%): The Turkish corporate customer self-assesses and remits 20% reverse-charge VAT via VAT Return No. 2 (which is generally recoverable as input VAT for VAT-paying commercial enterprises, though a real cost for VAT-exempt banks and insurance companies).
- Corporate Income Tax Withholding (KVK Art. 30 — 0% vs. 10% vs. 20%): Under Corporate Tax Law Article 30, domestic royalty payments to non-residents carry a statutory 20% withholding tax (reduced typically to 10% under most of Türkiye's Double Taxation Treaties upon presentation of an apostilled Certificate of Tax Residence). Critically, Turkish tax administration rulings distinguish between:
- Commercial Business Profits (0% Withholding under Tax Treaties): Standard off-the-shelf software subscriptions or multi-tenant SaaS access used solely for the Turkish customer's internal business operations—where no source code is transferred, no copyright modification/reproduction/redistribution right is granted, and the vendor has no Permanent Establishment in Türkiye—generally qualify as Article 7 Business Profits exempt from Turkish withholding tax!
- Royalties / Copyright Transfer (10%–20% Withholding): Payments acquiring underlying copyright ownership (20% domestic, subject to treaty capital-gains/royalty analysis) or granting rights to reproduce, customize source code, white-label, or commercially sub-distribute the software to third parties are taxed as Article 12 Royalties.
VI. KVKK Cloud Data Transfers & Regulated-Sector Data Localization
Whenever a SaaS vendor hosts personal data of Turkish employees, consumers, or end-users on cloud servers outside Türkiye (e.g., AWS eu-central-1 or US-East), Article 9 of Personal Data Protection Law No. 6698 (KVKK) governs the cross-border transfer. Following Türkiye's landmark June 2024 KVKK reform aligning cross-border transfers with EU GDPR methodology, Turkish controllers and foreign SaaS data processors no longer rely on fragile per-user explicit consent; instead, they execute official Turkish Standard Contractual Clauses (Standart Sözleşme — Controller-to-Processor or Processor-to-Processor modules) published by the KVKK Authority and notify the executed SCC to the Authority within 5 business days of signature (non-notification carries administrative fines on both controller and processor!).
However, foreign SaaS vendors targeting regulated Turkish verticals must account for strict sectoral localization laws that override general KVKK SCCs: core systems of banks (BDDK), payment/e-money institutions (CBRT Communiqué No. 2021/2), capital markets intermediaries/crypto platforms (SPK), defense contractors, and public-sector agencies (Presidential Digital Transformation Office Circular No. 2019/12) must store primary and disaster-recovery data physically inside Türkiye.
VII. Comparative Matrix: On-Premise License vs. SaaS vs. Custom Development
| Legal & Commercial Feature | On-Premise Software License | Cloud SaaS Subscription | Bespoke / Custom Software Development |
|---|---|---|---|
| Primary Statutory Regime | FSEK No. 5846 (Copyright License) + TCO general rules. | TCO No. 6098 (Mixed Service/Access Contract) + KVKK No. 6698. | TCO Arts. 470–486 (Work Contract / Eser Sözleşmesi) + FSEK Arts. 48 & 52. |
| IP Ownership Outcome | Vendor retains IP; customer receives term or perpetual object-code usage license. | Vendor retains 100% platform IP; customer owns Input/Output data only. | Developer retains IP unless FSEK Art. 52 itemized written assignment + post-completion deed is signed. |
| FX Contract Permissibility | USD/EUR permitted if non-resident vendor OR foreign-produced software; TRY if domestic. | USD/EUR permitted if non-resident vendor OR foreign-produced SaaS; TRY if domestic. | USD/EUR permitted if foreign party; strictly TRY if commissioned between two Turkish residents. |
| Cross-Border Withholding Tax | 0% (standard off-the-shelf internal copy under DTT) vs. 10%–20% if reproduction/resale rights granted. | Generally 0% under DTT Art. 7 (pure standard SaaS internal use with Tax Residency Certificate), subject to contract wording. | 20% (or 10% DTT royalty / professional service rules depending on IP assignment vs. development service). |
| Cloud & Data Compliance | Data stays on customer's local servers; minimal cross-border transfer issues. | Requires KVKK Art. 9 SCCs (notified in 5 business days); blocked in localized banking/public cores unless hosted in TR. | Governed by DPA confidentiality and secure development environment protocols. |
VIII. Software Piracy Remedies, Open-Source Audits & Dispute Resolution
Türkiye maintains specialized Intellectual and Industrial Property Civil and Criminal Courts (Fikri ve Sınai Haklar Hukuk ve Ceza Mahkemeleri) in Istanbul, Ankara, and Izmir experienced in enterprise software piracy and license over-deployment disputes. Under FSEK Article 68, where a commercial enterprise deploys unlicensed copies, cracked enterprise keys, or unauthorized virtualized seats beyond licensed ceilings, the rightsholder may obtain an ex parte technical court inspection (delil tespiti) of corporate servers and claim statutory compensation of up to three times (3x) the fair market license fee that would have been payable under a lawful contract—alongside criminal prosecution under FSEK Article 71 (carrying 1 to 5 years' imprisonment or judicial fines for corporate executives authorizing unlicensed software).
Finally, in bespoke software and tech M&A deals, licensees and acquirers must audit open-source dependencies to ensure restrictive "copyleft" licenses (such as GPLv3 or AGPLv3—the latter triggered even over network/SaaS interaction!) have not contaminated proprietary source code.
Key Legal Questions & Practical Answers
Often not in full. Under Article 52 of Turkish Copyright Law No. 5846 (FSEK), any transfer or exclusive license of software copyright must be in signed writing and must explicitly enumerate each individual economic right transferred (adaptation, reproduction, distribution, performance, and communication to the public). Generic umbrella phrases risk invalidation before Turkish IP courts, and future code modules require post-creation confirmatory assignment deeds under FSEK Article 48(3).
Yes for slight/ordinary negligence, but never for gross negligence or willful misconduct. Under Turkish Code of Obligations Article 115(1), any prior contractual limitation or exclusion of liability for intent or gross fault is mandatorily null and void. Drafting liability caps with an express carve-out for intent and gross negligence ensures Turkish courts uphold the cap (such as 12 months' fees) for ordinary operational breaches.
Yes. While Türkiye generally prohibits foreign-currency contracts between two Turkish residents, secondary legislation under Decree No. 32 explicitly exempts licensing and service contracts concerning software produced abroad. Therefore, foreign-origin enterprise software and SaaS subscriptions can lawfully be invoiced in USD or EUR even through a local Turkish reseller or subsidiary.
It depends on contract characterization and tax treaty documentation. If a Turkish enterprise purchases standard, unmodified SaaS access purely for internal business operations without acquiring source code, copyright ownership, or redistribution rights, and the foreign vendor provides an apostilled Certificate of Tax Residence under an applicable Double Taxation Treaty, payments generally qualify as exempt Business Profits (0% withholding) rather than Royalties (typically 10% treaty / 20% domestic)—though poorly drafted 'license' wording in invoices or contracts can trigger tax-audit reclassification.
For general commercial industries, yes—following Türkiye's 2024 KVKK Article 9 reform, parties can legitimize overseas cloud hosting by executing official KVKK Standard Contractual Clauses (SCCs) and filing them with the Turkish Personal Data Protection Authority within 5 business days of signing. However, regulated financial institutions (banks, payment/e-money firms, crypto exchanges) and public agencies remain bound by strict domestic data-localization laws requiring servers physically inside Türkiye.







