Software License Agreement in Turkey: Template, Key Clauses and Local Law (2026)

A software license agreement in Turkey is the contract by which the rights holder grants a customer the right to use software without transferring ownership of it. Turkey has no standalone software statute. Software is protected as a work under copyright law, so the licence rests on the Law on Intellectual and Artistic Works No. 5846, with a formal written requirement that catches many cross-border templates by surprise. This guide explains the Turkish legal framework, the clauses a software licence should carry, and a template skeleton. It is general information, not legal advice. ## What law governs a software license in Turkey? The framework is: - The Law on Intellectual and Artistic Works No. 5846 (FSEK), which classifies computer programs as works and protects them by copyright. Protection arises on creation and does not depend on registration. The rights holder has exclusive economic rights, including reproduction, adaptation (processing), distribution and communication to the public.

• The written-form rule in Article 52. A contract that transfers or licenses economic rights over a work is valid only if it is in writing and specifies the rights concerned. For online contracts commentary treats a qualified electronic signature as meeting this requirement, although courts have in practice upheld many clickthrough licences for mass-market software.
• The Turkish Code of Obligations No. 6098 for general contract terms, with Article 27 invalidating terms that breach mandatory law or public order, and the Law on the Protection of Personal Data No. 6698 (KVKK) where the software processes personal data. ## Is a software license enforceable in Turkey? Yes, but form matters. Two practical points: - Put the licence in writing and name the rights. Under Article 52, a licence of economic rights is valid only in writing and should specify which rights are granted, their scope, territory and duration; a signature by a qualified electronic signature supports an online licence.
• Default ownership favours the author. Without clear terms, the developer keeps the rights in custom software. For software made by an employee in the course of duties, the employer generally holds the economic rights while the employee keeps moral rights. ## Key clauses in a Turkish software license agreement ### Licence grant and scope State exactly which economic rights are granted, whether the licence is exclusive or non-exclusive, and the permitted users, sites, territory and term. ### Restrictions Set limits on copying, reverse engineering, sublicensing and transfer, within the limits copyright law allows. ### Fees and audit Set licence fees, any usage metrics and audit rights to confirm licensed use. ### Intellectual property and ownership Confirm the licensor keeps ownership and the licensee gets only the stated rights; address custom development and who owns it. ### Maintenance, support and updates State whether support, updates and new versions are included and on what terms. ### Warranties and liability Give the warranties offered, cap liability, carve out items that should not be capped, and keep the allocation within Article 27 limits. ### Data protection (KVKK) Where the software processes personal data, set the roles, security and any cross-border transfer basis under KVKK No. 6698. ### Term, termination and effect Set the term, termination rights, and what happens to use and copies of the software on termination. ### Governing law and disputes Choose Turkish law and a forum. ## Template skeleton ```

1. Parties and definitions
2. Licence grant and scope
3. Restrictions on use
4. Fees and audit
5. Intellectual property and ownership
6. Maintenance, support and updates
7. Confidentiality
8. Warranties and disclaimers
9. Liability and indemnities
10. Data protection (KVKK No. 6698)
11. Term, termination and effect of termination
12. Governing law (Turkey) and dispute resolution
13. Signatures

- **Software is protected as a work.** Copyright arises on creation without registration, and the economic rights listed in the law are the ones a licence has to grant expressly.
- **Default ownership favours the author.** Spell out custom development and employee-created software to avoid the default rules deciding it.
- **Article 27 and KVKK still apply.** Liability clauses must stay within mandatory law, and personal data processing brings KVKK duties. ## Common mistakes to avoid - Relying on an oral or loosely documented licence that fails the Article 52 written-form rule.
- Granting rights in vague terms instead of naming the specific economic rights, scope and term.
- Assuming the customer owns custom code without a clear assignment.
- Ignoring KVKK where the software clearly processes personal data. ## From the licence to the estate you actually manage Signing the licence is one moment; managing a software estate is continuous. Someone has to track each licence's scope and user limits, watch renewal and audit terms, and find the right clause fast when usage grows or a vendor asks for a true-up. Across many licences, that work is easy to lose. An AI contract workspace keeps each licence, its clause structure and its key dates in one place, so you can draft from a template, see where terms are one-sided, edit in plain language and get a reminder before a deadline. If you want to see drafting, review, tracking and governance in a single workspace, [Adira](https://adiralaw.com) is built around that idea. Deep Turkey-specific jurisdiction coverage is on Adira's roadmap today; India is deepest now. ## FAQ