Contractor code IP assignment verification is one of the most frequently overlooked legal risks for startups hiring talent in Latin America. Unlike in the United States where "work for hire" doctrine may automatically vest ownership in the hiring party, most LATAM jurisdictions require an explicit, written IP assignment agreement — and even then, the requirements vary significantly by country. Whether you are building a SaaS product with developers in Buenos Aires, a fintech platform with a team in São Paulo, or an enterprise application with engineers in Mexico City, understanding IP assignment is critical to protecting your company's most valuable asset before fundraising or acquisition.
Why IP Assignment from LATAM Contractors Matters
The fundamental question in any IP assignment scenario is: who owns the code that a contractor writes? In most LATAM jurisdictions, the answer is not the company paying for the work — at least not by default. Argentina, Brazil, and Mexico all have strong author's rights frameworks that vest initial ownership in the human creator, not the commissioning party. This is a critical difference from US work-for-hire doctrine, and it has significant implications for startups that discover the gap during Series A due diligence.
IP due diligence conducted by institutional investors now routinely includes a review of contractor agreements and IP assignment documentation. Investors want confirmation that all code in the product is owned by the company, that no contractor retains residual rights, and that open source compliance has been maintained throughout development. A missing or defective IP assignment clause is often sufficient to derail or significantly complicate a funding round.
Argentina: Ley 11.723 and IP Assignment
Argentina's software copyright framework is governed primarily by Ley 11.723 (the Argentine Copyright Law), which was amended in 1998 to explicitly include computer programs as protected works. Under this framework, copyright vests automatically in the creator at the moment of creation — there is no registration requirement. For contractors, this means the developer owns the code unless a written IP assignment explicitly transfers ownership to the hiring company.
The IP assignment clause must be clearly drafted to cover all works created during the engagement, including improvements, derivative works, and background IP incorporated into the deliverable. Argentine courts have generally upheld IP assignments when they are specific and clearly documented, but vague or generic clauses — such as "all work product belongs to the company" — may not be sufficient to transfer rights in all circumstances, particularly for moral rights that are inalienable under Argentine law.
Ley 11.723 — Argentine Copyright Law
Governs copyright protection for software in Argentina. Copyright vests in the creator automatically. Moral rights (right of attribution, right of integrity) are inalienable and cannot be transferred by IP assignment.
Brazil: Lei 9.610 and Software IP
Brazil operates one of the most comprehensive software IP frameworks in Latin America, governed by both Lei 9.610 (the Brazilian Copyright Law) and Lei 9.279 (the Brazilian Industrial Property Law). Under the Brazilian copyright framework, software created by a contractor belongs to the contractor by default unless there is a written agreement assigning those rights. Brazil's labor law (CLT — Consolidação das Leis do Trabalho) also creates a presumption of employer ownership for works created by employees, but this presumption does not automatically extend to independent contractors.
For foreign companies hiring Brazilian contractors, the IP assignment agreement should be governed by Brazilian law and should include explicit language covering the transfer of all economic rights (direitos patrimoniais) in the software. Brazilian law distinguishes between economic rights, which can be transferred, and moral rights (direitos morais), which are inalienable. Any IP assignment from a Brazilian contractor can transfer economic rights but cannot extinguish the contractor's moral rights, including the right of attribution.
The TRIPS Agreement, to which Brazil is a signatory, establishes minimum standards for IP protection that apply across all covered jurisdictions. Under TRIPS obligations, software is protected as a literary work and the term of protection is at least 50 years from publication or creation, providing a long window during which IP assignment defects can be raised.
Lei 9.610 — Brazilian Copyright Law
Governs copyright in Brazil including software. Economic rights are transferable via written assignment; moral rights are inalienable. Foreign companies must use written contracts in Portuguese or bilingual format for best enforceability.
Mexico: LFDA and IP Assignment Enforceability
Mexico's copyright framework for software is governed by the Ley Federal del Derecho de Autor (LFDA), administered by the IMPI (Instituto Mexicano de la Propiedad Industrial). As in Argentina and Brazil, copyright vests in the creator by default. However, Mexico has a specific provision addressing works created under employment: works created by employees in the normal scope of their duties belong to the employer. This provision does not automatically extend to independent contractors.
For contractors in Mexico, a written IP assignment agreement is essential. The agreement should be notarized for significant transactions, as notarized documents carry higher evidentiary weight in Mexican courts. The LFDA also recognizes moral rights that are inalienable, so IP assignments from Mexican contractors can transfer economic rights but not the right of attribution or the right to object to derogatory modifications.
LFDA — Ley Federal del Derecho de Autor (Mexico)
Mexico's primary copyright law governing software. Administered by IMPI. Economic rights are transferable; moral rights are inalienable. Notarization of IP assignments is recommended for enforceability in Mexican courts.
Country-by-Country IP Assignment Comparison
| Criterion | Argentina | Brazil | Mexico |
|---|---|---|---|
| Default ownership | Creator/contractor | Creator/contractor | Creator/contractor |
| Written assignment required | Yes | Yes | Yes (notarized recommended) |
| Work for hire doctrine | Limited (employees only) | Limited (employees under CLT) | Limited (employees in scope) |
| Moral rights transferable | No (inalienable) | No (inalienable) | No (inalienable) |
| Open source compliance | Ley 11.723 applies | Lei 9.610 applies | LFDA applies |
| Registration required | No | No | No |
| Primary authority | INPI Argentina | INPI Brazil | IMPI Mexico |
IP Assignment Verification Checklist
When conducting IP assignment verification as part of contractor compliance or pre-fundraising due diligence, the following checklist covers the most critical elements across LATAM jurisdictions.
- Written IP assignment signed by the contractor (not just an invoice or statement of work)
- Assignment covers all deliverables, improvements, and derivative works
- Agreement specifies which jurisdiction's law governs
- Open source compliance: no LGPL v2, GPL v3, or AGPL v3 code incorporated without disclosure
- Background IP: any pre-existing IP used by the contractor is either licensed or excluded
- For Brazil: economic rights specifically transferred, Portuguese version available
- For Mexico: notarization for high-value assignments
- Evidence that contractor classification was correct (not a misclassified employee)
Open Source Complications in IP Assignment
IP assignment verification becomes significantly more complex when contractors have incorporated open source code into the deliverables. Under the MIT License, Apache License 2.0, or BSD licenses, the contractor can freely use and incorporate the code, but the open source license obligations travel with the code through any IP assignment. Under the GNU General Public License (GPL v3) or AGPL v3, incorporation can create copyleft obligations that affect the entire codebase — obligations that do not disappear when IP is assigned.
For LATAM contractors working on open source compliance, the critical question is whether any copyleft-licensed code has been incorporated in a way that requires the entire product to be open-sourced. This is known as GPL contamination, and it represents one of the most significant IP due diligence risks in tech M&A and Series A due diligence. Under the TRIPS Agreement framework, these license obligations are enforceable across all LATAM jurisdictions.
Our LATAM Contractor Legal Stack at a fixed price of $149/mo Starter tier provides monthly monitoring of contractor IP assignment status, open source compliance, and misclassification risk — with 48-hour delivery of any flagged issues. For companies with contractors in multiple countries, the Standard tier at $299/mo covers up to three countries with quarterly contract health checks. Get your report and ensure that your contractor code is legally yours before fundraising.
Frequently Asked Questions
What is IP assignment and why does it matter for LATAM contractors?
IP assignment is a written legal agreement that transfers copyright ownership from the creator (the contractor) to the commissioning party (your company). In LATAM jurisdictions including Argentina, Brazil, and Mexico, copyright vests automatically in the human creator. Without a written IP assignment, the contractor owns the code they write for you, even if they were paid to write it. This means you may be using and distributing code you do not legally own — a critical risk discovered during Series A due diligence or M&A transactions.
How do I verify IP assignment from a Brazilian contractor?
To verify IP assignment from a Brazilian contractor, you need: (1) a written contract in Portuguese or bilingual format that explicitly assigns all economic rights (direitos patrimoniais) in the software to your company; (2) confirmation that the contractor has not incorporated GPL v3, AGPL v3, or other copyleft-licensed open source code without disclosure; (3) verification that the contractor's classification is correct — a misclassified employee in Brazil under the CLT may have different IP ownership implications than a true independent contractor. Our LATAM Contractor Legal Stack audit covers all three areas with a fixed price and 48-hour delivery.
What happens if a contractor didn't sign an IP assignment agreement?
If a contractor in Argentina, Brazil, or Mexico created code for your company without signing an IP assignment agreement, the contractor likely owns the copyright in that code. You may be using and distributing that code without legal title. To remediate this situation, you should obtain a retroactive IP assignment from the contractor, which is possible but may require negotiation and compensation. If the contractor is no longer available or refuses to sign, you may need to rewrite the affected code. This is why pre-fundraising IP due diligence is critical — discovering this issue during Series A diligence causes significantly more disruption than addressing it proactively. Get your report before your investors find the gap.
Does open source code affect IP assignment validity in LATAM?
Yes. Open source compliance and IP assignment are related but distinct issues. A contractor may validly assign their own original code to you, but if they incorporated GPL v3 or AGPL v3 licensed code into the deliverable, the copyleft obligations of those licenses are not assignable — they travel with the code regardless of ownership. This means you can own the IP but still be bound by open source license obligations that restrict how you can commercialize the product. A thorough IP assignment verification process must include open source license mapping, which our GitHub IP Audit and LATAM Contractor Legal Stack services both cover.
Secure Your Contractor IP Before Fundraising
Verify IP assignment, open source compliance, and contractor classification across LATAM in one fixed-price audit. 48-hour delivery. No surprises at due diligence.