Apps & Software
Source Code Ownership: Required Clauses in an Application Development Contract
Paying for an application does not automatically make its source code yours. These eight clauses make sure the company holds the code, access, and documentation needed to continue the system.
SEO and Content Specialist
4 min read
Short answer: make sure the contract states in writing that copyright in the source code is transferred to the company, that the code is stored in a repository under the company’s name, and that the vendor hands over the documentation, access, and credentials for every service the application uses. Without those clauses, under the Copyright Law, the party who creates a work on commission is the creator and copyright holder, unless agreed otherwise.
This article covers the technical points to confirm in a contract, not legal advice. The wording of the clauses should be drafted together with your company’s legal counsel.
Many companies only think about source code ownership when the relationship with the vendor ends: the vendor closes down, the maintenance price goes up, or the internal team wants to continue development itself. Only then does it turn out that the code was never handed over, the server is registered in the vendor’s name, or there is no documentation that would let anyone else carry on. All of this can be prevented in the contract.
Why it has to be in writing
Article 36 of Law Number 28 of 2014 on Copyright states that, unless agreed otherwise, the creator and copyright holder of a work made in an employment relationship or on commission is the party who made the work. Computer programs are among the protected works. This means that, without an agreement stating otherwise, paying for an application does not by itself make you the copyright holder of its code.
The eight clauses that need to be there
| Clause | What it ensures |
|---|---|
| Copyright transfer | Copyright in the source code and designs made specifically for the project transfers to the company |
| Repository in the company’s name | The code is stored in a repository account owned by the company from the start, not handed over at the end |
| Third-party components | A list of libraries, plugins, and third-party services along with their licenses |
| Documentation | Technical documentation and user guides sufficient for someone else to continue the work |
| Access and credentials | Servers, domains, cloud services, databases, and app store accounts registered in the company’s name |
| Data | Data stored in a system owned by the company and exportable in full |
| Handover | A list of what is handed over at the end of the project, and the handover record |
| Confidentiality | The vendor keeps the code and data confidential, including after the contract ends |
A repository from day one, not at the end
Code that is only handed over at the end of a project often arrives without change history, without configuration files, or in a form that cannot be run right away. It is safer if the repository is created in the company’s own account from the start, with the vendor given access as a developer. That way the full history is kept, and you can see the progress of the work at any time.
Third-party components and their licenses
Almost every application uses libraries and components made by others, including open-source software. Copyright in these components does not pass to you; what you get is the right to use them under their licenses. Ask for a list of components with their licenses, so that no component with a paid license, or a license that restricts commercial use, comes along without your knowing.
Access that is often forgotten
Source code alone is not enough to run an application. Also make sure the company holds:
- the accounts for the servers or cloud services where the application runs, along with their billing;
- the domain and certificates in use;
- accounts for third-party services such as email delivery, payments, or maps;
- developer accounts in the Apple and Google app stores for mobile apps, along with the app signing files;
- the admin passwords for the database and management panels.
Checks before signing
Before the contract is signed, compare the draft contract against this list:
- Is there a sentence stating that copyright in the code and designs made specifically for the project transfers to the company?
- Is it clear which components remain the vendor’s, and what usage rights you get for them?
- Are the repository, servers, domain, and service accounts stated to be registered in the company’s name?
- Are the contents of the documentation and the form of the handover itemized, rather than just called “documentation”?
- Is there a provision for what happens if the contract ends early, including the handover of work already completed?
If any answer is “no”, ask for the wording to be added. A vendor acting in good faith generally does not object, because these clauses also clarify the limits of their own responsibility.
How Legia handles it
In the Web Application Development service, the source code and its usage rights are yours and are stored in a repository under the company’s name, along with technical documentation and user guides so that other developers can continue without needing to ask Legia. For mobile apps, the code, documentation, and app signing files are handed over in full. Considerations before deciding to build your own application are in the article Custom Application, Off-the-Shelf Software, or Spreadsheet, and other related services are on the Applications & Software page.
Frequently asked questions
Can the vendor reuse code from our project?
It depends on the contract. General components the vendor already owned before the project often stay with the vendor, with you getting the right to use them. The parts made specifically for your project should be stated to transfer to you.
What about an application that is already finished without these clauses?
Talk with the vendor about making an additional agreement on the transfer of copyright and the handover of the code. It is easier to do while the working relationship is still good.
Does code ownership also apply to off-the-shelf software or SaaS?
No. With off-the-shelf software or SaaS, you buy or rent the right to use it, while the code remains the vendor’s. What needs to be confirmed there is ownership of your data and the ability to export it.


