Your UAE developer contract probably doesn’t transfer the IP you think it does — the 7 steps I use to fix it

Most UAE employers discover their IP problem at exactly the wrong moment: during due diligence, when an acquirer’s counsel asks to see the chain of title for the codebase. That is when someone opens the employment contracts and finds a single sentence saying the company owns “all work product” — with no definition, no assignment language, no Arabic version, and no coverage at all for the three contractors who wrote the payment module.

The fix is cheap if you do it at hiring time and expensive if you do it later, because after the fact you need signatures from people who no longer work for you and who now have leverage. Here is the seven-step sequence I run with employers building engineering teams in the UAE.

One caveat before we start, and it is not a formality: this is an operational guide written from hiring practice, not legal advice. The wording that ends up in your contract should be reviewed by counsel qualified in the relevant UAE jurisdiction.

Step 1: Identify which legal regime actually governs your entity

This is the step people skip, and it invalidates everything downstream. The UAE is not one contractual environment. It is at least three for these purposes.

Mainland UAE operates under a civil-law system, with Arabic as the language of the courts and federal legislation governing employment and intellectual property.

DIFC (Dubai International Financial Centre) is a financial free zone with its own common-law-based legal framework and its own courts. ADGM (Abu Dhabi Global Market) is likewise a common-law jurisdiction with its own courts and a framework closely aligned with English law.

Federal intellectual property legislation applies across the UAE, but the employment relationship, the rules of contractual interpretation and — critically — the forum that will hear a dispute differ substantially. A contract drafted for a DIFC entity and reused verbatim for a mainland LLC is not a time-saver; it is an unquantified risk.

Write down, in one line, which entity employs the developer and which courts would hear a dispute. Everything else follows from that answer.

Step 2: Use an express written assignment — never rely on implication

In several common-law jurisdictions, employers benefit from a statutory presumption that work created by an employee in the course of employment belongs to the employer. Many founders arriving in the UAE assume the same presumption travels with them. It does not travel reliably.

The dependable approach is to state the transfer expressly. A workable structure covers four things:

• Present assignment of future rights. Language that assigns rights as they come into existence, rather than promising to assign later. A promise to assign requires a further act; a present assignment does not.
• A definition of the covered work. Software, source code, documentation, designs, databases, models, prompts and configuration — spelled out, not left to “work product”.
• Scope tied to employment duties. Works created in the course of employment or using company resources. Attempts to claim everything a person creates during their private time tend to be both unpopular and fragile.
• A further-assurances obligation. The employee agrees to sign any additional documents needed to perfect or register the rights. This is the clause that saves you during due diligence.

Step 3: Draft in Arabic where a mainland court could hear the dispute

Arabic is the language of the UAE courts. Where a dispute involving a mainland entity reaches those courts, documents will be considered in Arabic, and a translation prepared under litigation pressure is not where you want your assignment clause to be tested for the first time.

Standard practice is a bilingual contract — Arabic and English in parallel columns — with an explicit clause stating which language prevails in the event of inconsistency. For mainland entities, expect Arabic to prevail.

The practical failure mode here is subtle. Companies do produce bilingual contracts, but the Arabic version is often a machine translation of an English template drafted for a different legal system. Terms of art do not survive that process. Have the Arabic reviewed by counsel, not by a translation vendor.

For DIFC and ADGM entities, English-language contracts are the norm before those courts, and the Arabic requirement falls away — another reason Step 1 comes first.

Step 4: Close the contractor and offshore freelancer gap

This is where the real exposure sits, and it is almost universal in early-stage teams. A contractor is not an employee. There is no employment relationship to hang an ownership argument on. If the services agreement does not assign the IP, the contractor may well retain rights in what they built — regardless of the fact that you paid the invoice.

Paying for work buys you the work. It does not automatically buy you the copyright in it. That distinction has ended more than one acquisition conversation.

Three practical safeguards, in order of usefulness:

• Assignment in the services agreement itself, in the same form as the employee version, including further assurances. Do not rely on a purchase order or an email thread.
• Payment milestones tied to delivery and assignment. Final payment on acceptance and on signature of the assignment acknowledgement. Leverage before payment is worth more than a claim after it.
• Repository control from day one. The contractor works in your repository under your account, not in theirs with a hand-off at the end. This is an operational control, not a legal one, and it is the most reliable of the three.

For offshore contractors, be realistic about enforcement. A judgment obtained in the UAE against a developer with no assets in the UAE has limited practical value. This is why the operational controls matter more than the forum selection clause.

Step 5: Handle moral rights separately from economic rights

Copyright splits into economic rights — the right to copy, distribute, modify, commercialise — and moral rights, which typically include the right to be identified as the author and the right to object to derogatory treatment of the work.

Economic rights are assignable. Moral rights, in the UAE as in most civil-law systems, are treated as personal to the author and are not assignable in the same way. A clause that purports to assign moral rights outright is likely to be ineffective on that point.

What works instead is a combination: an acknowledgement that the employer may modify, adapt and distribute the work without attribution, together with a consent to acts that would otherwise engage moral rights, drafted to the extent permitted by applicable law.

For most software teams this is a low-severity issue in practice — few developers assert moral rights over a microservice. It becomes material where the work is publicly attributed, where a developer’s name is embedded in an open-source release, or where a departing engineer objects to how their work was subsequently changed.

Step 6: Carve out pre-existing work and open-source components

An assignment clause that promises the employer owns “all” delivered code is a clause the developer cannot honour, because no modern codebase is entirely original.

Two carve-outs make the assignment deliverable and therefore enforceable:

Background IP. Tools, libraries and frameworks the developer created before joining, or created outside the scope of their employment. The right structure is not an assignment but a broad, perpetual, royalty-free licence to the employer for anything the developer incorporates into company work. Ask for a written schedule of background IP at signing — the act of asking surfaces problems early.

Open-source components. The developer warrants that third-party components are used in compliance with their licences and disclosed in a dependency manifest. This matters commercially: copyleft obligations attached to a component in your core product are a diligence finding that affects valuation, not merely a legal footnote. Our colleagues at HireDeveloper.sg have written on how Singapore acquirers treat the same issue during technical due diligence.

Step 7: Enforce the assignment at offboarding

An assignment clause that is never operationalised at exit is a clause you will be reconstructing under pressure later. Four items belong in the offboarding checklist:

• Signed acknowledgement of assignment at exit, confirming all work created during employment has been assigned and that nothing has been retained. This is the single most useful document in later diligence.
• Repository and cloud access revocation, including personal forks, personal access tokens and any accounts created against a personal email address.
• Return or deletion certification for local copies of source code, with a specific statement rather than a generic company-property clause.
• Confirmation of the further-assurances obligation surviving termination, so you can obtain signatures on registration documents after the person has left.

Run this checklist for contractors as well. Contractor offboarding is routinely informal — the invoice is paid and the relationship simply ends — which is precisely why contractor-authored code is where the gaps concentrate.

The three mistakes that come up most often

• Reusing a US template unchanged. Work-for-hire language drafted for US copyright law does not map onto the UAE framework, and the clause that does the heavy lifting in the original may do nothing here.
• Treating the Arabic version as a translation task. For mainland entities, the Arabic text is the operative one before the courts. It deserves legal review, not a vendor turnaround.
• Assuming the invoice transferred the rights. The most expensive assumption in the list, and the one that surfaces exclusively during due diligence, when the leverage has moved to the other side.

If you are building a distributed engineering team across the region, the same analysis has to be repeated per jurisdiction — the structure that works for a Dubai mainland LLC is not the one that works for a Singapore entity or a Japanese subsidiary. Our teams at HireDeveloper.sg and JapanDev cover the equivalent employer obligations in Singapore and Japan, where the tax and equity mechanics differ sharply from the UAE.

For the hiring side of the process, our guide to building an engineering team in Dubai covers sourcing, assessment and compensation structuring.

Frequently asked questions