Apps & Software
Does the Company That Pays for an App Automatically Own Its Source Code?
Not automatically. Under the Copyright Law, the creator and copyright holder of a commissioned work is the party that made it, unless agreed otherwise.
SEO and Content Specialist
2 min read
Short answer: not automatically. Article 36 of Law Number 28 of 2014 on Copyright states that, unless agreed otherwise, the creator and copyright holder of a work made on commission is the party that made the work. For the source code of an application to belong to the company that ordered it, the transfer of copyright needs to be written into the contract.
A summary of the provisions for planning purposes, not legal advice. Contract wording should be prepared together with legal counsel.
Why this often comes as a surprise
Many companies assume “we paid, so we own it.” For physical goods, that logic is usually right. For creative works such as computer programs, the law provides otherwise: without an agreement, copyright stays with the maker. The consequences are only felt later, for example when you want to switch vendors, continue development with your own team, or sell a part of the business that uses the application.
Copyright and usage rights are different
The copyright holder has the right to decide who may copy, modify, and distribute the code. A usage right only grants permission to use the application. A company that holds only usage rights can keep running the application, but may run into trouble when it wants to modify the code itself, move it to another vendor, or reuse parts of the code in a new system.
What to write in the contract
| What to write | Why |
|---|---|
| Transfer of copyright over code and designs made specifically for the project | Replaces the default provision of Article 36 |
| Boundaries of the vendor’s pre-existing components | The vendor’s general components usually stay with the vendor; you get a usage right |
| A list of third-party components and their licenses | Copyright in third-party components does not transfer, only the right to use them |
| Delivery of code, documentation, and access | Copyright without code and access cannot be used |
One more thing: a copyright transfer in the contract should be accompanied by an actual handover. Code kept in a repository under the company’s name from the start of the project is much safer than a promise to hand it over at the end, because the full history is stored with it and you can inspect its contents at any time.
What about an application that has already been built?
Talk to the vendor about drawing up a supplementary agreement that transfers the copyright and regulates the handover of the code. Do it while the working relationship is still good, not once a dispute has started. The full list of clauses, including server access, domains, and app store accounts, is in the article Source Code Ownership: Required Clauses in an App Development Contract.
At Legia, the source code of applications built under the Web Application Development service, along with its usage rights, belongs to you and is kept in a repository under the company’s name.

