Who Owns Source Code Written for a Turkish Startup? Employees, Contractors and FSEK Arts. 18, 48 and 52

Does code written by employees or contractors automatically belong to a Turkish company?

If this question concerns a matter of your own, you can write to us with the documents you have: Write on WhatsApp · Email us.

Av. Onur ÇalışıcıPublished 20 August 2026 · 10 min read
Engraving: a laptop with its screen off, a gear wheel, a ribboned assignment agreement, a brass key and a Turkish tea set.

In brief

  1. Under Article 18/2 of Law No. 5846 (FSEK), rights in works that employees create while performing their work are exercised by the employer, unless a special contract or the nature of the work indicates otherwise.
  2. Article 18/2 covers civil servants, employees and workers, and the organs of legal entities. A freelancer or outside agency is not on that list, so the company needs a written assignment.
  3. Article 52 requires contracts and dispositions on economic rights to be in writing and to show each right separately. Under Articles 12 and 14 of the Code of Obligations, the signature of the person undertaking the obligation is required, and a text sent and stored with a secure electronic signature also counts.
  4. Article 48/3 makes a disposition over a work not yet created void, while Article 50 keeps an undertaking valid, and either side can end an undertaking covering all future works or a type of them on one year's notice. Future-code clauses should be drafted around that split.
  5. Copyleft risk depends on the licence and the delivery model: GPLv3 does not treat mere network interaction as conveying, while AGPLv3 section 13 reaches modified versions used remotely.

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.

A closed laptop with an arrow leading to a signed document, and a key placed beside the document.
Software ownership should be transferred in writing.

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 codeStarting positionWhat the company needs
Employee, while performing their workRights exercised by the employer (Art. 18/2), unless a special contract or the nature of the work indicates otherwiseAn employment contract that describes the development duties
Director or other organ of the companyThe 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 houseOutside Art. 18/2; rights stay with the authorA written assignment that meets Art. 52
Founder, before the company existedRights stay with the founderA 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.

  1. 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.
  2. 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 categoryExamplesWhat to check
PermissiveMIT, Apache 2.0, BSDNotice and attribution terms. Proprietary code can generally stay closed.
Weak copyleftLGPL, MPLObligations centre on the library or files concerned and changes to them.
Strong copyleftGPL v2, GPL v3Source 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 copyleftAGPL v3Section 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:

  1. A signed assignment from each founder covering code written before incorporation.
  2. 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.
  3. Employment contracts that describe development duties, and an inventory of anyone who worked on the code without one.
  4. A software composition scan listing open-source components and their licences, reviewed against the delivery model.
  5. 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.

A magnifying glass stands in front of a laptop with its screen switched off and several file folders.
The company's intellectual property is reviewed before an investment goes ahead.

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.


Frequently asked questions

Does code written by an employee outside working hours belong to the company?

Article 18/2 of FSEK does not set an hours test. Its test is whether the work was created while the employee was performing their work, read with any special contract and the nature of the work. Code written after hours on a task the job requires can still fall inside it, and code unrelated to the job may fall outside it, so the employment contract should describe the development duties clearly.

Can moral rights (manevi haklar) be transferred to the company under Turkish copyright law?

FSEK Arts. 14 to 16 give moral rights to the author, and Turkish doctrine treats them as personal and not assignable. A contract can record the author's written permission to publish, to leave the name out and to change the code. Even so, Arts. 14/3 and 16/3 keep the author's power to prohibit disclosure or changes that harm honour and reputation, or changes that distort the nature of the work, and a waiver of that power is void.

Does paying a freelancer transfer the source code to the company?

No. Payment is not one of the requirements in FSEK Art. 52. The company needs a written document that shows each economic right separately. Without one, the rights stay with the developer who created the code.

Is an email or Slack message enough to assign code?

Normally not. Article 12/2 of the Code of Obligations makes a statutory form a condition of validity as a rule, and Article 14 requires the signature of the person undertaking the obligation. Article 14/2 accepts a signed letter, a confirmed fax or similar means, or a text sent and stored with a secure electronic signature. An ordinary message without a signature does not meet that standard.

Can a contract assign all code a developer will write in the future?

Article 48/3 makes a disposition over a work not yet created void. Article 50/1 keeps an undertaking to make that disposition valid, and Article 50/2 lets either party end an undertaking covering all future works, or a type of them, one year after notice. The usual answer is an undertaking in the main contract and a signed assignment on each delivery.

Are algorithms protected by copyright in Turkey?

Article 2 of FSEK protects computer programs in any form of expression, and their preparatory designs if they lead to a program. Its closing paragraph says that the ideas and principles underlying any element of a program, including its interfaces, are not works. Those ideas need other protection, such as confidentiality.

Does using GPL code force a SaaS company to publish its code?

Not by itself. GPLv3 attaches its source obligations to conveying, and its section 0 says that mere interaction with a user over a network, with no transfer of a copy, is not conveying. The position changes when software is delivered to customers, for example as an on-premise or mobile product. AGPLv3 section 13 goes further: a modified version must offer its remote users the corresponding source.

This guide is general information, not legal advice. For advice on your specific situation, speak with a lawyer. Prepared by Lex Lata Consulting & Law.

Av. Onur Çalışıcı

Av. Onur Çalışıcı

About the author · Founding Attorney · Istanbul Bar Association · Bar reg. no 83426

Lex lata is Latin for “the law as it is”. The office was founded by Av. Onur Çalışıcı, and you deal with Av. Çalışıcı directly from the first meeting to the end of the matter. With foreign clients we write in English and explain what each Turkish document says.

Tell us briefly what happened and we will get back to you. This guide is general information, not advice on your case.

Last reviewed: November 2026 · LinkedIn: linkedin.com/in/onurcalisici

OfficeKarataş Sk. No:6, SNS Plaza Kat:3, Kağıthane, Istanbul

On screen

Beyaz TV · Beyaz Ana Haber · September 2026 · In Turkish

Evicting a tenant who disturbs the neighbours

Why a tenant's unbearable conduct has to be shown with concrete evidence, and the exceptional cases in which the 30-day period may not be required.

Office and events

Gürsel Mah., Karataş Sk. No:6, SNS Plaza Kat:3, Kağıthane / İstanbul · Address and directions

The Lex Lata office in Kağıthane, Istanbul: desks and wall screens showing the Lex Lata logo
The office · Kağıthane, Istanbul
Av. Onur Çalışıcı on the blockchain law panel at Blockchain Expo World, Istanbul, July 2024
Blockchain law panel · Blockchain Expo World, Istanbul · July 2024
A meeting around the table in the Lex Lata meeting room
Meeting room · Kağıthane, Istanbul

SNS Plaza, Kağıthane, IstanbulContact page