In an outsourcing contract, IP ownership should be settled in writing before work starts: an NDA for confidentiality, an assignment clause transferring code and design to you after final payment, and a list of third-party and open-source parts you only license. Keep the repository, domain and hosting in your name from day 1. This is not legal advice.
Key Takeaways
- Copyright in code and design generally starts with whoever creates it, so ownership must be transferred in writing.
- An NDA protects confidential information; it does not by itself transfer ownership of the work.
- An assignment clause transfers rights in the custom work, usually on final payment.
- Themes, plugins, libraries and fonts are licensed, not owned; the contract should list them.
- Control of the repository, domain and hosting matters as much as the words in the contract.
Why Does Outsourcing Contract IP Ownership Matter?
When you outsource a website or app, you are paying someone else to create code, designs and sometimes content. WIPO describes copyright as the rights creators have over their works, and it lists computer programs among the works commonly protected. In many countries, the creator holds those rights by default unless an agreement transfers them. Without clear terms, you may have paid for a website you cannot freely change, move or resell.
We are web developers, not lawyers. This guide explains the common clauses in plain English so you can discuss them with your lawyer. Laws differ by country, so take legal advice on the final wording.
Which Clauses Should Your Contract Include?
| Clause | Plain-English meaning | Example wording idea |
|---|---|---|
| Confidentiality (NDA) | The developer keeps your business information secret | "Supplier will not disclose Client's confidential information to anyone" |
| Assignment of rights | Ownership of custom code and design passes to you | "On final payment, Supplier assigns all rights in the Deliverables to Client" |
| Third-party components | Licensed parts stay under their own licences | "Third-party and open-source components are listed in Schedule B" |
| Supplier's pre-existing tools | The developer may reuse its own general tools, licensed to you | "Supplier grants Client a perpetual licence to use pre-existing tools in the Deliverables" |
| Moral rights and credits | No credits or claims to the work unless agreed | "Supplier will not add credits or links without Client's consent" |
| Handover | What you receive at the end | "Supplier delivers source code, database, documentation and credentials" |
The wording ideas show the intent only. Have a lawyer draft the actual clauses for your jurisdiction.
Is an NDA Enough?
No. A non-disclosure agreement stops the developer sharing your information, such as your business plans, customer data or unreleased designs. It does not usually transfer ownership of what they build. You need both: an NDA from the first conversation in which you share sensitive material, and an assignment or ownership clause in the main contract.
What About Open-Source and Third-Party Parts?
Almost every website uses parts the developer did not write: WordPress itself, themes, plugins, JavaScript libraries, fonts and icons. These are licensed, not owned. Some open-source licences require you to keep notices or share changes in certain cases; paid themes and plugins usually allow use on a set number of sites. Ask for a list of every significant component with its licence, and make sure paid licences are bought in your name.
Why Is Control as Important as the Contract?
A perfect clause helps little if the developer holds the keys. From day one, keep these in your own name and add the developer as a user:
- the code repository, such as a GitHub or GitLab organisation you own
- the domain name, registered with your details
- hosting and server accounts, billed to you
- admin logins, analytics, Search Console and app store accounts
Our guide on who owns your website covers each account in detail.
What If a Developer Refuses to Hand Over Code?
Prevention is far easier than cure. If you control the repository and hosting, the code is already yours to use. If not, ask in writing with reference to the contract and payments made, request the repository transfer or a full backup, and seek legal advice for serious disputes. Milestone payments tied to delivered code reduce how much is at stake at any point.
What Are Our Own Terms?
Our standard terms keep things simple: we sign an NDA before receiving confidential material, the domain and hosting are registered in the client's name, the client owns the custom code and design after final payment, third-party licences are bought in the client's name and listed at handover, and we add no credits without permission. Projects start from Rs 40,500 for websites and Rs 360,000 for web applications. See our contact page, our website contract checklist and the guide to hiring Pakistani developers.
Frequently Asked Questions
How We Researched This Guide
Copyright points follow WIPO's overview, checked 29 October 2026; account control follows ICANN and Google help pages. The clause table gives plain-English intent and wording ideas only and is not legal advice. Our own terms are approved business facts. Prices are our own published packages.
Sources
- WIPO — Copyright (rights of creators, includes computer programs)
- ICANN — Registrants' benefits and responsibilities
- WordPress.org — Roles and capabilities
- Google Search Console Help — Manage owners, users and permissions
- Google Analytics Help — Add, edit and delete users
Disclosure: Kamboh Associates sells the web development services discussed here. Other providers' prices are quoted from their own public pages on the dates shown and may have changed. We correct errors as soon as they are reported. First published ; last reviewed .
Keep Reading
Want clear ownership terms from day one?
Send us a short description of your project and we'll reply within one business day with a written scope, fixed price and timeline.