Contracts in Brazil

Who owns the code? IP clauses with Brazilian developers

After the Supreme Court left the human authorship rule in place, code ownership is a contract question, and Brazilian law sets its own defaults for employees, contractors and transfers.

By Rafael Parodi Ferraresso5 min read

In March 2026 the US Supreme Court declined to hear Thaler v. Perlmutter (No. 25-449, certiorari denied on March 2, 2026), leaving in place the D.C. Circuit’s decision of March 18, 2025, which held that a work generated by a machine alone has no author under the Copyright Act. A year earlier, in January 2025, the US Copyright Office had reached a related conclusion in Part 2 of its report on copyright and artificial intelligence, stating that, “based on the functioning of current generally available technology, prompts do not alone provide sufficient control.” For software companies whose engineers now write a good share of their code with AI assistants, the question has moved from philosophy to paperwork: who owns what the team ships, and can the company prove it?

The answer has always depended on a second layer that is easy to forget, which is the contract with the people who actually write the code, and that layer works differently when the developers, the agency or the outsourcing vendor are in Brazil.

The US starting point: contractors need an assignment

Under US law, code written by an employee within the scope of employment is a work made for hire, so the employer is treated as the author. Code written by an independent contractor is another matter, because the work-for-hire route for commissioned works in 17 U.S.C. § 101 requires a written instrument signed by the parties and covers only nine listed categories, and computer software is not among them. That is why US companies rely on an express assignment of copyright signed by the contractor, rather than on a work-for-hire label alone.

Brazil: the default favors the company, with conditions

Brazil protects software under its own statute, the Software Law (Law 9,609/1998), which applies the copyright regime for literary works (art. 2), grants protection for 50 years counted from January 1 of the year after publication or, if there is none, after creation (art. 2, § 2), and does not depend on registration (art. 2, § 3, and art. 3). The central rule on ownership is art. 4: unless the parties agree otherwise, the rights in a program belong exclusively to the employer or to the party that hired the services when the program was developed during the contract and the contract was expressly aimed at research and development, the developer’s activity was foreseen in it, or the program results from the nature of the duties.

At first glance this is friendlier to the company than the US rule, since it reaches service providers and not only employees, and the developer’s compensation is limited, unless agreed otherwise, to the salary or fee already agreed (art. 4, § 1). The same treatment applies to interns and scholarship holders (art. 4, § 3).

The conditions matter, though, because the rights stay with the developer when the program was created with no link to the contract and without the company’s resources, such as technological information, trade secrets, materials, facilities or equipment (art. 4, § 2). In practice the disputes tend to sit at the edges: a tool built on a weekend that later becomes part of the product, code written before the contract started, or a contractor whose scope was described so vaguely that it is hard to say the work was foreseen in it.

When ownership moves by transfer

Many cross-border arrangements do not fit neatly into art. 4, for example when a US company acquires a platform that a Brazilian vendor had already built, or when a Brazilian agency subcontracts freelancers to deliver the work. In those cases ownership moves by assignment, and Brazil’s Copyright Law (Law 9,610/1998) has rules that often surprise foreign counsel:

  • a total and definitive transfer is only admitted by a written contract (art. 49, II), and without a written term the transfer lasts at most five years (art. 49, III);
  • the assignment is valid only for the country where the contract was signed, unless the contract says otherwise (art. 49, IV);
  • it covers only the forms of use that existed on the date of the contract (art. 49, V), and when the contract does not specify them it is interpreted restrictively (art. 49, VI);
  • a total transfer covers all economic rights but not moral rights (art. 49, I), and an assignment is always made in writing and is presumed to be for consideration (art. 50).

A short US-style sentence in which the contractor “hereby assigns all right, title and interest” may still do the job, but it is safer to add a worldwide territory, the full term of protection, a broad description of the forms of use and the consideration, so that a Brazilian judge or arbitrator has no reason to read the clause narrowly.

AI-generated code adds a third layer

The Thaler decision and the Copyright Office report deal with US law, and the Brazilian Software Law, enacted in 1998, says nothing specific about code produced with AI assistants. What the contract can do, on both sides of the border, is allocate the risk: require developers and vendors to disclose which AI tools they use, follow the company’s policy on those tools and on open-source licenses, and keep a record of the human review and editing that supports a claim of authorship. Where part of the output may not be protected by copyright at all, confidentiality and trade secret clauses become the main line of defense, so they deserve the same care as the assignment itself.

Checklist for contracts with Brazilian developers and vendors

  1. Describe the scope concretely, so the work is clearly foreseen in the contract for the purposes of art. 4 of the Software Law.
  2. Include an express written assignment of the economic rights, worldwide, for the full term of protection, with the forms of use spelled out and the consideration stated.
  3. Deal with pre-existing code and tools, listing them and granting a license when they stay with the developer.
  4. Address AI tools and open-source components, with disclosure duties and a review process.
  5. Keep confidentiality and trade secret clauses strong, since they protect what copyright may not.
  6. Align governing law, forum and arbitration with the assignment, so the clause is read under the law you expect.

None of this requires a completely different contract for Brazil, only clauses written with both legal systems in mind, which is usually far cheaper than proving ownership later in a due diligence or a dispute. For the broader picture, see our notes on selling software to Brazilian companies and on governing law, forum and arbitration.

Rafael Parodi Ferraresso

Brazilian lawyer (OAB/SP 434.463), partner at Parodi & Domingues Advogados and LL.M. in U.S. Law from George Mason University

This article provides general information about Brazilian law and is not legal advice. Reading it does not create an attorney-client relationship.

Doing business with a Brazilian company?

Tell us about your matter by email or WhatsApp and we will explain the next steps.

More insights

Tell us about your matter

Send us a message and we will get back to you by email.

You are contacting us as:

By sending this form, you agree to our privacy policy.