Who Owns the Software You Paid For? Copyright, Contracts and Code Under Omani Law

Paying for custom software does not, by itself, make you its owner under Omani law. Oman’s Copyright and Neighbouring Rights Law, issued by Royal Decree 65/2008, protects computer programs as works. The economic rights in a work can be transferred only by a written contract that specifies each right, its purpose, its duration and its place. Anything not expressly assigned stays with the author. And the author’s moral rights cannot be transferred at all.

So what you own is decided by the wording of your contract, not by the invoice. A development agreement that says “the client owns the software” without more may transfer less than you think. A project with no written assignment may transfer nothing but a copy and the right to use it.

This article explains the rules and what the contract needs to say. The wider vendor contract — acceptance, support, exit — is covered in how to choose a software partner in Oman.

The short answer

• Software is protected as a work under Article 2, along with databases. No registration is needed.
• The author is a natural person — the individual who creates the work (Article 1). A company can own the rights through a collective work or by assignment, but not by default.
• Assignment must be written and specific — the right, purpose, duration and place — and the author keeps whatever is not expressly assigned (Article 8).
• Buying a copy is not buying the rights (Article 12).
• Moral rights cannot be sold or waived (Article 5).
• Ideas, methods and data are not protected — only their expression (Article 4).

What Omani copyright protects in software

Article 2 lists computer programs and databases, “whether machine-readable or otherwise”, among protected works. Article 3 adds compilations of data that are intellectual creations through the selection and arrangement of their contents.

Article 4 sets the limit. Protection does not extend to mere ideas, procedures and methods of operation, mathematical concepts, principles, discoveries or data.

For a business system, that means three things:

• The code is protected. Source and object code, and arguably the expressive design around it.
• Your business process is not. The approval workflow you designed is an idea or method of operation. Copyright does not stop a competitor building the same workflow from scratch.
• Your data is not protected as data. A database may be protected as a compilation through its structure, but the facts in it are not. Protecting your data is a matter of contract, confidentiality and access control, not copyright.

Protection arises automatically. Article 34 allows the right holder to deposit a copy with the Ministry, which creates a presumption of ownership. It is optional, but it can help if ownership is ever disputed.

Economic rights last for the author’s life plus 70 years (Article 26). For collective works, they last 95 years from first lawful publication (Article 28).

Paying is not owning: the written-contract rule

Article 6 gives the author exclusive economic rights. These include reproducing the work, translating, adapting or transforming it, distributing copies, renting a computer program commercially, and making the work available to the public.

Article 8 then says how those rights move. The author may assign them, or license their exploitation, by a written contract that specifies the right being transferred, the purpose, the duration and the place. The author remains the owner of every right not expressly assigned.

Two further articles close the gaps people rely on:

• Article 12: disposing of the original or a copy does not transfer any economic right. A delivered system on your server is a copy.
• Article 11: rights in software are exercised within the limits of the licence written or attached to the program — including terms shown on screen at installation. The buyer or user must comply with them.

The consequence for a custom build is direct. Suppose your contract says only that you will receive “the system” on payment. You may hold a copy and an implied right to use it. You may not hold the right to modify it, to have another company maintain it, or to sell it to your subsidiaries. Those are separate economic rights, and Article 8 requires them to be named.

Who the author is when a company builds your system

The law defines the author as the natural person who creates the work. That raises the question of how a software company comes to own code its developers wrote.

Collective works. Article 1 defines a collective work as one created by a group of authors under the direction of a natural or legal person, who publishes it in its own name and under its responsibility. The authors’ efforts merge into the work’s overall aim, and individual contributions cannot be separated. Under Article 22, that person owns the moral and economic rights, unless otherwise agreed in writing. Many vendor-built systems fit this description, which is one route by which a vendor comes to hold the rights in the first place.

Joint works. Where contributions can be distinguished, Article 21 makes the co-authors equal holders. None may exercise the rights alone unless agreed in writing.

Employees and freelancers. We did not find a general rule in the Law that vests works made by employees in the employer automatically. Your vendor’s rights over its developers’ and freelancers’ contributions therefore depend on the collective-work rule and on its own written agreements with them.

What follows for you: the vendor can only assign what it holds. Your contract should include a warranty that the vendor holds, or will obtain in writing, the rights from everyone who contributed — staff, freelancers and subcontractors. That is called chain of title, and it is the clause most often missing.

Moral rights: what you can never buy

Article 5 gives the author three moral rights that cannot be lost through time or transferred:

1. the right to be identified as author, in the manner the author chooses;
2. the right to decide on the work’s first publication;
3. the right to prevent any distortion or modification that would harm the author’s honour or reputation.

Any disposal of these rights is “absolutely void”, whether paid for or not.

In practice, moral rights rarely trouble a business system. Routine maintenance and extension of code do not normally harm anyone’s honour or reputation. But the integrity right exists, and attribution notices in code are worth keeping. If you plan to rebrand or publicly republish a system written by named individuals, take advice on how the moral rights interact with your plans.

What the contract needs to say

1. An assignment, in writing, naming each economic right. Reproduction; translation, adaptation and modification; distribution; making available to the public; and any rental or licensing to others. Article 8 requires the rights to be specified.
2. The purpose. Unrestricted business use, including modification by you or any third party you appoint.
3. The duration. The full term of protection.
4. The place. Worldwide, or at least every country where you or your group operate.
5. When it transfers. On creation, on acceptance or on payment. Whichever you choose, make sure you hold enough rights to keep operating if the relationship ends mid-project.
6. Pre-existing components. Vendors reuse their own libraries. Take a perpetual, irrevocable, transferable licence to whatever is embedded in your system and not assigned to you.
7. Third-party and open-source components listed with their licences.
8. Chain of title. A warranty that every contributor’s rights have been secured in writing.
9. Source code and access. A repository you can see from the first week, not a handover at the end.

Points 7 to 9 overlap with the vendor clauses in hiring a software company without handing over your data, which covers the confidentiality side.

Open source: free to use, not free of conditions

Almost every modern system contains open-source components, and that is normally a good thing. But open source comes under licences, and they differ:

• Permissive licences such as MIT, BSD and Apache 2.0 allow use, modification and redistribution with conditions such as keeping copyright and licence notices.
• Copyleft licences such as the GPL require that, if you distribute software derived from the component, you distribute its source under the same licence.
• Network copyleft licences such as the AGPL extend that obligation to software offered to users over a network.

For an internal business system, copyleft rarely bites, because you are not distributing it. It becomes important when you sell or distribute the software, or turn it into a product. The contract should require the vendor to list components and licences. It should also require them not to introduce copyleft components into code you intend to distribute without your agreement.

Code written with AI tools

Developers increasingly use AI coding assistants. Under Omani law the author is a natural person, and the work must show creative character. How that applies to code generated largely by an AI tool has not, as far as we could find, been settled by an Omani court.

Two practical steps reduce the uncertainty:

• Ask the vendor to disclose AI tool use and to warrant the deliverables. The vendor should hold, or have obtained, all rights needed to assign them to you. It should also confirm that the tools’ terms do not claim rights in the output or restrict commercial use.
• Keep the human contribution real. Design, review, integration and testing by identifiable people are what make the system a work of authorship. They are also what make it maintainable.

If ownership is disputed

The Law gives right holders civil and criminal remedies. Courts may award compensation for infringement. As an alternative, the Law lets the court award compensation at amounts set by the executive regulation, capped at OMR 10,000 per infringing act. Most disputes over custom software are not infringement cases, though. They are arguments about what the contract transferred. That is why the contract is where the work is.

---

Frequently asked questions

If I paid for custom software, do I own it in Oman? Not automatically. Under Article 8 of the Copyright Law, economic rights pass only by a written contract specifying the right, purpose, duration and place. Without that, you may hold a copy and a right to use it, but not the rights to modify, license or sell it.

Does the software company own code its developers wrote? Often yes, as a collective work created under its direction and published in its name (Article 22), unless agreed otherwise in writing. It can then assign those rights to you, but only if it secured them from all its contributors.

Can I buy the moral rights in software? No. Moral rights — attribution, first publication, and protection against harmful distortion — cannot be transferred, and any disposal of them is void. In practice they rarely affect routine maintenance of a business system.

Is my business process protected by copyright? No. Article 4 excludes mere ideas, procedures, methods of operation and data. Copyright protects the code that implements your process, not the process itself. Protect business methods through confidentiality and contracts.

Do I need to register software in Oman to protect it? No. Protection arises automatically. Article 34 allows you to deposit a copy with the Ministry, which creates a presumption of ownership that can help in a dispute.

Who owns code written with an AI assistant? Omani law defines the author as a natural person, and we found no Omani court decision on largely AI-generated code. Ask your vendor to disclose AI tool use and warrant that it can assign full rights in the deliverables.

---

This article states the position under the Copyright and Neighbouring Rights Law issued by Royal Decree 65/2008 as in force on 21 October 2026, the date of publication. It is not legal advice. Have any assignment or development contract reviewed by a qualified adviser before signing.

Sources: Royal Decree 65/2008 — Copyright and Neighbouring Rights Law (Arabic text) · WIPO Lex — Oman Law on Copyright and Neighboring Rights · Open Source Initiative — approved licences · GNU — the GPL and AGPL

Commissioning a system and want to own it properly? ZAWAT builds custom software, and we are glad to go through ownership, repository access and handover terms with you before anything is signed. Book a call.