MyLegalDocsAI.aeLegal documents online
United Arab Emirates

UAE personal data requests: access, correction, erasure, restriction and proof

A UAE personal-data request should identify the controller, data, processing activity and right being exercised. Separate access to information, portability, correction, erasure, restriction and objection instead of sending one vague privacy demand.

Published 27 Sep 2026 · checked against official UAE sources

Check first whether the federal PDPL governs the processing

Federal Decree-Law No. 45 of 2021 creates a federal personal-data protection framework, but its scope contains exclusions and the UAE also has special data-protection regimes and sector rules. Before drafting, identify the controller, where it is established, what data is involved and whether a financial free-zone law, government-data exclusion, health-data rule, credit-information law or another specialist framework may apply. Do not cite the federal PDPL automatically to every organisation operating in the UAE.

Record why the chosen regime appears applicable and keep the organisation’s privacy notice, terms and contact details. If the controller identifies a Data Protection Officer, preserve that contact. Where jurisdiction is uncertain, a neutral request can ask the organisation to identify the regime and controller responsible for the processing. This is better than asserting a legal conclusion that may be wrong for a DIFC, ADGM, government or specially regulated dataset.

Use Article 13 for a structured information request

Article 13 gives the data subject a right, by request to the controller and without charge, to obtain specified information. The categories include types of personal data processed, purposes of processing, automated decision-making including profiling, sectors or establishments with which the data is shared inside and outside the State, storage and preservation controls, procedures for correction, erasure, restriction and objection, cross-border safeguards, breach-response measures in relevant circumstances, and how to complain to the Bureau. Draft the request around the categories actually needed.

Avoid asking the controller to produce “everything about me under all laws” if the real issue is a particular account or decision. Identify the relationship, approximate dates, identifiers and processing activity so the controller can locate the record. Where the request concerns automated profiling, describe the decision or event that makes that information relevant. A focused Article 13 request reduces the risk of an argument that the request is unrelated or excessively repetitive.

Account for Article 13 refusal grounds

The federal law permits the controller to reject an Article 13 information request in specified circumstances, including where the request is unrelated to the listed information or excessively repetitive, conflicts with judicial procedures or competent-authority investigations, may negatively affect information-security efforts, or affects the privacy and confidentiality of third parties’ personal data. A request should therefore avoid unnecessary repetition and should not demand third-party information merely because it appears in the same account.

If the controller refuses, ask for the legal and factual basis to be identified sufficiently for the data subject to understand the response, subject to any lawful restriction on what can be disclosed. Keep the original request and refusal together. Do not assume every redaction is unlawful; a redaction may protect another person’s data. The next step should address the actual refusal ground rather than simply resending the same wording.

Use Article 14 only where portability conditions fit

Article 14 addresses receiving personal data provided by the data subject in an orderly, machine-readable form where the processing is based on consent or is necessary for performance of a contractual obligation and is carried out by automated means. It also addresses transfer to another controller where technically feasible. This is narrower than a general demand for every internal record. Identify the data that was provided, the relevant consent or contract and the desired structured format.

If direct transfer to another controller is requested, provide accurate recipient details and explain the data set sought. Do not use portability as a shortcut to demand confidential internal analysis that the data subject never provided unless another right genuinely covers it. Separating portability from Article 13 information rights makes the request easier to process and reduces scope disputes.

Correct inaccurate data with a fact-by-fact schedule

Article 15 provides a right to request correction or completion of inaccurate personal data without undue delay. A correction request should list the field as currently recorded, the corrected value, why the existing value is inaccurate or incomplete, and the document supporting the correction. Typical evidence might include identification, a contract amendment, payment record or correspondence. Do not ask the controller to replace a disputed opinion with the data subject’s preferred opinion as though that were a simple factual correction.

Where accuracy is contested, request that the controller identify the source and preserve a record of the dispute while it is assessed. If an inaccurate data point is being shared with other recipients, identify the practical harm and ask what propagation or correction steps are available under the applicable law. Keep proof of submission and the corrected output once received.

Frame erasure requests around Article 15 conditions and exceptions

Article 15 allows erasure requests in circumstances including where data is no longer necessary for the purposes for which it was collected or processed, consent has been withdrawn where relevant, the data subject objects and there is no legitimate ground to continue, or processing violates the decree-law and erasure is needed for compliance. The law also contains exceptions, including situations connected with public health, investigations, claims or defence of legal rights, conflicting legal retention duties and other cases specified by regulation.

A useful erasure request therefore identifies the data, original purpose and reason the statutory condition is said to apply. Do not demand destruction of records that an organisation is legally required to retain without addressing that obligation. Where only part of a record is unnecessary, consider a narrower request. If litigation or a dispute is pending, preservation obligations can be important and the proper remedy may differ from immediate deletion.

Use restriction when accuracy or lawfulness is being checked

Article 16 gives the data subject a right to require restriction and cessation of processing in specified cases, including while accuracy is contested and verified, where processing is said to violate agreed purposes or applicable law, and in related circumstances set out in the provision. A restriction request should identify the disputed data and the processing activity to be paused. It is more precise than demanding that an organisation “stop using all my data” without identifying what use is challenged.

The same article permits continued processing in certain circumstances, including storage and legal-claims contexts. If the controller says processing must continue, ask it to identify the basis and limit the activity to what that basis permits. Keep a dated record of when restriction was requested, acknowledged, lifted or refused. That chronology can be important where an automated decision or disclosure occurs during the disputed period.

Separate objection to automated decisions from a basic access request

The federal framework also addresses objections related to automated processing and profiling. If the issue is a decision made solely by automated processing that has legal or other significant effects, identify the decision, date, data inputs known to the individual and the review requested. Article 13 can be used to seek information about automated decision-making, but the substantive objection or request for human review should be stated separately under the applicable provision.

Do not assume every use of software is a solely automated decision. A human may have reviewed the outcome, or the system may only have generated a recommendation. Ask the controller to explain the role of automation rather than asserting facts that are not known. Preserve screenshots, notices and outcome letters that show how the decision was presented.

Map recipients and cross-border transfers before narrowing the request

Article 13 expressly includes information about the sectors or establishments inside and outside the State with which personal data is shared, and information on safeguards used for cross-border processing. Where disclosure is the concern, ask the controller to identify the relevant recipient categories, purposes and cross-border safeguards for the data set in question. Keep the wording focused on the person’s data and the relevant processing period rather than asking for confidential contracts or security material that is not necessary to understand the transfer.

Once the response identifies recipient categories, compare them with the privacy notice that applied when the data was collected and any later notice of change. If a particular transfer is disputed, record the destination, approximate date, purpose and data category as far as the evidence allows. This produces a usable factual record for a complaint while avoiding unsupported claims about where servers or processors are located.

Prove identity without oversharing

A controller needs reasonable assurance that a person exercising rights is the relevant data subject, but the request itself should not create a new unnecessary data exposure. Use the organisation’s official channel and follow its current identity-verification procedure. Where a copy of identity documentation is requested, check why it is necessary, how it will be transmitted and whether a less intrusive verification method is available. Avoid sending passports or Emirates ID images to unverified addresses.

If a representative makes the request, provide the authority document appropriate to the context and limit it to the necessary scope. The file should show who submitted the request, on whose behalf and what identification was provided. Redact copies retained in a general working file if full identifiers are not needed for later proof.

Create a request register with one row per right

Maintain a table with request date, controller, right invoked, data or processing covered, delivery method, acknowledgment, response date, outcome and next action. If access, correction and erasure are requested together, give them separate rows even if sent in one letter. This makes it possible to see that a controller answered the access element but did not address the correction request, rather than treating the whole response as complete.

Attach each response to the relevant row and preserve any portal reference number. Where the controller asks for clarification, record the clarification date and exact narrowed scope. A structured register is especially useful for organisations with multiple accounts or data systems because it prevents the same request from being duplicated unnecessarily.

Escalate a privacy complaint from the documentary gap

If the controller does not resolve the request, identify what remains unanswered: missing Article 13 information, disputed accuracy, refused erasure, continued processing despite a restriction request, or an unresolved automated-decision objection. Preserve the request, proof of delivery, controller response and relevant privacy notice. Check the current UAE Data Office or other competent supervisory route for the applicable regime before filing a complaint.

A complaint should not simply repeat the original request. Explain the statutory right relied on, what the controller did, the precise deficiency and the corrective action requested. If another data-protection regime applies, use that regulator and its forms. Jurisdiction and scope are part of the complaint, not an afterthought.

Keep legal claims and preservation needs in view

Personal-data rights can intersect with litigation, employment disputes, fraud investigations and regulatory retention duties. Before requesting erasure of records that may be evidence, consider whether preservation is necessary to establish or defend legal rights. The federal PDPL itself recognises legal-claims and investigation contexts in several provisions. A request should not unintentionally destroy material the data subject later needs.

Where the real objective is to obtain evidence for a dispute, identify whether the PDPL right actually provides the information sought or whether a procedural disclosure route is more appropriate. Where the objective is to stop an inaccurate automated decision, correction and restriction may be more useful than broad erasure. Choosing the right remedy produces a cleaner record and avoids conflicting requests.

Official sources checked for this guide

Official portals, forms, index calculations and translated legislation can change. Re-check the current source immediately before sending a notice, making a complaint or acting on a deadline.

Final check

This guide is general document-preparation information, not a determination that the federal PDPL applies to a specific controller or dataset. UAE government data, financial free zones and sector-specific information can involve different rules. Verify scope, exceptions, current supervisory procedures and the operative Arabic legislation before escalating a request.