Buyer guide
Who owns the code when a freelancer builds my app?
In short
Paying for software does not by itself settle who owns it. In the US, work by an employee is owned by the employer, but work by a contractor is owned by the contractor unless it fits narrow categories with signed wording or the rights are assigned in writing. Put ownership in the contract and have a lawyer in your country check it.
Who is this guide for?
Business owners who have hired, or are about to hire, a freelancer or agency to build an app and want to know what to put in writing so that they own what they paid for.
Payment and ownership are separate questions
Many owners assume that paying for an app means owning its code. In copyright law the starting point is different: the person who creates a work is normally its author. GOV.UK states that copyright protection arises automatically, with no application or fee.
So unless something moves ownership to you, the author may keep it, even if you paid for the work. What moves it is the contract.
Employees and contractors are treated differently
The US Copyright Office explains that a work is made for hire in two situations. One is when an employee creates it as part of regular duties. The other is when a specially ordered or commissioned work falls in one of nine listed categories and the parties sign a written agreement saying it is a work made for hire. If a work fails any of those requirements, it is not a work made for hire.
A freelancer is usually a contractor, and a software application does not obviously fit those nine categories. That is why a contract for a freelancer normally also includes a written transfer of the rights, rather than relying on work-made-for-hire wording alone.
Who counts as an employee
The Copyright Office says the question is decided by the facts of the relationship under general agency law, and lists factors such as who controls when and how the work is done, how the person is paid, whether benefits and taxes are handled and whether the person runs their own business.
A job title or a clause saying contractor does not settle it. The rules differ by country, so this is one to put to a lawyer.
What the contract should say
A good contract says who owns the code and the other deliverables once they are paid for, when that ownership passes to you, and what happens to code the developer brought in from earlier work or from open-source libraries.
It should also say what you receive at the end, such as the source code and the build instructions, and that the accounts, domain and store listings are yours.
Open-source parts and reused code
Almost every app contains open-source libraries, and each has its own licence. Ask for a list of the libraries used and their licences, so you know what conditions come with them.
A developer may also reuse their own earlier components. A fair contract lets them keep general know-how while giving you a licence, or ownership, of what is in your product. Ask for it in writing.
A note on what this page is
This page explains what to ask about. It is not legal advice, and copyright and contract rules differ by country. Have a lawyer in your country check your contract before you sign it.
How do the options compare?
| Situation | Usual starting point | What to do |
|---|---|---|
| Your own employee, within their duties | The employer is the owner of work made for hire (US rule) | Check local law and the employment contract |
| A freelancer, no clear written terms | The creator keeps the rights | Get a signed agreement before work continues |
| A freelancer, with signed work-made-for-hire wording | Applies only to the listed categories in US law | Add a written assignment of rights as well |
| Open-source libraries inside the app | Each library keeps its own licence | Ask for a list of libraries and licences |
What should I check before I sign?
- The contract names who owns the code and when ownership passes.
- It does not rely only on work-made-for-hire wording.
- There is a written assignment or licence for what you paid for.
- Pre-existing code and open-source parts are listed with their licences.
- You will receive the source code and build instructions at the end.
- The accounts, domain and store listings are in your name.
- Both parties have signed, and you hold a copy.
- A lawyer in your country has checked the contract.
How pricing works
I quote in writing after a short discovery call, against a written scope. Building an app from scratch? The app cost calculator gives a first range in two minutes.
What else do people ask?
I paid in full. Do I own the app?
Not necessarily. Payment alone does not move copyright. Look at what your contract says about ownership, and if it is silent, get a signed agreement and ask a lawyer in your country to review it.
Is a work made for hire clause enough?
In US law it applies only to defined categories, with signed wording. Many contracts add a written assignment as a back-up. Ask a lawyer which applies where you are.
Can the developer reuse my code for another client?
That depends on the contract. Say clearly what is yours, what is general know-how and what may be reused.
Does this work the same in every country?
No. Rules on authorship, employees and transfers differ. Have a lawyer in your country check your case.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.