Who owns the code for a custom mobile app in Canada? By default, the developer does. Under the Copyright Act, the author of a work is its first owner, and for custom code that is usually the person or firm that wrote it. You own the code outright only when a signed, written assignment transfers the copyright to you. Paying the invoice in full does not do that on its own. This article sets out the default rule, the exceptions, and what owning the app should include, clause by clause.
The short answer: who owns the code for a custom mobile app in Canada
Section 13(1) of the Copyright Act makes the author the first owner of copyright in a work. Computer programs are protected as literary works, so the developer who writes the code is the first owner.
Section 13(3) is the main exception. Where an author creates a work in the course of employment under a contract of service, the employer is the first owner, unless the parties agree otherwise. That exception covers employees. It does not reach independent contractors or agencies, whose work stays with them until they assign it.
Section 13(4) sets the form any transfer must take. An assignment, or a licence of an interest in the copyright, is valid only if it is in writing and signed by the owner or the owner's authorized agent. A verbal agreement, a project brief or a payment receipt does not meet that test.
The practical rule is this: a developer or agency keeps the copyright unless a signed written assignment says otherwise.
This article is general information, not legal advice. Check the current text of the Act on the Justice Laws website, and have a Canadian lawyer review your developer contract before you sign it.
Why paying the invoice does not transfer copyright
Payment and assignment are separate things. You can settle every invoice and still not hold the copyright in the code.
The consequence is practical. You may have paid for an app but lack the legal right to copy, modify or reuse its code without the developer's consent. If the relationship breaks down, you could be negotiating for source code you believed was already yours, with the developer holding the leverage.
The fix sits in the contract. The assignment clause should state that copyright passes to your company, in writing, and is signed by the developer. Settle it before work starts, not after the final invoice.
Employee or contractor: who wrote the code decides ownership
The author's identity decides the answer. Code written by an employee in the course of their job usually belongs to the employer under section 13(3). Code written by a contractor or agency belongs to that contractor until it is assigned.
That means one app can have mixed ownership. If an in-house developer wrote the front end and an agency wrote the back end, you need documentation for both. Ask who wrote what before you sign anything.
When your developer is an employee
Employer ownership applies to work made in the course of employment, and its scope is narrower than many founders assume. Work outside the job description, work done on evenings or weekends for a side project, or work done under a separate arrangement may not transfer automatically.
Do not rely on the default alone. Put an intellectual property and confidentiality clause in every employment contract for technical staff. It should state that work created in the role, and anything relevant to the business, belongs to the company, and that the employee will sign whatever is needed to confirm it.
When your developer is a contractor or agency
Contractors and agencies keep copyright by default. You need a signed written assignment, and nothing else does the job.
A verbal promise that you will own it is not enough. A project brief saying the work is for your business is not enough. A payment receipt is not enough. Each may show what was intended, but none transfers copyright under section 13(4).
What owning the app should actually cover
A signed assignment of the code alone often leaves a business without a working app. You may hold the source files but not the store listing, the back end that stores your users' data, or the admin login for the services the app depends on.
Use this list as a checklist in your contract review. Each item should be named in the contract, with a transfer date and a person responsible for handing it over.
- Source code, in a repository your company controls
- Design files, prototypes, user flows and documentation
- Apple App Store and Google Play accounts, and the app listings under them
- Firebase, Supabase and other cloud or back-end accounts
- Third-party and open-source components, with their licence types
- Any reusable components the developer keeps, and your licence to use them
Source code and the Git repository
The repository is the most important asset. Set it up in your company's organization from day one, with your company as owner and the developer added as a member. Moving a repository later is possible, but it is avoidable work.
The full commit history matters. It supports future development and debugging, and it is what a buyer or investor will ask for in due diligence. This holds whatever the stack, whether React Native, Flutter, Expo, Swift, Kotlin or a Node.js back end. Ask any developer to work this way.
Designs, prototypes and documentation
Design files are often treated as an afterthought. Figma or other design files, the clickable prototype, user flows, API documentation and handover notes all take real time to produce, and all should be covered by the assignment.
The clickable prototype is often the first asset a project produces. If the contract assigns the code but not the prototype, you end up with a working app and no record of the design decisions behind it. For how the design stage works, see our custom mobile app development page. If your brand identity is part of the project, our logo design cost guide for Canada covers what you pay and what you own.
Apple App Store and Google Play accounts
Owning the app listing and owning the developer account are different things. The listing is the app's public page and its version history. The developer account is the login that publishes updates and controls who can make them.
Apple registers developer accounts as either individual or organization accounts. Whether an existing individual account can be changed into an organization account, and how an app moves between accounts, are governed by Apple's current rules, which change. Confirm the position on developer.apple.com before you plan any transfer. The safer course is to register an organization account in your company's name from the start. Apple's organization enrollment asks for a D-U-N-S Number, so check whether your company has one, and how long one takes to obtain, before the build begins.
For Google Play, get the same certainty in writing. Before you sign, ask the developer to confirm which Play Console account will publish the app, who holds the owner role, and how the account and listing will pass to your company at handover.
The same principle applies to your Google Business Profile, which should also sit under an account your company controls. See our Google Business Profile service for setup and verification, and read who owns your Google Business Profile when an agency manages it.
Firebase, Supabase and other cloud accounts
Firebase, Supabase and similar services are where ownership problems often hide. If the developer creates the project under their own Google or GitHub login, the project, the billing and the data can all sit with them.
Set these up correctly from the start. Your company's organization should own the Firebase project or Supabase organization, and the billing account. The developer should be given admin access, not ownership. Keep at least two people in your organization with admin rights, so one departure does not lock you out.
If you are also planning hosting and infrastructure, cloud setup and migration is the right place to start.
Third-party and open-source components
Custom code usually belongs to the client. Libraries and frameworks do not. Open-source packages, SDKs and frameworks keep their own licences, and those licences set the conditions for using them.
Ask the developer for a list of open-source components and their licence types before launch. Most are permissive, but some carry obligations you need to know about, particularly if you plan to distribute the app or keep its code closed.
Agencies often reuse internal tools such as a template, a utility library or an authentication module built for earlier clients. It is reasonable for the developer to keep those. The contract should say so, and give you a licence to use those components inside your app, including after the engagement ends.
A clause checklist for your developer contract
Take these eight points into your contract review. If a clause is missing, ask for it in writing before you sign.
- Assignment wording. The developer assigns copyright in the custom code, designs and documentation to your company, in writing and signed, as section 13(4) requires.
- Transfer trigger. The contract names the event that transfers ownership, such as final payment or delivery of a named version. See the section below.
- Open-source disclosure. The developer lists every third-party and open-source component, with its licence type, before launch.
- Background IP and reusable components. Pre-existing tools are separated from the code written for you, and you receive a licence to use them inside the app.
- Repository and account transfer. The repository, store accounts, cloud projects and admin roles move to your organization, with a date and a named person responsible.
- Warranty of originality. The developer confirms the code is their original work, or properly licensed, and that it does not infringe anyone else's rights.
- Handover on termination. If either party ends the contract, the developer releases the materials listed in the section on switching developers, within a set period.
- Moral rights waiver. Moral rights cannot be assigned in Canada, but they can be waived (section 14.1). Ask counsel to draft a waiver covering the developer and any individual authors.
Moral rights are a point many contracts miss. A copyright assignment does not remove an author's right to be associated with the work, or to object to changes that would harm their reputation. A waiver drafted by a lawyer closes that gap.
When ownership should transfer: milestone, final payment or delivery
The trigger has to be explicit, and there are two common structures. Each suits a different risk.
Transfer on final payment or delivery of the launch version protects the developer, who keeps the rights until the last invoice is settled. The cost falls on the client, who pays for most of the build without holding its rights until the end.
Progressive transfer, with each milestone's deliverables assigned as they are paid for, gives the client rights as the money goes out. The cost falls on the developer, who hands over work that has not yet been paid for in full.
For most projects, we recommend a combination. The client receives a licence to use work in progress from the first milestone, and the assignment takes effect on final payment for the launch version. Write the trigger in those terms. Upon completion is vague and invites argument later.
At Eskore, every project starts with a written scope, a fixed price and a launch date agreed before work begins. That fixes the deliverables and the final payment point before the first line of code, which makes the trigger straightforward to write.
Switching developers mid-project or after launch
Sometimes the relationship ends before launch. The business changes direction, the developer cannot deliver, or the two sides disagree. The same question arises after launch, when you want to move the app to a new team.
The first question is what the developer owns for the work completed so far. A well-drafted contract answers it, and it should define ownership of completed work. On request, the developer then releases the handover materials, in a usable state. Ask for these in writing:
- The repository, with its full commit history
- Documentation, design files and prototypes
- The list of open-source components and their licence types
- The list of accounts, with current admins, and access for you or your next developer
Without these, the next developer has to reverse-engineer the app, which costs time and money. If you hold a signed assignment and these materials, you can take the code to another developer after launch. A fixed-price contract with a written scope makes the handover easier, because both sides can see what has been delivered and what has not.
Ownership in an existing-app takeover
If you are taking over an app another agency built, the chain of title starts with that agency. The code belongs to the agency, or to whoever they assigned it to, until the assignment is proven.
Before new work starts, ask for four things:
- Written proof of assignment from the previous agency, covering the code and the designs
- Transfer of the store listings and developer accounts to your company
- Access to cloud and back-end accounts, with admin roles in your organization
- A code audit, so you know what you are inheriting, including dependencies, licence types and known issues
If the previous agency cannot or will not provide the assignment, do not spend money on the app until you have legal advice. A missing assignment is a serious problem, though not always an unfixable one.
If you are considering a takeover, these questions apply whichever agency you choose, including Eskore. Our mobile app development team can talk through what you would be inheriting.
US law: what changes for American buyers
This is a summary, not a US legal opinion. Speak to a lawyer licensed in the United States before you sign a specific contract.
Under US law, work an employee creates within the scope of employment is generally work made for hire, and the employer owns it. Software written by an independent contractor is generally not work made for hire, unless it falls within narrow statutory categories and a written agreement says so. In practice, a written assignment is still needed.
Canada differs in one respect. Section 13(3) reaches only employees working under a contract of service, so a contractor's copyright stays with the contractor unless it is assigned. The working rule is the same on both sides of the border: get the assignment in writing, and list the accounts and assets you need to run the app. That applies equally if you are building in New York, Austin, Raleigh or Denver.
How Eskore handles code and account ownership
We work from a written scope, a fixed price and a launch date, all agreed before work starts. You own the code and the accounts.
We have offices in Toronto, Thornhill, London and New York, and one team covers software, design, cloud and marketing. For custom software development and mobile apps, ownership belongs in the first conversation, not the last.
Next step: get your ownership terms in writing
Before you sign, ask your developer who owns the code for your custom mobile app, and ask for the answer in writing. Request the clause checklist above and an account setup plan that shows who owns the repository, store accounts and cloud projects. If they cannot give you both, that tells you something useful. Book a free 30-minute scoping call and we will walk through your contract terms and account setup with you.