Skip to main content
ع
Two different jobs that share one word: translation

Translation and Localisation for Technology Companies in the UAE: SaaS Contracts, PDPL Privacy Policies and Arabic Product Localisation

Take a software product into the UAE and you soon find that "translation" means two jobs. Localisation re-engineers your app into Arabic and right-to-left so it feels built for the market. Legal translation puts the subscription agreement, data-processing agreement and privacy policy into Arabic that a counterparty, regulator or court will rely on. We are a legal translation office in Dubai working under UAE Ministry of Justice accreditation, and we translate that contract stack for software vendors, SaaS providers, app publishers and platform operators, alongside your localisation team. Send the documents on WhatsApp for a free quote.

  • Your whole contract stack translated for the UAE: SaaS and licensing agreements, DPAs, NDAs and terms of service
  • Bilingual privacy policies written to the UAE Personal Data Protection Law, in plain Arabic and English
  • Product localisation that mirrors the interface right-to-left, not merely flips it
  • One approved termbase holding your defined terms steady across every document and every screen
  • Dubai-based, UAE-wide service
  • Arabic & English
  • Clear guidance on every document
  • Direct request, no middlemen
  • Licensed by Dubai's Department of Economy and Tourism

    An accredited and licensed centre in Dubai. The trade licence is held in the name of MANJAZ Corporate & Translation Services L.L.C.

  • From AED 65 a document

    A personal certificate is AED 65 flat however many pages it runs to, a page between Arabic and English is AED 65, and another European or Asian language is AED 90 to 220.

  • 21 documented languages

    Arabic and English are the core pair, and every other language has its own page with the documents it actually brings.

  • More than 18 years of professional experience

    The MANJAZ team brings more than 18 years of professional experience to legal translation and the authorities that receive it.

In short

For a software product entering the UAE, "translation" is two different jobs. Localisation re-engineers the app into Arabic and right-to-left so it reads as built for the market. Legal translation puts the subscription agreement, the data-processing agreement and the PDPL privacy policy into Arabic that a counterparty, a regulator or a court will rely on. MANJAZ handles the second under UAE Ministry of Justice accreditation, alongside your localisation team.

The controlling idea

For a technology company, "translation" hides a fork in the road

When a software business decides to serve the UAE, it usually thinks it has one language problem. In fact it has two, and they pull in opposite directions. The first is about the product: the interface, the onboarding screens, the error messages, the marketing site and the help centre all need to work in Arabic, which means mirroring a left-to-right design into a right-to-left one, choosing an Arabic typeface that renders cleanly, and formatting dates, numbers and currency the way a UAE user expects. That work is as much engineering as language. The second problem is about the paperwork behind the product: the subscription agreement a customer signs, the data-processing terms a client's legal team reviews, the privacy policy a regulator can read, the non-disclosure agreement that protects a proof of concept. That work is legal translation, and its test is not how natural it feels but whether it holds up when someone acts on it.

Mixing the two up is the most expensive language mistake a technology team can make. A brilliant localisation of the app does nothing to make a licence agreement enforceable before a UAE court. And a flawless certified translation of the contract will not stop the Arabic interface breaking because someone flipped the layout instead of re-engineering it. Different work, different people, different standards. Much of what follows is simply a map of that fork: where a document belongs on the legal side, where a string belongs on the product side, and what "good" means on each.

Three kinds of statement run through this page, and it helps to keep them apart. The first is general information about how technology companies work with Arabic in the region. The second covers the official requirements set by the authorities: Arabic as the language of the onshore courts, certified translation of foreign-language documents for court and government use, and the obligations the UAE Personal Data Protection Law places on anyone processing personal data. The third is what we at MANJAZ actually do. We translate the contract stack against its originals, build and keep a termbase so defined terms never drift, and work alongside your localisation so the product and the paperwork speak with one voice. We never blur the three. A technology buyer who takes a market convention for a legal rule is the one who gets caught out later.

One point frames everything else. For a technology company the UAE is not one legal environment. It is at least three. Onshore, where most consumer apps reach their users, Arabic is the language of the courts. The two financial free zones, the Dubai International Financial Centre and the Abu Dhabi Global Market, run in English under common-law systems and keep their own data-protection laws. Much of the advice below turns on which of these worlds your entity, your customers and your data sit in. So the first question we ask is rarely about words. It is almost always about place.

The documents and product assets a technology rollout runs on

SaaS / subscription agreement
The contract by which a customer subscribes to a hosted product rather than buying a copy. It sets the service description, availability commitments, fees, and the boundary of what the provider is and is not responsible for. For an enterprise deal it often sits under a master service agreement with order forms beneath it.
Software licence / EULA
The grant that says what a user may do with the software (install it, copy it, modify it, resell it) and what they may not. An end-user licence agreement is accepted at install or on first use. Its operative grants and restrictions must survive translation exactly, because they are the property line of the product.
Data processing agreement (DPA)
The controller-to-processor contract that governs how a provider handles personal data on a customer's behalf: purposes, security measures, sub-processors, breach handling and cross-border transfer. It is the document a client's privacy team scrutinises most closely, and it maps directly onto the UAE data regimes.
Non-disclosure agreement (NDA)
The confidentiality contract signed before a proof of concept, an integration or a funding conversation, defining what is confidential and what may be done with it. Also called a confidentiality agreement. It is frequently the first document a UAE partner asks to see in Arabic.
Privacy policy and consent flow
The public-facing notice that tells users what data is collected, why, who receives it and how rights are exercised, together with the in-product screens that capture consent. Under the transparency principle of UAE data law it must be written in plain language, and for an Arabic-speaking audience that means a genuine Arabic version, not a machine rendering.
Terms of service / acceptable-use policy
The rules that bind every user of a platform: the terms and conditions and the acceptable-use policy. They speak to consumers and bind them as a contract at the same time. So they must read naturally for a user and hold precisely for a lawyer, which is harder than it looks.
Technical documentation and API docs
User manuals, administrator guides, API references and release notes. Here the risk is not legal exposure but terminological drift: the same feature named three ways across three documents confuses users and support alike. A termbase is what keeps a product's technical vocabulary singular.
UI strings and in-product content
The words inside the software: buttons, labels, menus, tooltips and system messages, usually held in resource files keyed for developers. This is the localisation layer, where length limits, variables and plural rules matter as much as the wording, and where Arabic script and right-to-left flow are engineering constraints, not preferences.
Information-security and IP documents
Cybersecurity policies, information-security schedules attached to enterprise deals, and intellectual-property material such as patent filings and IP assignments. These carry both fixed regulatory vocabulary and highly proprietary content, so they sit at the intersection of precision and confidentiality.

The bright line: localising a product is not the same as translating a contract

Product localisation

  • The goal is a product that feels native. Arabic runs right-to-left, so the interface has to be mirrored. Layout, navigation, icons and alignment are re-engineered, not simply reversed, then tested with an Arabic typeface for line breaks and rendering. Dates, numbers and currency are reformatted to local expectation, and some markets expect the Hijri calendar as an option.
  • Register is a deliberate choice. Interfaces and marketing generally use Modern Standard Arabic for formal, pan-Arab reach, but Gulf Arabic differs from Levantine in expression and tone, so the dialect and voice are chosen for the audience and validated by native speakers. This is a branding decision as much as a linguistic one.
  • The work lives in code. Strings sit in resource files with keys, length limits, variables and plural forms. What you get back is a build that renders correctly, not a document. "Done" means the app looks right and reads right on a device. Product and QA run that test, not a court.

Legal translation of the paperwork

  • The goal is a document that is relied upon. The subscription agreement, licence, DPA, NDA and privacy policy are rendered in full and precisely, with defined terms, grants and obligations carried across without softening. The audience is a counterparty's lawyer, a regulator or, in the worst case, a judge.
  • Register is fixed, not chosen. Legal and contractual text stays in formal Modern Standard Arabic, so there is no dialect to decide. Where a document is going to an onshore court or a government body, UAE law requires it to be translated into Arabic by a legal translator registered with the Ministry of Justice. That is a question of admissibility, not style.
  • The work lives in meaning. The deliverable is a document whose two versions say the same thing, so that no ambiguity can be exploited later. "Done" means a lawyer can rely on the Arabic and a court could act on it. The test is obligations honoured, not pixels aligned.

Want this checked for your own document?

Localise the product so it feels built for the user. Translate the contract so it holds up for the lawyer. Ask one job to do the other's work and you get an app that reads beautifully and an agreement that does not stand.

The privacy policy and the UAE Personal Data Protection Law

For a consumer app or platform, the privacy policy is where translation and regulation meet head on. The UAE Personal Data Protection Law is Federal Decree-Law No. 45 of 2021, which came into effect at the start of 2022. It governs the processing of personal data and has extra-territorial reach, so it can catch a company processing the data of people in the UAE even when the business itself sits elsewhere. The national regulator is the UAE Data Office. The law is built on principles a privacy notice has to reflect: a lawful basis for processing, transparency toward the individual, appropriate security measures, and defined rights for the data subject.

Several of these become concrete drafting duties. The transparency requirement (widely cited as Article 13) obliges a controller to tell individuals, in clear terms, the purposes of processing, the parties who receive the data, cross-border sharing, and how to exercise their rights. Where consent is the basis relied on (Article 6), it has to be demonstrable. Security measures are required (Article 5). A qualifying breach must be notified to the Data Office without delay (Article 9). And high-risk or large-scale sensitive processing can trigger the appointment of a data protection officer (Article 10). Data subjects get rights of access, portability, correction and erasure, restriction, objection, and rights around automated decision-making. A privacy policy is, in effect, the public statement that these duties are being met. That is why its wording is not marketing copy.

So where does translation come in? For a business serving Arabic-speaking users, a policy in Arabic and English is the practical route to the transparency principle. That is compliance practice, not a single explicit article, and we flag it as such. Here is our part. We put the notice into plain, readable Arabic that keeps the legal meaning intact. We hold the data-protection vocabulary steady across the privacy policy, the DPA and the consent screens with one termbase. And we keep the two language versions saying the same thing. We do not advise on your compliance position. For that, work with a UAE privacy lawyer and confirm current requirements with the UAE Data Office.

One country, three data-protection regimes, and they are not identical

RegimeWho it coversBreach notification
Federal PDPL: Federal Decree-Law No. 45 of 2021Onshore UAE and free zones without their own data law; extra-territorial reach to UAE data subjects. Regulator: UAE Data Office.Notify the Data Office immediately upon becoming aware of a qualifying breach (Article 9).
DIFC: Data Protection Law No. 5 of 2020Entities established in the Dubai International Financial Centre; broadly GDPR-aligned.Notify the Commissioner as soon as practicable in the circumstances (no fixed hour).
ADGM: Data Protection Regulations 2021Entities established in the Abu Dhabi Global Market; broadly GDPR-aligned, under English common law.Notify the Commissioner without undue delay and, where feasible, within seventy-two hours of becoming aware.

Tell us what you are launching (a consumer app, a SaaS platform or an enterprise integration), where your entity and data sit, and which documents are involved. We map what needs localising, what needs certified legal translation, and in what order. You get a free quote, and we confirm the delivery time in writing with it.

Scope a technology project

A SaaS company entering the UAE: the two workstreams, in order

  1. Fix the jurisdiction and the data regime first

    Decide where the contracting entity sits and which data regime governs your processing: federal PDPL, DIFC or ADGM. That one decision shapes the contract language, the privacy notice and the DPA, so it comes before any translation.

  2. Build the termbase before translating anything

    Agree the Arabic for your defined terms, such as the product name, "Service", "Subscriber", "Personal Data", "controller" and "processor", and lock them in a termbase. Set once, they stay identical across the contract stack, the policies and the interface.

  3. Translate the contract stack

    Render the subscription or master service agreement, the licence, the DPA and any NDA into Arabic, in full and against the originals. Where a document is destined for an onshore court or authority, it is handled as certified legal translation.

  4. Draft the PDPL-ready bilingual privacy policy

    Produce the privacy policy and consent flow in plain Arabic and English, reflecting the transparency, consent, security and rights duties of the governing data regime, with the vocabulary matched to the DPA already translated.

  5. Localise the product and its content

    Now the engineering-plus-language work: mirror the interface right-to-left, localise the UI strings, marketing site and help centre, and test rendering in an Arabic typeface. The register here is a branding choice, distinct from the fixed legal Arabic of the contracts.

  6. Keep it consistent as versions ship

    A product is never finished. The termbase and translation memory carry forward into release notes, new features and policy updates: the same defined terms, the same voice, and no re-arguing decisions already made.

Have a question about your case?

Technology situations that turn on a translated document or a localised screen

A SaaS company launching a consumer app in the UAE market

What is usually neededTwo workstreams. Product localisation covers right-to-left mirroring, Arabic fonts, locale formats and the dialect choice. Legal translation covers the SaaS agreement, the DPA and a PDPL-ready bilingual privacy policy. A shared termbase keeps the two aligned.

A tech vendor closing an enterprise deal across several documents

What is usually neededThe deal's business contracts translated as one set: master service agreement, DPA, NDA and statements of work. A shared termbase and translation memory keep every defined term identical, and confidentiality controls cover the material throughout.

A fintech or health-tech deciding which data regime applies

What is usually neededPrivacy and data-processing documents drafted to the correct regime (federal PDPL, DIFC Law No. 5 of 2020 or ADGM Regulations 2021), in Arabic and English, with careful handling of the sensitive-data and cross-border wording.

A software vendor whose licence dispute reaches an onshore court

What is usually neededA certified Arabic translation of the licence or EULA and the correspondence, by a legal translator registered with the Ministry of Justice, because onshore the Arabic version is what the court reads and acts on.

A startup preparing an investor data room and NDAs

What is usually neededNDAs, corporate and IP documents rendered accurately and consistently, so a bilingual due-diligence process reads the same terms in both languages and confidentiality is preserved.

A platform publishing technical documentation and release notes

What is usually neededUser manuals, API references and release notes localised with an enforced termbase, so the same feature is named the same way across every document, screen and support article.

Why one word, one meaning

The quiet engine of a technology account: the termbase, the memory and a second reviser

Technology content punishes inconsistency more than almost any other kind. One product might name the same feature one way in the interface, another way in the user manual and a third way in the API reference. A contract might define "Subscriber" while the privacy policy talks about "the user" and the DPA about "the data subject". Each choice is defensible on its own. Together they blur the picture for whoever has to match them up: a support agent, a customer's lawyer, a regulator. Terminology management is what prevents this. On a serious technology account it is not an optional extra. It is the spine of the work.

Two tools do the work, at different levels. A termbase is a glossary with rules. It works at the level of the word, storing your approved terms and how each one should be rendered, so "Personal Data", "controller" and your product name are fixed once and reused everywhere. A translation memory works at the level of the sentence. It stores segments you have already approved and offers them back when the same or a similar passage comes round again, which is common across versions of a policy or successive release notes. Enterprise translation tools combine the two. Industry references count a well-maintained termbase among the biggest drivers of both consistency and speed across legal, financial, technical and software content.

There is also a quality-process point worth stating plainly, because technology buyers ask about it. The international translation-services standard ISO 17100 describes how defensible translation should be organised. It calls for a terminology-management system, defined translator and reviser competence, and a two-step process in which a second qualified person revises the translation, with an audit trail behind it. It is a voluntary process standard, and it answers a different question from UAE licensing. A two-stage revision discipline speaks to how consistent and traceable the work is. A legal translator's registration with the Ministry of Justice speaks to whether a court or authority will accept the document at all. A serious provider can answer both questions, but they should never be folded into one.

Here is what continuity looks like in practice. When your v2 ships with new screens and an updated privacy policy, we do not start from a blank page. The termbase already holds your vocabulary and the memory already holds your recurring clauses, so the new work matches the old without re-arguing how each term should read. That is why the first project is worth setting up carefully. Everything after it inherits the decisions made once.

Source code, pre-release features and the confidentiality posture behind them

Technology material is unusually sensitive. An NDA arrives before a deal is public, a DPA describes a security architecture, technical documentation can expose how a product actually works, and IP filings carry inventions not yet protected everywhere. Confidentiality here is not a courtesy. It is a condition of the work. In the UAE it also has a legal backbone: under the federal law regulating the translation profession, a registered translator is bound to keep the confidentiality of what passes through their hands, and disclosure of confidential information is treated as a serious professional breach.

On our side, we set the confidentiality scope before the file arrives, keep proprietary technical and source material to the people who must see it, and are ready to work under your own NDA. Where you need it, we handle the enterprise document set (MSA, DPA, NDA and security schedules) as one controlled workstream rather than scattered files. That way the handling itself exposes nothing sensitive.

Where a technology localisation or translation goes wrong

  • The mistakeTreating localisation as translation: flipping the layout instead of re-engineering it and skipping the Arabic font and line-break tests, so the interface arrives broken.

    The fixMirror the design right-to-left as an engineering task, test rendering in a real Arabic typeface, and format dates, numbers and currency to local expectation before shipping.

  • The mistakeAssuming the three UAE data regimes are the same, so a DIFC-style notice is reused onshore, or a breach process built for one regime is applied to another with a different notification rule.

    The fixConfirm which regime governs (federal PDPL, DIFC Law No. 5 of 2020 or ADGM Regulations 2021), then draft the notice, DPA and breach language to that regime specifically.

  • The mistakeIgnoring register: legal terms written in a casual dialect, or a consumer interface written in stiff contractual Arabic that no user warms to.

    The fixKeep contracts and policies in formal Modern Standard Arabic. For the interface, choose the register (Modern Standard or a Gulf voice) deliberately for the audience, and have native speakers validate it.

  • The mistakeLetting terminology drift across a multi-document deal, so "Service", "controller" and the product name are rendered differently in the contract, the policy and the interface.

    The fixBuild and enforce one termbase at the start, and carry it, with a translation memory, across every document and every later version.

  • The mistakeForgetting that some categories of data face transfer or localisation restrictions, and drafting a cross-border clause that a regime would not permit.

    The fixFlag sensitive and regulated categories early, keep the cross-border wording within what the governing regime allows, and confirm the current position with a UAE privacy lawyer and the Data Office.

  • The mistakeAssuming an English-only contract is safe because the business runs in English, then discovering at litigation that the onshore court reads Arabic and needs a certified translation.

    The fixWhere a dispute could reach an onshore court, prepare a certified Arabic version through a legal translator registered with the Ministry of Justice rather than improvising one under deadline.

What to send us to scope a technology project

  • What you are launching and for whom (a consumer app, a SaaS platform, an enterprise integration), and which you need: localisation, legal translation, or both.
  • Where the contracting entity sits and where your users and data are (onshore, DIFC or ADGM), so the governing data regime is settled before drafting.
  • The contract stack in hand: the SaaS or master service agreement, the licence or EULA, the DPA, any NDA and the terms of service.
  • Any existing privacy policy, consent flow and cookie notice, and whether a version already exists in Arabic.
  • Your defined terms and product names, and any glossary or style guide you already use, so the termbase starts from your decisions rather than ours.
  • For product localisation, the string files or export format, with any length limits, variables and platform constraints noted.
  • The confidentiality terms you need: your own NDA, restricted access, or handling instructions for source and pre-release material.

The language pairs behind a UAE technology rollout

  • English ↔ ArabicThe core pair. Products and their paperwork are usually written in English and translated into Arabic for the market, for the users and, if it ever comes to that, for an onshore court. Arabic documents and user feedback travel the other way, into English for the product team.
  • Arabic register: Modern Standard vs GulfNot a language pair but a choice within Arabic. Contracts and policies stay in formal Modern Standard Arabic. A consumer interface or campaign may lean to a Gulf voice for the UAE audience, and that is a decision to make on purpose, not by default.
  • Other source languages → Arabic / EnglishTechnology teams are global. Product content and corporate documents arriving from other source languages are reconciled into consistent Arabic and English for the UAE, against one termbase so terms do not diverge on the way.
  • Arabic → English for the free zonesFor a DIFC or ADGM entity operating in English, an Arabic document that lands in the file, such as a counterparty's contract or an onshore notice, is translated into English so the in-zone team can read it and act on it.

Not sure which route applies to your document?

Technology translation and localisation: your questions

Next step

Request Information Technology Translation

Send the document and we confirm the exact certification the receiving authority expects.