Software dev template · UAE · Pro
Software development agreement template for the UAE
In short
The UAE variant of the software development agreement uses AED by default, refers to the PDPL for any personal data the developer processes, and is governed by the law of your chosen emirate with the onshore courts, DIFC Courts or DIAC arbitration.
Pro Pro template: USD 5 for 30 days. The outline and explanations on this page are free to read.
What is a software development agreement?
A software development agreement is a services contract built for building software: a fixed price paid in milestones, acceptance testing against a specification, a change-request process, a bug-fix warranty, rules for open-source components and a full handover of source code, repositories and credentials.
It is a Pro template in Legal Drafter. It assigns the client the IP in each milestone once paid, licenses the developer's reusable tools, blocks copyleft surprises, and offers optional source code escrow.
When you need one
- Commissioning a mobile or web app, an MVP or an internal tool from an agency or freelancer.
- Outsourcing development to a team in another country.
- Any project where payment should depend on accepted milestones.
Typical uses: mobile and web app builds, mvps for startups, agency and outsourced development, custom internal tools.
What changes in the UAE
- Governing law
- the laws of the Emirate of Dubai and, to the extent applicable, the federal laws of the United Arab Emirates
- Disputes
- You choose: Local (onshore) courts, DIFC Courts, Arbitration (DIAC)
- You fill in
- Emirate (default Dubai)
- Default currency
- AED
- Date style
- 21 October 2026
- Data protection law cited
- Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (the "PDPL") and any other applicable data protection law of the United Arab Emirates
Software is protected by copyright
UAE copyright law (Federal Decree-Law No. 38 of 2021) protects software. The IP clause transfers rights in writing, milestone by milestone, once each is paid.
Personal data under the PDPL
Where the developer works with personal data, the Confidentiality and data clause requires it to follow your instructions and comply with the PDPL (or the DIFC or ADGM law if that applies).
VAT
Prices exclude VAT (5 percent). A VAT-registered developer adds it to each milestone invoice.
Choosing a forum for technical disputes
Software disputes are often technical. Arbitration lets the parties choose an arbitrator with relevant expertise; DIFC Courts offer English-language proceedings.
Wording that is specific to the UAE version
Generated live from the template: these are the paragraphs that differ from the generic version. Placeholders in brackets are filled from the form.
Confidentiality and data
Each party shall keep the other's confidential information secret and use it only for this Agreement. Where the Developer processes personal data on the Client's behalf, it shall do so only on the Client's documented instructions, keep it secure, and comply with Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (the "PDPL") and any other applicable data protection law of the United Arab Emirates.
Governing law and disputes
This Agreement and any dispute or claim (including non-contractual disputes or claims) arising out of or in connection with it or its subject matter shall be governed by and construed in accordance with the laws of the Emirate of Dubai and, to the extent applicable, the federal laws of the United Arab Emirates.
Any dispute arising out of or in connection with this Agreement shall be subject to the exclusive jurisdiction of the competent courts of the Emirate of Dubai.
Other paragraphs of this clause are the same in every version.
General
(h) Language. This Agreement is made in English. Where this Agreement is translated into Arabic for registration or court purposes, the parties intend the English text to reflect their agreement.
Other paragraphs of this clause are the same in every version.
Sample outline
The UAE Software Development Agreement in clause order. Numbering shifts when optional clauses are switched off.
- Parties and date
- 1.Definitions
- 2.Project
- 3.Fees and milestones
- 4.Acceptance testing
- 5.Change requests
- 6.Intellectual property and source code
- 7.Open-source software
- 8.Warranty
- 9.Source code escrowoptional, off by default
- 10.Confidentiality and data
- 11.Limitation of liability
- 12.Termination
- 13.Governing law and disputes
- 14.General
- Signatures
Key clauses explained in plain English
- Parties and date
- The client commissioning the software and the developer building it.
- 1. Definitions
- Key terms used throughout. The Specification is the yardstick for whether the software works.
- 2. Project
- What is being built and how the client is kept informed.
- 3. Fees and milestones
- A fixed price paid in stages, each stage due only once the client accepts that milestone. Running costs such as hosting are separate.
- 4. Acceptance testing
- How the client checks each stage. Silence or going live counts as acceptance, so projects cannot be held up indefinitely.
- 5. Change requests
- New ideas mid-project are priced and approved in writing before work starts, keeping the budget and timeline under control.
- 6. Intellectual property and source code
- The client owns the code once it has paid, and receives the full source, repositories and passwords at the end. The developer keeps reusable tools but licenses them for this software.
- 7. Open-source software
- Open-source code is fine, but some licences can force you to publish your own code. This clause stops that happening by surprise.
- 8. Warranty
- A free bug-fix period after launch. Problems caused by others' changes or third-party services are excluded.
- 9. Source code escrow
- Optional. Protects the client if the developer disappears before handing over the code.
- 10. Confidentiality and data
- Both sides keep information private, and the developer must handle any personal data in the system lawfully and securely.
- 11. Limitation of liability
- Caps liability at the contract value and excludes knock-on losses, with the usual exceptions.
- 12. Termination
- The client can stop the project, paying for work done. In return it receives everything built so far, including the code.
- 13. Governing law and disputes
- Says which country's (or state's) law applies and where any court case or arbitration happens. It also asks both sides to try talking it through for 30 days first, except in emergencies.
- 14. General
- The standard "boilerplate": this document is the whole deal, changes must be in writing, neither side can hand the contract to someone else without permission, a bad clause does not sink the rest, and how formal notices are sent.
- Signatures
- Where each side signs. For a company, the person signing must be authorised to bind it (for example a director or a manager named on the trade licence).
Common mistakes
- Leaving accounts in the developer's name. App-store, cloud and domain accounts registered to the developer can be hard to recover. Require them in the client's name from day one.
- No specification. Acceptance testing measures the software against the specification. Attach one, even a short one, as Schedule 1.
- Paying everything upfront. Tie payments to milestones that the client accepts. The template invoices each instalment on acceptance.
- Not getting the keys. Make sure repositories, cloud accounts, app-store accounts and domains end up in the client's name. The IP clause requires handover of credentials and administrative control.
- Ignoring open-source licences. Some licences (for example the GPL, used in certain ways) can require you to publish your own code. The template requires open-source components to be identified and copyleft use to be approved.
FAQ
Is this agreement suitable for UAE government projects?
Government and semi-government projects usually use their own mandated contract forms. This template is designed for private commercial projects.
Can a UAE company hire an overseas developer with this agreement?
Yes. Agree the currency, the governing law and the forum carefully; DIAC arbitration is often a practical neutral choice.
How is a software development agreement different from a freelance contract?
It adds what software projects need: milestone payments tied to acceptance tests, a warranty period, source code and credentials handover, open-source rules and change control.
Is the software development template free?
No. It is a Pro template. Pro costs USD 5 for 30 days and also removes your personal daily AI limit (a daily AI budget shared by all users still applies) and the export footer. You can read the full clause outline and explanations on this page for free.
Draft your UAE software development agreement now
Answer a short guided form and watch the draft fill in live. Party details stay in your browser. Edit any paragraph, switch optional clauses on or off, and export to Word, PDF, Markdown or text.
Pro Pro template: USD 5 for 30 days. The outline and explanations on this page are free to read.