Who Owns a Software in Chile?
Titularidad y propiedad intelectual del software en Chile
Ownership and Intellectual Property of Software in Chile
When a company hires a developer to create an application, or when a programmer works on a software project within an employment relationship, the same question inevitably arises: who owns that software?
The answer is not always intuitive and can have enormous economic consequences. A common—and costly—mistake is assuming that whoever pays for the development automatically becomes the owner of the code. In Chile, the law establishes specific rules on software ownership that every entrepreneur, company, and developer should understand.
💡 In Chile, software is protected as an intellectual work under Law No. 17,336 on Intellectual Property, not through patents. This means that ownership is governed by the same rules that apply to books, music, or films.
1. How Does Chile Protect Software Ownership?
Software is considered an intellectual work and, as such, is protected in Chile under Law No. 17,336 on Intellectual Property. This law recognizes two types of rights:
- Moral rights: These are non-transferable and inalienable. They recognize the authorship of the person who created the code. A developer will always be able to claim authorship of their work, even if they have assigned all economic rights.
- Economic rights: These allow the commercial exploitation of the software: selling it, licensing it, reproducing it, or modifying it. These rights can be transferred through contracts.
Protection arises from the moment the software is created, without the need for prior registration. However, registration with the Department of Intellectual Rights (DDI) of the Ministry of Cultures provides a certain date and evidentiary support in case of disputes.
2. The Three Most Common Ownership Scenarios
2.1 Independent Developer (Freelancer)
When a company hires a developer as an independent contractor—without an employment relationship—the general rule is that the developer is the author of the code, unless a contract states otherwise.
This means that if a freelancer creates an application for your company and there is no rights assignment clause in the contract, they technically retain ownership of the code. The company would only obtain the final result—the functioning software—but not the right to freely modify it, sublicense it, or prevent the developer from using it in other projects.
⚠️ Common mistake: Paying for software development does not automatically grant intellectual property rights over the code. Without a rights assignment clause, the client may lack ownership.
2.2 Employee (Employment Relationship)
In an employment relationship, Article 8 (final paragraph) of Law No. 17,336 establishes that rights over works created by an employee in the course of their duties or following the employer’s instructions belong to the employer.
However, this rule has important nuances:
- It only applies if the software was developed within the scope of the employee’s job duties.
- If the employee developed the software outside working hours and without using employer resources, they may retain ownership, unless agreed otherwise.
- It is advisable for employment contracts to include an explicit clause addressing this issue to avoid future conflicts.
2.3 Development Outsourced Between Companies
When one company commissions another to develop software (technology outsourcing), the rules are similar to the freelancer scenario: the developing company owns the code unless the contract assigns rights to the client.
In this scenario, it is essential that the software development contract expressly includes:
- Full assignment of economic rights: The developer transfers all exploitation rights to the client.
- Delivery of source code: Without access to the source code, the client depends entirely on the provider for future modifications.
- Non-infringement warranty: The provider must guarantee that the software does not include third-party code with incompatible licenses.
3. Jointly Developed Software: Co-Ownership
When two or more parties collaborate on software development, co-ownership arises. This is common in startups, academic projects, or technology joint ventures.
Co-ownership has significant practical implications:
- None of the co-owners may license or transfer the software to third parties without the consent of the others.
- Decisions regarding commercial exploitation require agreement among all owners.
- In case of conflict, any co-owner may request judicial liquidation of the shared ownership.
For these reasons, in collaborative projects it is highly advisable to sign a shareholders’ agreement or co-ownership agreement from the outset
4. Open Source Software: What Happens to Ownership?
The use of open source libraries and components is common in software development. However, incorporating open source code does not eliminate ownership: the original author retains moral rights, and usage conditions are determined by the specific license.
Common open source licenses have different implications:
- Permissive licenses (MIT, Apache 2.0, BSD): Allow integration into proprietary software without requiring the entire project to be open source.
- Copyleft licenses (GPL, AGPL): Require that any software incorporating such code be distributed under the same open license, potentially preventing proprietary commercialization.
⚠️ Before commercially distributing software that includes open source components, it is essential to verify all licenses. A poorly managed GPL license may force you to disclose your entire source code.
5. Essential Clauses to Protect Ownership in a Development Contract
Regardless of the scenario, the contract is the key tool for clearly defining ownership. A well-drafted software development contract should include at least the following clauses:
Clause | Why It Matters |
Assignment of economic rights | Transfers all exploitation rights to the client, including modification, sublicensing, and commercialization. |
Source code delivery | Ensures the client receives the full code and can maintain or modify it with any provider. |
Originality statement | The developer guarantees the software is original and does not infringe third-party rights. |
Open source management | Identifies open source components and ensures their licenses are compatible with intended use. |
Confidentiality | Protects the client’s confidential information shared during development. |
Non-compete warranty | Limits the developer from using acquired knowledge to create competing products. |
6. Is It Useful to Register Software in Chile?
Registering software with the Department of Intellectual Rights (DDI) is not mandatory for legal protection—it arises automatically upon creation—but it offers important practical advantages:
- Certain date: Establishes an official creation date, crucial in authorship disputes.
- Proof of ownership: Facilitates the enforcement of rights before courts or institutions.
- Licensing support: Some agreements require registration as part of due diligence.
- Deterrence: Public registration discourages infringement.
The registration process in Chile is relatively simple and can be completed online through the DDI portal. It requires a software description, a sample of the source code (which may be partial), and ownership details.
7. Frequently Asked Questions
Is an app name protected by copyright?
No. The name or brand of an application is protected through trademark registration with INAPI, not copyright. Copyright protects the source code, graphical interface, and structure, but not the commercial name.
Can I patent my software in Chile?
Generally, no. Chile does not recognize software patents as an independent category. Software is protected by copyright, which protects the expression of the code, not the underlying idea.
What happens if the developer dies before delivering the software?
Economic rights form part of the developer’s estate and pass to heirs. Contractual assignments remain valid. For critical projects, continuity mechanisms such as source code escrow are recommended.
Can a foreign company claim rights over software developed in Chile?
Yes. Chile is part of the Berne Convention and WIPO, meaning copyright protection is recognized internationally.
Conclusion
Software ownership is one of the most valuable intangible assets of a technology company—and one of the most frequently unprotected. In Chile, Law No. 17,336 provides a clear framework, but its practical application largely depends on the contracts signed during development.
Whether you are hiring a developer, forming a tech venture, or acquiring external software, well-drafted contracts and specialized intellectual property advice can make the difference between truly owning your software or facing a costly dispute.
Do you need to protect your software or review a development contract?
At von Marttens Torres, we specialize in intellectual property and technology contracts.
Contact us at contacto@vonmarttens.cl
AI Usage Information: This article was written by members of our team; however, AI tools were used to improve readability and structure the text for search engines.
