TRW & Co · Technology & IP
Software Licensing in the UAE
Software licensing in the UAE rests on the 2021 copyright decree-law and, since 1 June 2026, a new Civil Transactions Law that lets courts revisit agreed compensation. This guide explains how vendors and buyers should structure licences, protect code ownership, handle audits, VAT and data rules, and choose a forum that works when things go wrong.
Key pointUnder Article 340 of the 2025 Civil Transactions Law, in force from 1 June 2026, UAE courts can reduce or increase agreed compensation and no cap protects fraud or gross negligence, so software liability caps need to be drafted as proportionate bargains rather than relied on as absolute limits.
At a glance
Code is copyright
Federal Decree-Law No. 38 of 2021 protects computer programs and databases on creation; Ministry registration is optional but useful evidence.
Assignments must be written
Economic rights in software must be transferred in writing and are read narrowly, so contractor code needs an express assignment.
New civil code applies
Federal Decree-Law No. 25 of 2025 took effect on 1 June 2026; Article 340 lets courts review agreed compensation clauses.
VAT on licence fees
VAT applies to software supplied in the UAE, and UAE buyers of overseas licences generally self-account under the reverse charge mechanism.
Choice of forum matters
Onshore courts work in Arabic; DIFC and ADGM courts and arbitration under DIAC rules are common alternatives for technology contracts.
Swipe or scroll →
What software licensing in the UAE covers
Software licensing in the UAE is the law and practice of granting, buying and enforcing rights to use computer programs, from on-premise enterprise systems and embedded code to subscription software, mobile apps and open-source components. It matters to vendors selling into the region, resellers and system integrators, UAE companies and government entities buying technology, and developers building products in Dubai, Abu Dhabi and the free zones.
A licence is a permission, not a sale. The vendor keeps ownership of the code and the customer receives defined rights to install, access, modify or distribute it. Almost every commercial dispute in this area comes back to the scope of that permission: how many users, which entities, which territory, what modifications and for how long.
It becomes a legal question at procurement, at renewal, when a vendor audits usage, when a customer wants to exit or migrate, when code is built by contractors, and when a product is distributed through partners. Each stage has UAE-specific traps around copyright ownership, contract enforcement, tax and data.
The legal framework for software
Copyright protects the code
Computer programs, applications and databases are protected as works under Federal Decree-Law No. 38 of 2021 on Copyrights and Neighbouring Rights, implemented by Cabinet Decision No. 47 of 2022. Protection arises on creation and does not depend on registration, although registering a program with the Ministry of Economy and Tourism creates useful evidence of authorship and date, which helps in enforcement.
The copyright law treats economic rights, which can be licensed or assigned, separately from moral rights, which stay with the author. Any assignment or licence of economic rights should be in writing and should specify each right, its purpose, duration and territory. Vague grants are read narrowly, which usually favours the owner.
Patents play a smaller role. Federal Law No. 11 of 2021 on industrial property rights governs patents, and software as such is generally protected by copyright and confidentiality rather than patents, though technical inventions implemented in software may qualify. Our page on copyright and content goes deeper.
Contract law and the new Civil Transactions Law
Onshore licence agreements are interpreted under the civil code. Federal Decree-Law No. 25 of 2025 on Civil Transactions replaced the 1985 code with effect from 1 June 2026. Article 340 lets parties agree compensation in advance, but the court can reduce it if excessive or if the obligation was partly performed, and can award more where the debtor acted with fraud or gross negligence. Clauses that try to exclude this control are void.
That matters for software contracts, which rely on liability caps, service credits and liquidated damages. Under UAE law these are reviewable, so a cap is a strong negotiating anchor rather than a guaranteed ceiling, and it will not protect a party shown to have acted fraudulently or with gross negligence.
Data, cybercrime, e-signatures and competition
Licensed software that processes personal data engages the federal Personal Data Protection Law, Federal Decree-Law No. 45 of 2021, in force since 2 January 2022, and in the financial free zones the DIFC Data Protection Law and the ADGM regime overseen by its Office of Data Protection. Health, financial and government data carry additional localisation rules. The UAE Government portal summarises these laws, together with Federal Decree-Law No. 34 of 2021 on combating rumours and cybercrimes, which criminalises unauthorised access and circumvention of protection measures.
Electronic contracting is valid under the federal law on electronic transactions and trust services, so click-through and e-signed licences are generally enforceable if formed properly. Exclusive and restrictive licensing terms are also tested against Federal Decree-Law No. 36 of 2023 regulating competition, whose implementing rules and thresholds were updated in 2025 and 2026.
Choosing a licence model
The commercial model drives the legal risk. The table below compares the models we see most often in software licensing in the UAE.
| Model | What the customer gets | Main legal issues | Typical buyer |
|---|---|---|---|
| Perpetual on-premise licence | Indefinite right to install and use a version, with separate support and maintenance | Scope of use, audit rights, support end-of-life, source code escrow | Banks, government entities, large enterprises |
| Term or subscription licence | Right to use for a fixed period, often with updates included | Renewal pricing, true-ups, exit and data return | Mid-sized and large companies |
| Software as a service | Access to hosted software rather than a copy | Service levels, data location, security, outsourcing rules | Most sectors; regulated sectors need extra controls |
| OEM and embedded licence | Right to integrate code into the licensee's product and distribute it | Sublicensing chain, royalties, open-source compliance, warranties | Device makers, platform builders |
| Reseller and distribution | Right to market and sublicense to end users in a territory | Exclusivity, competition law, commercial agency risk, end-user terms | System integrators and value-added resellers |
Software as a service raises its own questions on hosting and outsourcing, covered in our pages on SaaS and technology contracts and cloud and outsourcing.
Clauses that decide most disputes
Whatever the model, a handful of clauses decide most disputes over software licensing in the UAE.
Grant and scope. Define the licensed entities (including affiliates and free-zone group companies), users or metrics, permitted purposes, environments, territory and any right to modify or create derivative works. Under the copyright law, rights not expressly granted are retained by the owner.
Ownership of customisations. If a vendor or contractor builds configurations, integrations or new modules, state who owns them and include an express written assignment where the customer is meant to own them. Without one, the developer may keep the copyright.
Audit and true-up. Vendors increasingly audit enterprise customers. Agree notice periods, frequency, who conducts the audit, confidentiality, how licence shortfalls are priced and how disputes over the results are resolved.
Liability, warranties and service credits. Draft caps, exclusions and service credits in the knowledge that a UAE court can review agreed compensation. Pair caps with clear performance obligations and remedies so the bargain looks proportionate.
Termination and exit. Set out what happens to the licence, data, transition assistance and escrow on termination or insolvency. For critical systems, a source code escrow with clear release triggers is essential.
Governing law and forum. Choose between UAE onshore law and courts, DIFC or ADGM law and courts, or arbitration, for example under the Dubai International Arbitration Centre rules. Onshore proceedings are conducted in Arabic, so English-language contracts will need certified translation if they end up in court.
In UAE software deals, a liability cap is a negotiating anchor, not a guaranteed ceiling: the court can revisit agreed compensation, and no cap survives fraud or gross negligence.
Selling to government and regulated buyers
Government and government-related entities are among the largest buyers, and they change the shape of software licensing in the UAE. Federal and emirate-level procurement rules, tender conditions and standard government contract forms usually take priority over the vendor's own paper. Expect UAE governing law, onshore courts or a specified arbitration centre, extensive termination for convenience rights and limited room to negotiate liability.
Government buyers also apply national and emirate information security standards, often require hosting in the UAE and may ask for Arabic versions of key documents. Bid teams should review tender terms with counsel before pricing, because concessions on liability, audit or escrow are hard to recover after award.
Regulated private buyers bring their own overlays. Banks and insurers licensed by the Central Bank must manage material outsourcing and technology risk under its rules, healthcare providers must keep health data in the UAE unless an exemption applies, and listed companies face disclosure and governance expectations. In each case software licensing in the UAE becomes a three-way conversation between vendor, customer and regulator, and the licence should give the customer the audit, access and exit rights its regulator expects.
Tax treatment of licence fees
Tax is part of the commercial negotiation. VAT applies to software licences and services supplied in the UAE at the standard rate, and UAE businesses buying from overseas vendors generally account for VAT under the reverse charge mechanism. Pricing clauses should say whether fees are exclusive of VAT and who bears it. The Federal Tax Authority publishes the relevant guides.
The UAE does not currently levy withholding tax on royalties paid abroad, which keeps cross-border licensing straightforward. UAE corporate tax applies to licence income earned by UAE vendors, and free-zone businesses should check whether their licensing income is qualifying income before relying on the free-zone regime. See our pages on VAT and corporate tax.
Negotiating an enterprise licence: the process
- Map the requirement. Identify the business process, users, entities, data types and integrations, and whether the software is critical enough to need escrow or step-in rights.
- Check regulatory overlays. Confirm whether sector rules apply, such as Central Bank outsourcing rules, health data localisation or government information security standards, and whether data can leave the UAE.
- Review the vendor's paper. Mark up the master agreement, order form, end-user terms and any policies incorporated by reference, which often contain the most important restrictions.
- Negotiate scope, price and audit together. Licence metrics, discounts, true-up pricing and audit methodology are linked; agreeing one without the others creates future exposure.
- Settle liability and exit. Agree caps, carve-outs, service credits, termination rights, data return and transition support, and set up escrow where needed.
- Execute and record. Sign through a valid authority and method, keep the full contract set together, and register entitlements in a licence management tool.
- Govern the relationship. Track usage against entitlements, prepare for renewals early and keep a file of vendor representations relied upon.
Enforcing software rights
When software is copied, used beyond licence or reverse-engineered, rights holders have civil, criminal and administrative options. Copyright infringement can be pursued through civil claims for damages and injunctions, criminal complaints under the copyright and cybercrime laws, and administrative action by economic authorities against commercial piracy. Interim measures such as precautionary attachment and evidence preservation orders may be available before the main claim.
Most licence disputes, however, are contractual: unpaid fees, audit shortfalls, overuse by affiliates or breach of confidentiality. These go to the forum in the contract. Our page on trade secrets covers protection of source code and know-how where copyright is not enough.
Before suing for infringement, secure evidence of ownership and use: the source code history, authorship records, any Ministry registration, the licence chain and screenshots or logs showing unlicensed use. UAE courts rely heavily on documents and court-appointed experts, so a clean evidential file is worth more than a forceful demand letter.
Risks and common mistakes
Assuming contractors' code belongs to you
Freelancers, outsourced development houses and even group companies often write code for a business without a written assignment of copyright. Under the copyright law, economic rights must be transferred in writing and the grant is read narrowly, so the customer may hold only an implied permission to use what it paid for. That gap surfaces at due diligence, during a funding round or when the developer reuses the code for a competitor. Put written assignments and moral rights waivers, to the extent permitted, in every development contract.
Ignoring open-source licence obligations
Most products contain open-source components whose licences impose conditions, from attribution notices to obligations to publish source code when software is distributed. Developers rarely track them carefully. A distribution or OEM deal, a sale of the business or a dispute with a competitor can expose non-compliance. Maintain a software bill of materials, review copyleft components before release, and include open-source warranties and disclosure schedules in licence and acquisition agreements.
Treating a reseller as an agent
Software distribution through local resellers is common. Where a vendor appoints a mainland reseller under terms that look like a registered commercial agency, the reseller may later claim the protections that UAE commercial agency law gives registered agents, including on termination. Draft reseller agreements as distribution or referral arrangements, avoid registration unless intended, and set clear termination and transition terms. Our page on distribution and agency agreements explains the line.
Signing audit clauses without limits
Unlimited audit rights let a vendor arrive with little notice, demand broad system access and price shortfalls at list rates. Customers with complex affiliate structures across mainland and free-zone entities are most exposed because licence metrics often count entities differently. Negotiate annual limits, notice, independent auditors, confidentiality, a right to dispute findings and pricing for shortfalls at contracted rates. Run your own internal compliance review before renewals.
Overlooking data and export control rules
Licensed software that sends telemetry or customer data abroad may breach data protection or sector localisation rules. Software with encryption or dual-use features may also be subject to foreign export controls, particularly US rules, when re-exported from the UAE. Check where data flows, whether sector regulators must approve outsourcing, and whether the vendor's export classification restricts onward supply. Our page on sanctions and export controls covers the second point.
The cross-border angle
Software licensing in the UAE is usually cross-border by design. Vendors license from the US, Europe or Asia into UAE entities, and UAE developers license out to the GCC and beyond.
United Kingdom and the financial free zones. Many enterprise licences choose English law. DIFC and ADGM courts apply common-law principles that international vendors find familiar, and a DIFC or ADGM forum can be chosen even by onshore parties in the right circumstances.
India and Bangladesh. Development work is often outsourced to teams in India and Bangladesh. The development agreement, IP assignment and confidentiality terms must work under both the developer's local law and UAE law. TRW & Co's offices in Dhaka, Chattogram and Sylhet help with this structuring.
Saudi Arabia and the GCC. Licensing into Saudi Arabia brings its own data, cybersecurity and government procurement rules, and Saudi customers increasingly ask for local hosting. A UAE licence template rarely works there without adjustment.
China and Singapore. Software from China may raise questions under foreign sanctions and export regimes for customers with US exposure, while Singapore is often the Asia-Pacific licensing hub for groups also active in the UAE.
How TRW & Co helps with software licensing in the UAE
We advise vendors, resellers and enterprise buyers on drafting, negotiation, compliance and disputes. Where representation before UAE onshore courts or the DIFC/ADGM Courts is required, we work alongside locally licensed advocates and registered practitioners.
Vendor templates
We build UAE-ready licence, subscription and reseller templates that reflect the copyright law, the new civil code and VAT, with fallback positions for negotiation.
Enterprise procurement
We review and negotiate vendor paper for buyers, focusing on scope, audit, liability, exit and regulatory overlays for banks, healthcare and government-linked entities.
IP ownership and open source
We audit ownership of code, put assignments in place and review open-source compliance before funding rounds, distribution deals or sales. See IP licensing.
Audits and disputes
We manage vendor audits, challenge shortfall claims and coordinate infringement and contract disputes with local counsel and technical experts.
Software deals often sit inside broader technology transactions. Explore our practices or contact us to discuss a licence.
Checklist for decision-makers
- Do we hold written assignments for all code built by employees, contractors and vendors?
- Does each licence define entities, users, territory and permitted modifications clearly?
- Are our liability caps and service credits drafted to withstand review under Article 340?
- Have we limited audit rights and checked our own usage before renewal?
- Do we know where licensed software sends data, and is that permitted for our sector?
- Is critical software protected by escrow and a tested exit plan?
- Are VAT, reverse charge and corporate tax treatment reflected in pricing?
- Have we chosen governing law and forum deliberately for software licensing in the UAE?
A short review against this list before signing or renewing usually saves far more than it costs.
Frequently asked questions
01Is software protected by copyright in the UAE?
Yes. Federal Decree-Law No. 38 of 2021 on Copyrights and Neighbouring Rights protects computer programs, applications and databases as works. Protection arises automatically when the work is created and does not depend on registration. Registering software with the Ministry of Economy and Tourism is optional but provides useful evidence of authorship and date if you later need to enforce. Patents play a smaller role, as software as such is generally protected by copyright and confidentiality rather than patents.
02Who owns code written by a contractor?
Unless there is a written assignment, the contractor may keep the copyright and the client may hold only a permission to use the code. The copyright law requires transfers of economic rights to be in writing and specific, and grants are read narrowly. Every development, outsourcing and freelance contract should contain an express assignment of all economic rights in the deliverables, a waiver or consent on moral rights to the extent permitted, and obligations to deliver source code and documentation.
03Are limitation of liability clauses enforceable?
They are generally respected but not absolute. Under Article 340 of the 2025 Civil Transactions Law, effective from 1 June 2026, a court may reduce agreed compensation if it is excessive or the obligation was partly performed, and may award more than the agreed amount where the debtor acted with fraud or gross negligence. Agreements excluding this control are void. Draft caps and service credits as proportionate commercial bargains, and consider DIFC, ADGM or arbitration forums where appropriate.
04Do we pay VAT on software licences from overseas vendors?
Usually yes, through the reverse charge. VAT applies to software licences and related services supplied in the UAE, and a VAT-registered UAE business receiving services from an overseas supplier generally accounts for the VAT itself rather than paying it to the vendor. Licence agreements should state whether fees exclude VAT. The UAE does not currently levy withholding tax on royalties paid abroad, which simplifies cross-border pricing.
05Can a software vendor audit our usage?
Only if the licence allows it, which most enterprise licences do. The terms decide notice, frequency, scope, who performs the audit and how shortfalls are priced. Customers should negotiate limits on frequency, reasonable notice, independent auditors, confidentiality, a right to challenge findings and pricing at contracted rather than list rates. Group structures spanning mainland and free-zone entities need particular care, because licence metrics may count entities in ways that differ from the corporate structure.
06Which court will hear a software licence dispute?
The one chosen in the contract, if the clause is valid. Options include the onshore UAE courts, the DIFC or ADGM Courts, or arbitration, for example under DIAC rules. Onshore proceedings are in Arabic and rely heavily on documents and court-appointed experts. DIFC and ADGM Courts operate in English under common-law procedure. If there is no clear clause, the onshore courts will usually have jurisdiction over a UAE defendant.
07Do click-through and electronic licences bind customers?
Generally yes. UAE law recognises electronic transactions and signatures, so click-through, browse-wrap and e-signed licences can be enforceable if the user had a fair opportunity to see the terms and clearly accepted them. For enterprise customers, a signed master agreement is still preferable, and consumer-facing terms must also comply with consumer protection rules. Keep records showing which version of the terms each customer accepted and when.
Sources and official materials
- Intellectual Property Legislations – Ministry of Economy and Tourism — Copyright decree-law, implementing regulation and industrial property law
- Regulation of Competition Legislations – Ministry of Economy and Tourism — Competition decree-law, thresholds and implementing rules
- Data protection laws – UAE Government portal — PDPL, cybercrime and e-transactions laws
- Federal Tax Authority — VAT and corporate tax guidance
- Telecommunications and Digital Government Regulatory Authority — Digital government and ICT regulation
- Dubai International Arbitration Centre — Arbitration rules for commercial and technology disputes
- ADGM Office of Data Protection — Data protection regime in Abu Dhabi Global Market
General information only, current as at 27 October 2026. It is not legal advice and does not create a lawyer–client relationship. UAE law differs between the onshore jurisdiction, the DIFC, ADGM and the free zones, and changes frequently; check current official sources and take advice on the facts of your matter.
