What FSEK Arts. 18, 48, 49 and 52 require, and what investors check in due diligence.
In a Turkish startup, rights in code that employees write while performing their work are exercised by the company, unless a special contract or the nature of the work indicates otherwise (Article 18/2 of Law No. 5846, FSEK). Code written by a freelancer or an outside agency stays with the developer until the rights are transferred in writing, with each right shown separately (FSEK Art. 52). Paying the invoice does not move them.
The question usually comes up in a funding round or an acquisition, when counsel for the other side asks the company to show who wrote each part of the code base and how the rights reached the company. This guide follows that chain: who holds the rights at the start, what a valid assignment contains, how future code is covered, what remains with the author, and where open-source licences change the picture.
1. Who Holds the Rights at the Start?
Computer programs are works of science and literature under FSEK Art. 2/1-1, in any form of expression, together with preparatory designs that lead to a program. Article 13 allows registration on request, so ownership does not depend on a certificate. Article 2 also sets a limit: the ideas and principles underlying any element of a program, including its interfaces, are not works. Copyright covers the code as written, not the idea behind an algorithm.
Under Article 8, the owner of a work is the person who created it, and under Article 18/1 the authority to exercise economic rights belongs exclusively to the author. The company therefore starts with nothing unless the statute or a contract gives it something.
| Who wrote the code | Starting position | What the company needs |
|---|---|---|
| Employee, while performing their work | Rights exercised by the employer (Art. 18/2), unless a special contract or the nature of the work indicates otherwise | An employment contract that describes the development duties |
| Director or other organ of the company | The same rule applies to organs of legal entities (Art. 18/2) | Corporate records and a written assignment for code outside that role |
| Freelancer, agency, foreign development house | Outside Art. 18/2; rights stay with the author | A written assignment that meets Art. 52 |
| Founder, before the company existed | Rights stay with the founder | A written assignment of the existing code to the company |
Payroll employees (FSEK Art. 18/2)
Article 18/2 reads: “Unless otherwise understood from the special contract between them or from the nature of the work, rights in works created by civil servants, employees and workers while performing their work are exercised by those who employ or appoint them.”
The test is the link with the work, not the place or the hour. Article 18/2 gives the employer the exercise of the rights by statute, so Article 52 is not the source of the employer’s position. A written clause is still useful, because it fixes which duties are in scope and removes the argument that the nature of the work points the other way.
Freelancers, agencies and independent contractors
Article 18/2 names civil servants, employees and workers. A contractor is not one of them. Paying invoices or a service fee does not satisfy Article 52, and without a written assignment that meets it, the developer stays the holder of the rights and the company has no title to show an investor.
Teams
Where several people create a work that can be divided into parts, Article 9 treats each as the owner of their own part. Where the work forms an inseparable whole, Article 10 treats the group as the owner. Article 10 adds that, unless a contract, service terms or a statute provides otherwise, the rights in such a work are exercised by the natural or legal person who brought the authors together. That rule is a narrow default and does not replace signed assignments in a diligence file.
Where the code was written by an employee rather than a contractor, a separate statutory procedure governs inventions arising from the work, set out in employee inventions and the four-month claim window. Where a single project mixes employees, contractors and a technopark tenancy, the allocation has to be settled across all four outputs at once (patents, software copyright, designs and know-how), which is the exercise described on our employee inventions and R&D intellectual property page.
2. What Must a Valid Assignment Contain?
Article 52 of FSEK says that contracts and dispositions concerning economic rights must be in writing and must show the rights forming their subject separately. Two consequences follow.
- Written form with a signature. Article 12/2 of the Code of Obligations No. 6098 makes a statutory form a condition of validity as a rule, and an agreement that ignores it has no effect. Article 14 requires the signature of those undertaking the obligation. Article 14/2 also accepts a signed letter, a confirmed fax or similar means, and a text sent and stored with a secure electronic signature, which under Article 15 has all the legal effects of a handwritten one. An ordinary email or chat message without such a signature does not meet this standard.
- Each right shown separately. A clause saying that all intellectual property belongs to the company does not show the rights separately. Article 20 adds that economic rights are independent of one another, so disposing of one does not affect the others. The agreement should list each right by its statutory name:
- Adaptation (FSEK Art. 21)
- Reproduction (FSEK Art. 22), which reaches loading, displaying, running, transmitting and storing a program to the extent they require temporary copies
- Distribution (FSEK Art. 23)
- Representation (FSEK Art. 24)
- Communication to the public by devices for transmitting signs, sounds or images (FSEK Art. 25), which includes access at a place and time chosen by the user
Article 48 allows the assignment to be limited or unlimited in time, place and content, and paid or free, so the agreement should state all three. It also separates an assignment from a licence. A company that only receives a licence is not the holder, and under Article 56 a licence is treated as non-exclusive unless the statute or contract indicates otherwise.
3. How Should Future Code, Adaptations and Onward Transfers Be Covered?
Three provisions decide whether an ordinary contractor agreement holds up over time.
Future code. Article 48/3 makes a disposition over a work not yet created or still to be completed void. Article 50/1 keeps an undertaking to make such a disposition valid even if it is given before the work exists. Under Article 50/2, either party can end an undertaking covering all future works, or a certain type of them, with effect one year after notice. A sound structure is an undertaking in the framework agreement, plus a signed assignment on each delivery or milestone that names the delivered code.
Adaptations. Under Article 55, the assignment of an economic right or the grant of a licence does not extend to translations or other adaptations unless otherwise agreed. Software is changed constantly, so the adaptation right belongs in the agreement expressly. Article 51 also makes void any contract on economic rights that future legislation may grant to authors.
Onward transfers. Under Article 49, a person who acquired an economic right or a licence from the author can transfer it to someone else only with the author’s or heirs’ written consent. A share sale leaves the rights in the company, while an asset sale moves them to the buyer. Where an asset deal is possible, the original assignment should record that consent.
4. Which Rights Stay With the Author?
Articles 14 to 16 give the author the power to decide on disclosure, the power to decide whether the work appears under a name, and the power to prohibit changes. Turkish doctrine treats these moral rights as personal and not assignable. A contract can still record the author’s written permission to publish the software, to release it without naming individual developers, and to change it.
That permission has a statutory limit. Under Article 14/3, the author can prohibit disclosure in a manner that harms their honour and reputation even after giving written permission. Under Article 16/3, the author can prohibit changes that harm honour and reputation or distort the nature and characteristics of the work, even after unconditional written permission. A waiver of either power is void. The clause should therefore be drafted as a permission, and should not be presented as a complete waiver. Article 16/2 separately allows changes that the technique of adaptation or reproduction makes necessary.
5. Open-Source Licences: Which Ones Reach Proprietary Code?
Open-source obligations come from the licence text rather than from Turkish statute, and they depend on how the software reaches users. The summary below is general; the licence version and the way the components are combined decide each case.
| License category | Examples | What to check |
|---|---|---|
| Permissive | MIT, Apache 2.0, BSD | Notice and attribution terms. Proprietary code can generally stay closed. |
| Weak copyleft | LGPL, MPL | Obligations centre on the library or files concerned and changes to them. |
| Strong copyleft | GPL v2, GPL v3 | Source obligations arise when copies are conveyed. GPLv3 section 0 says that mere network interaction, with no transfer of a copy, is not conveying. On-premise, desktop and mobile delivery need closer review. |
| Network copyleft | AGPL v3 | Section 13: if you modify the program, the modified version must offer users interacting with it remotely the opportunity to receive its corresponding source. |
6. What Do Investors Check in IP Due Diligence?
Before funding negotiations or an acquisition review, a company should be able to show:
- A signed assignment from each founder covering code written before incorporation.
- A signed assignment meeting Article 52 from every contractor, external developer and UI designer, with a delivery-level assignment for code written after the contract date.
- Employment contracts that describe development duties, and an inventory of anyone who worked on the code without one.
- A software composition scan listing open-source components and their licences, reviewed against the delivery model.
- Written consents under Article 49 for rights acquired from earlier assignees, where the chain has more than one step.
Gaps are normally closed by signing corrective assignments before closing, which is why the people concerned should be identified early, while they can still be reached.
Assignment paperwork settles ownership, but on its own it does not protect the know-how that never becomes a registered right, such as customer lists, pricing models and architecture decisions. That layer rests on the unfair competition provisions of the Commercial Code, as set out in trade secret protection in Türkiye. Where the code or the interface turns up on someone else’s site, the removal routes are statutory rather than contractual, and the two available ones are compared in online copyright takedown in Türkiye.
Diligence on the same file usually turns up restrictive covenants signed by the development team; the penalty clauses attached to them are examined in penalty clauses in non-compete covenants.