Data Protection Monitor
Global Privacy & Data Protection Intelligence

Qatar Data Protection & Privacy Regulation

QA schema gdpri-v2 trajectory: not yet assessed hybrid regime overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 95 claims · 40 sources in the cumulative register

Qatar's data-protection enforcement posture has moved decisively from an awareness phase into a pattern of active, dated binding decisions.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Regulator & Framework, Controller/Processor Duties (3 open gaps).

Framework & posture10 of 10 modules active
10 active · 15 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix95 claims · 36 sources · machine-compiled
32 Confirmed44 Probable18 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

Jurisdiction brief

Latest update · 4 November 2026

Lead Signal

A sector-specific data-localisation layer affecting the financial industry is understood to have surfaced afresh in commentary on Qatar. A Qatar Central Bank Data Handling and Protection Regulation, issued in February 2025, is reported to require financial institutions supervised by the central bank to keep the primary storage and processing environment for personal, sensitive personal and sensitive financial information inside Qatar, with an offshore primary environment permitted only where the central bank gives explicit prior approval. This sits as a sector-specific overlay on top of the jurisdiction's general cross-border transfer rule under Article 15 of Law No. 13 of 2016, which already restricts the transfer of personal data outside Qatar where the receiving jurisdiction's processing would breach the Law or cause serious damage to the data subject, with the Compliance and Data Protection Department assessing the adequacy of the receiving jurisdiction on a case-by-case basis.

Key regulatory facts for Qatar
Key regulatory facts for Qatar
Regulatory DimensionQatar Standing Position
JurisdictionQatar (QA)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 95 sourced findings)
Regulator & FrameworkBoth primary instruments are identified and verifiably in force, but mainland secondary guidance (Tier-2) is thin and the dual-perimeter structure creates residual scoping ambiguity for firms operating across both.
Lawful Processing & Special DataLawful bases, consent and special-category rules are confirmed for both regimes; pseudonymisation/anonymisation treatment is an unresolved gap.
Data Subject RightsQFC rights framework is well-documented and comprehensive; mainland rights detail and statutory response deadlines are thinly sourced.
Controller/Processor DutiesCore accountability, security, ROPA and breach-notification duties are well-evidenced for the QFC; DPO-appointment obligation for firms is unresolved, and mainland retention/disposal rules were not located.
Primary Instruments CitedQatar Official Instrument (assurance.ncsa.gov.qa law), Qatar Official Instrument (qatarliving.com data-protection-privacy-law-comp), MOTC, Qatar Official Instrument (recordinglaw.com qatar-data-privacy-laws), Qatar Official Instrument (practiceguides.chambers.com qatar)
Last Confirmed / Updated (40 sources in cumulative register)

#

Both primary instruments are identified and verifiably in force, but mainland secondary guidance (Tier-2) is thin and the dual-perimeter structure creates residual scoping ambiguity for firms operating across both.

Primary frameworkLaw No. 13 of 2016 Concerning Privacy and Protection of Personal Data (mainland Qatar)
Traffic-light rationale — AmberBoth primary instruments are identified and verifiably in force, but mainland secondary guidance (Tier-2) is thin and the dual-perimeter structure creates residual scoping ambiguity for firms operating across both.

Sub-modules (5)

Regulator and authorityAmber

Mainland: NCSA's National Cyber Governance and Assurance Affairs division is the supervisory authority for Law 13/2016. QFC free zone: the independent QFC Data Protection Office, under the QFC Authority, administers the QFC Data Protection Regulations 2021.

Claims (8):

  • The National Cyber Governance and Assurance Affairs division of the National Cyber Security Agency (NCSA) is the supervisory authority for Law No. 13 of 2016 Concerning Privacy and Protection of Personal Data in mainland Qatar.
  • The QFC Data Protection Office is an independent institution of the Qatar Financial Centre charged with administering the QFC Data Protection Regulations 2021 and all aspects of data protection within the QFC.
  • National Cyber Governance and Assurance Affairs (NCGAA) — NCGAA, a division of NCSA, acts as the competent authority for administering and enforcing the PDPPL on the mainland.
  • Applies to all personal data electronically processed within Qatar's territory, excluding the Qatar Financial Centre Free Zone.
  • National Cyber Security Agency (NCSA) / NCGAA — PDPPL via NCGAA's Compliance and Data Protection Department; NCSA clarified it (not MCIT) is the Art 26 'competent department'
  • The National Cyber Security Agency (NCSA) performs the duties of the Competent Authority supervising personal-data processing in Qatar under the PDPPL.
  • National Cyber Governance and Assurance Affairs (NCGAA), NCSA — NCGAA, a division of Qatar's National Cyber Security Agency (NCSA), is responsible for administering and enforcing the Personal Data Privacy Protection Law (PDPPL) on the Qatari mainland, including developing and publishing compliance guidelines.
  • Mainland Qatar's data-protection regime is overseen by the NDPO within the NCSA; the QFC operates a separate Data Protection Office.

Act and instrumentsGreen

Mainland instrument: Law No. 13 of 2016, published in the Official Gazette 29 December 2016. QFC instrument: QFC Data Protection Regulations 2021 plus the Data Protection Rules 2021, which replaced the 2005 QFC Data Protection Regulation and Rules.

Claims (7):

  • Law No. 13 of 2016 Concerning Privacy and Protection of Personal Data was published in Qatar's Official Gazette on 29 December 2016 and became effective in 2017.
  • The QFC Data Protection Regulations 2021, supported by the Data Protection Rules 2021, came into force on 19 June 2022, replacing the QFC Data Protection Regulations and Rules 2005.
  • The QFC Data Protection Regulations 2021 came into force 19 June 2022, replacing the earlier QFC Data Protection Regulations 2005, and form a standalone GDPR-modelled regime for QFC-registered entities.
  • QFC Data Protection Regulations and Rules 2021 came into force 19 June 2022, repealing the 2005 instruments.
  • Law No. 13 of 2016 Concerning Privacy and Protection of Personal Data — Law No. 13 of 2016 was published in Qatar's Official Gazette on 29 December 2016 and entered into effect in 2017, applying to personal data obtained or processed electronically, including through a mix of traditional and electronic methods.
  • Qatar operates two parallel data-protection regimes: the mainland PDPPL and the separate QFC Data Protection Regulations 2021.
  • Law No. 13 of 2016 was published in the Official Gazette on 29 December 2016 and became effective in 2017.

Material scopeGreen

Mainland Law 13/2016 covers only electronically processed personal data (or data gathered for electronic processing), excluding purely private/family processing and official surveys/statistics. QFC Regulations apply to Data Controllers/Processors incorporated or registered in the QFC.

Claims (3):

  • Law No. 13 of 2016 applies only to personal data that is electronically processed, or gathered/extracted in preparation for electronic processing, and does not apply to private/family processing or data gathered for official surveys and statistics.
  • The QFC Data Protection Regulations 2021 apply to a Data Controller or Data Processor incorporated or registered in the QFC.
  • Law No. 13 of 2016 (PDPPL), Art 1 — personal data of an individual whose identity is defined or reasonably definable, obtained or extracted electronically, including via combined traditional/electronic processing

Territorial scopeAmber

The QFC Commissioner interprets Article 7(2) as extending the Regulations to non-QFC-licensed firms that process personal data of data subjects in Qatar on an ongoing (non-occasional) basis, and QFC guidance confirms a non-QFC controller processing a QFC subsidiary's employee data for that subsidiary's benefit is itself caught. No equivalent explicit extraterritorial clause was located for mainland Law 13/2016 in the sources reviewed.

Claims (2):

  • The QFC Data Protection Office interprets the Regulations as applying to non-QFC-licensed firms that process personal data of data subjects located in Qatar on an ongoing (more than occasional) basis, including non-QFC controllers processing data of a QFC subsidiary's employees.
  • The QFC Data Protection Office interprets the QFC Data Protection Regulations 2021 as applying to non-QFC-licensed firms that process personal data of data subjects located in Qatar on an ongoing basis.

Regulator registration and filingAmber

QFC Data Controllers have no general obligation to register with the Data Protection Office. Mainland Law 13/2016 requires Competent Department permission before processing personal data of a 'special nature.'

Claims (2):

  • QFC Data Controllers have no general obligation to register with the QFC Data Protection Office.
  • Under mainland Law No. 13 of 2016, personal data of a special nature may only be processed after obtaining permission from the Competent Department, per measures determined by ministerial decision.
Category narrative 123 words

Qatar operates two entirely separate data-protection perimeters. Mainland Qatar is governed by Law No. 13 of 2016 Concerning Privacy and Protection of Personal Data, supervised by the National Cyber Governance and Assurance Affairs division of the National Cyber Security Agency (NCSA), with implementation guidance historically issued via the Ministry of Transport and Communications (MOTC) Compliance and Data Protection Department. Separately, the Qatar Financial Centre (QFC) free zone operates the QFC Data Protection Regulations 2021 (in force since 19 June 2022, replacing the 2005 regime), administered by the independent QFC Data Protection Office (DPO) under the QFC Authority. The two regimes do not apply to each other's perimeter; QFC Law expressly disapplies mainland civil/regulatory law matters covered by the QFC Regulations within the QFC.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (22)
  1. Confirmed DataGuidance — The National Cyber Governance and Assurance Affairs division of the National Cyber Security Agency (NCSA) is the supervisory authority for Law No. 13 of 2016 Concerning Privacy and Protection of Personal Data in mainland Qatar. observed
  2. Confirmed Qatar Financial Centre — The QFC Data Protection Office is an independent institution of the Qatar Financial Centre charged with administering the QFC Data Protection Regulations 2021 and all aspects of data protection within the QFC. observed
  3. Confirmed DataGuidance — Law No. 13 of 2016 Concerning Privacy and Protection of Personal Data was published in Qatar's Official Gazette on 29 December 2016 and became effective in 2017. observed
  4. Confirmed Qatar Financial Centre — The QFC Data Protection Regulations 2021, supported by the Data Protection Rules 2021, came into force on 19 June 2022, replacing the QFC Data Protection Regulations and Rules 2005. observed
  5. Confirmed MOTC — Law No. 13 of 2016 applies only to personal data that is electronically processed, or gathered/extracted in preparation for electronic processing, and does not apply to private/family processing or data gathered for official surveys and statistics. observed
  6. Confirmed Qatar Financial Centre Authority — The QFC Data Protection Regulations 2021 apply to a Data Controller or Data Processor incorporated or registered in the QFC. observed
  7. Probable Qatar Financial Centre Data Protection Office — The QFC Data Protection Office interprets the Regulations as applying to non-QFC-licensed firms that process personal data of data subjects located in Qatar on an ongoing (more than occasional) basis, including non-QFC controllers processing data of a QFC subsidiary's employees. observed
  8. Confirmed Qatar Financial Centre — QFC Data Controllers have no general obligation to register with the QFC Data Protection Office. observed
  9. Confirmed DataGuidance (unofficial translation) — Under mainland Law No. 13 of 2016, personal data of a special nature may only be processed after obtaining permission from the Competent Department, per measures determined by ministerial decision. observed
  10. Confirmed DataGuidance — National Cyber Governance and Assurance Affairs (NCGAA) — NCGAA, a division of NCSA, acts as the competent authority for administering and enforcing the PDPPL on the mainland. observed
  11. Confirmed https://www.recordinglaw.com/world-laws/world-data-privacy-laws/qatar-data-privacy-laws/ — The QFC Data Protection Regulations 2021 came into force 19 June 2022, replacing the earlier QFC Data Protection Regulations 2005, and form a standalone GDPR-modelled regime for QFC-registered entities.
  12. Probable Finance Magnates — Applies to all personal data electronically processed within Qatar's territory, excluding the Qatar Financial Centre Free Zone. observed
  13. Probable DataGuidance — QFC Data Protection Regulations and Rules 2021 came into force 19 June 2022, repealing the 2005 instruments. observed
  14. Probable Chambers and Partners — Law No. 13 of 2016 Concerning Privacy and Protection of Personal Data — Law No. 13 of 2016 was published in Qatar's Official Gazette on 29 December 2016 and entered into effect in 2017, applying to personal data obtained or processed electronically, including through a mix of traditional and electronic methods. observed
  15. Uncertain Chambers and Partners — The QFC Data Protection Office interprets the QFC Data Protection Regulations 2021 as applying to non-QFC-licensed firms that process personal data of data subjects located in Qatar on an ongoing basis. observed
  16. Probable https://practiceguides.chambers.com/practice-guides/data-protection-privacy-2026/qatar — National Cyber Security Agency (NCSA) / NCGAA — PDPPL via NCGAA's Compliance and Data Protection Department; NCSA clarified it (not MCIT) is the Art 26 'competent department'
  17. Probable https://securiti.ai/qatar-personal-data-protection-law/ — Law No. 13 of 2016 (PDPPL), Art 1 — personal data of an individual whose identity is defined or reasonably definable, obtained or extracted electronically, including via combined traditional/electronic processing
  18. Confirmed https://assurance.ncsa.gov.qa/en/privacy/law — The National Cyber Security Agency (NCSA) performs the duties of the Competent Authority supervising personal-data processing in Qatar under the PDPPL.
  19. Probable QFC Regulatory Authority — Qatar operates two parallel data-protection regimes: the mainland PDPPL and the separate QFC Data Protection Regulations 2021. observed
  20. Confirmed National Cyber Security Agency (NCSA), Qatar — National Cyber Governance and Assurance Affairs (NCGAA), NCSA — NCGAA, a division of Qatar's National Cyber Security Agency (NCSA), is responsible for administering and enforcing the Personal Data Privacy Protection Law (PDPPL) on the Qatari mainland, including developing and publishing compliance guidelines. observed
  21. Probable Chambers and Partners — Mainland Qatar's data-protection regime is overseen by the NDPO within the NCSA; the QFC operates a separate Data Protection Office. observed
  22. Probable DataGuidance — Law No. 13 of 2016 was published in the Official Gazette on 29 December 2016 and became effective in 2017. observed

#

Lawful bases, consent and special-category rules are confirmed for both regimes; pseudonymisation/anonymisation treatment is an unresolved gap.

Primary frameworkLaw No. 13 of 2016 (mainland); QFC Data Protection Regulations 2021, Articles 10-12 (QFC)
Traffic-light rationale — AmberLawful bases, consent and special-category rules are confirmed for both regimes; pseudonymisation/anonymisation treatment is an unresolved gap.

Sub-modules (4)

Lawful basesGreen

Mainland: consent of the data subject is the main legal basis for processing. QFC: Article 10 enumerates the lawful bases (bases) under which all Personal Data Processing must take place.

Claims (4):

  • Mainland Law No. 13 of 2016 establishes the consent of the data subject as the main legal basis for processing personal data.
  • Article 10 of the QFC Data Protection Regulations 2021 sets out the lawful basis or bases under which all Personal Data Processing must take place.
  • Qatar PDPPL — prior, informed and specific consent of the data subject; no GDPR-style legitimate-interests balancing test confirmed
  • PDPPL Article 4 requires explicit consent for data processing absent a lawful purpose justification.

Special categoriesGreen

Mainland: special-nature data requires Competent Department permission and may be subject to Minister-imposed additional precautions. QFC Article 12 separately governs processing of Sensitive Personal Data.

Claims (4):

  • Under mainland Law No. 13 of 2016, the Minister may impose additional precautions to protect personal data of a special nature by ministerial decision.
  • Article 12 of the QFC Data Protection Regulations 2021 separately governs the Processing of Sensitive Personal Data.
  • PDPPL special categories — Processing of special/sensitive categories (ethnic origin, health, religion, marital status, criminal records, children) generally requires prior approval from the competent authority (MCIT/MOTC successor NCSA), or in the QFC a specific written DPO permit.
  • Special-nature personal data categories under PDPPL/QFC — generally prohibited unless prior approval from the competent department (NCSA) or, in the QFC, a written DPO permit

Pseudonymisation and anonymisationRed

No pseudonymisation or anonymisation definitions, safe-harbours, or exemptions were identified for either the mainland Law 13/2016 regime or the QFC Data Protection Regulations 2021 in the sources reviewed.

Category narrative 57 words

Mainland Law 13/2016 establishes consent as the principal lawful basis, with a withdrawal right and specific notification requirements for sensitive/special-nature data. The QFC Regulations set out lawful bases in Article 10, consent conditions in Article 11, and sensitive personal data rules in Article 12. No pseudonymisation/anonymisation safe-harbour definitions were located in either regime within the sources reviewed.

Sources and claims (11)
  1. Confirmed DataGuidance — Mainland Law No. 13 of 2016 establishes the consent of the data subject as the main legal basis for processing personal data. observed
  2. Confirmed Qatar Financial Centre Authority — Article 10 of the QFC Data Protection Regulations 2021 sets out the lawful basis or bases under which all Personal Data Processing must take place. observed
  3. Confirmed DataGuidance (unofficial translation) — Mainland Law No. 13 of 2016 provides individuals a right to withdraw their prior consent to personal data processing. observed
  4. Confirmed Qatar Financial Centre Authority — Article 11 of the QFC Data Protection Regulations 2021 sets out the conditions for valid consent to processing. observed
  5. Confirmed DataGuidance (unofficial translation) — Under mainland Law No. 13 of 2016, the Minister may impose additional precautions to protect personal data of a special nature by ministerial decision. observed
  6. Confirmed Qatar Financial Centre Authority — Article 12 of the QFC Data Protection Regulations 2021 separately governs the Processing of Sensitive Personal Data. observed
  7. Probable Gulf Times — PDPPL special categories — Processing of special/sensitive categories (ethnic origin, health, religion, marital status, criminal records, children) generally requires prior approval from the competent authority (MCIT/MOTC successor NCSA), or in the QFC a specific written DPO permit. observed
  8. Probable The Peninsula — PDPPL Article 5(1) — An individual may withdraw prior consent for personal-data processing at any time. observed
  9. Probable Aurosecurity — Qatar PDPPL — prior, informed and specific consent of the data subject; no GDPR-style legitimate-interests balancing test confirmed observed
  10. Probable https://practiceguides.chambers.com/practice-guides/data-protection-privacy-2026/qatar — Special-nature personal data categories under PDPPL/QFC — generally prohibited unless prior approval from the competent department (NCSA) or, in the QFC, a written DPO permit
  11. Confirmed Gulf Times — PDPPL Article 4 requires explicit consent for data processing absent a lawful purpose justification. observed

#

QFC rights framework is well-documented and comprehensive; mainland rights detail and statutory response deadlines are thinly sourced.

Primary frameworkQFC Data Protection Regulations 2021, Articles 16-22
Supervisory authorityQFC Data Protection Office
Traffic-light rationale — AmberQFC rights framework is well-documented and comprehensive; mainland rights detail and statutory response deadlines are thinly sourced.

Sub-modules (5)

Access rightGreen

QFC Article 16 establishes the right to access.

Claims (1):

  • The QFC Data Protection Regulations 2021 grant data subjects a right to access their personal data (Article 16).

Rectification and erasureGreen

QFC Articles 17-18 establish rights to rectification and erasure.

Claims (1):

  • The QFC Data Protection Regulations 2021 grant data subjects rights to rectification (Article 17) and erasure (Article 18).

Restriction and objectionGreen

QFC Articles 19-20 establish rights to object (including opt-out from automated decision-making/profiling) and to restriction of processing.

Claims (1):

  • The QFC Data Protection Regulations 2021 grant data subjects rights to object (Article 19), to restriction of processing (Article 20), and not to be subject to automated individual decision-making, including profiling.

Data portabilityGreen

The QFC Regulations grant data subjects a right to data portability.

Claims (3):

  • Data subjects under the QFC Data Protection Regulations 2021 are empowered with a right to data portability.
  • QFC Data Protection Rules / QDPR 2021 Article 34 — In exercising the right to data portability, the Data Subject has the right to have personal data transmitted directly from one Data Controller to another, where technically feasible.
  • QFC Data Protection Regulations 2021 — In exercising the right to data portability under Article 21(1), a data subject has the right to have personal data transmitted directly from one data controller to another, where technically feasible.

Deadlines and response windowsRed

QFC guidance references a 'without undue delay' standard for controller action on some data-subject requests, but a codified numeric response window (e.g., 30 days) was not confirmed in the sources reviewed for either regime, and no mainland deadline provision was located.

Claims (1):

  • QFC Data Protection Regulations 2021 guidance references an obligation for controllers to provide personal data to a data subject without undue delay in response to certain requests.
Category narrative 62 words

The QFC Data Protection Regulations 2021 provide a full rights suite (access, rectification, erasure, objection, restriction, portability, and a right not to be subject to solely automated decision-making including profiling) at Articles 16-22. Mainland Law 13/2016's rights framework is less granularly documented in the sources reviewed beyond the consent-withdrawal right; a specific mainland statutory response-time deadline for subject requests was not located.

Sources and claims (7)
  1. Confirmed Qatar Financial Centre Authority — The QFC Data Protection Regulations 2021 grant data subjects a right to access their personal data (Article 16). observed
  2. Confirmed Qatar Financial Centre Authority — The QFC Data Protection Regulations 2021 grant data subjects rights to rectification (Article 17) and erasure (Article 18). observed
  3. Confirmed Qatar Financial Centre — The QFC Data Protection Regulations 2021 grant data subjects rights to object (Article 19), to restriction of processing (Article 20), and not to be subject to automated individual decision-making, including profiling. observed
  4. Confirmed Qatar Financial Centre — Data subjects under the QFC Data Protection Regulations 2021 are empowered with a right to data portability. observed
  5. Uncertain Qatar Financial Centre Authority — QFC Data Protection Regulations 2021 guidance references an obligation for controllers to provide personal data to a data subject without undue delay in response to certain requests. observed
  6. Probable QFC Regulatory Authority — QFC Data Protection Rules / QDPR 2021 Article 34 — In exercising the right to data portability, the Data Subject has the right to have personal data transmitted directly from one Data Controller to another, where technically feasible. observed
  7. Confirmed QFC Data Protection Office — QFC Data Protection Regulations 2021 — In exercising the right to data portability under Article 21(1), a data subject has the right to have personal data transmitted directly from one data controller to another, where technically feasible. observed

#

Core accountability, security, ROPA and breach-notification duties are well-evidenced for the QFC; DPO-appointment obligation for firms is unresolved, and mainland retention/disposal rules were not located.

Primary frameworkQFC Data Protection Regulations 2021, Articles 25-31
Supervisory authorityQFC Data Protection Office
Traffic-light rationale — AmberCore accountability, security, ROPA and breach-notification duties are well-evidenced for the QFC; DPO-appointment obligation for firms is unresolved, and mainland retention/disposal rules were not located.

Sub-modules (7)

Accountability & DPIAGreen

QFC Article 26 requires data protection by design and by default; Article 27 requires DPIAs to be conducted in certain circumstances.

Claims (2):

  • Article 26 of the QFC Data Protection Regulations 2021 requires data protection by design and by default, and Article 27 requires Data Protection Impact Assessments in certain circumstances.
  • PDPPL Art 8 requires controllers to take administrative, technical and financial precautions when designing data-processing products/systems/services.

DPO requirementsAmber

Secondary commentary is split: one analysis states the QFC's 2023 Data Protection Rules update 'lacks requirements for a Data Protection Officer' for regulated firms, distinct from the QFC's own regulator-level Data Protection Office/Commissioner.

Claims (1):

  • Secondary legal commentary indicates the QFC's updated Data Protection Rules lack an explicit requirement for regulated firms to appoint an internal Data Protection Officer, distinct from the QFC's own regulator-level Data Protection Office.

Ropa requirementsGreen

QFC Article 30 requires a record of processing operations.

Claims (1):

  • Article 30 of the QFC Data Protection Regulations 2021 requires controllers to maintain a record of processing operations.

Joint controller arrangementsAmber

QFC Article 28 addresses Data Processor obligations and processor liability where a processor has not complied with obligations specifically directed to it; no distinct 'joint controller' provision was located in the sources reviewed for either regime.

Claims (1):

  • Article 28 of the QFC Data Protection Regulations 2021 addresses Data Processor obligations, with a Data Processor liable for damage caused by processing only where it has not complied with obligations specifically directed to Data Processors.

Security measuresGreen

QFC Article 29 sets security-of-processing requirements; mainland Law 13/2016 requires precautions against loss, damage, modification, disclosure, or unauthorized access.

Claims (3):

  • Article 29 of the QFC Data Protection Regulations 2021 sets out security-of-processing requirements for Data Controllers and Data Processors.
  • Mainland Law No. 13 of 2016 requires organizations to train data handlers and take necessary precautions to protect personal data from loss, damage, modification, disclosure, or unauthorized access.
  • PDPPL Article 13 — A security-of-processing obligation applies to controllers, and breach of Article 13's safeguards can attract a penalty of up to QAR 5 million.

Breach notificationGreen

QFC Article 31 requires notification of personal data breaches to the Data Protection Office within 72 hours, unless the controller determines the breach is unlikely to result in a risk to data subjects.

Claims (7):

  • Article 31 of the QFC Data Protection Regulations 2021 obligates Data Controllers to notify the Data Protection Office of all Personal Data Breaches within 72 hours, except where the breach is determined unlikely to result in a risk to data subjects.
  • NCSA issued Binding Decision No. 3 of 2025 against a sports-sector company for PDPPL violations.
  • PDPPL Article 13 / QFC breach notification — Article 13 of the PDPPL requires a processor to notify the controller immediately when it becomes aware of a breach of safeguards; QFC entities must generally notify the QFC Data Protection Office within 72 hours unless the breach is assessed unlikely to create risk to data subjects.
  • PDPPL Arts 13-14 require 72-hour controller-to-NCGAA breach notification.
  • PDPPL Arts 13-14 — processor must notify controller of a breach capable of causing 'serious damage' to an individual's privacy or data; all breaches should separately be reported to NCSA
  • PDPPL Art 14 requires breach notification to the individual and competent authority where serious damage may result.
  • The QFC Data Protection Office fined a QFC firm USD 150,000 on 8 October 2024 for a late breach notification and weak security.

Retention and disposalAmber

QFC guidance references a storage-limitation principle (Principle 5) requiring data not be kept longer than necessary. No mainland Law 13/2016 retention/disposal provision was located in the sources reviewed.

Claims (1):

  • QFC Data Protection Regulations guidance identifies storage limitation as one of the core processing principles (Principle 5), requiring data not be retained longer than necessary for its purpose.
Category narrative 84 words

The QFC Data Protection Regulations 2021 impose accountability duties including data protection by design/default (Article 26), DPIA obligations (Article 27), processor obligations (Article 28), security-of-processing measures (Article 29), records of processing (Article 30), and 72-hour breach notification to the DPO (Article 31). Mainland Law 13/2016 requires organizations to train data handlers and take precautions against loss, damage, modification, disclosure, or unauthorized access. Whether QFC firms must appoint an internal Data Protection Officer (distinct from the QFC's own regulator-level DPO) is contested across secondary sources.

Periodic update · new data 2026-10-11

Qatar's controller and processor duties framework under Law No. (13) of 2016 on Protecting Personal Data Privacy centres this cycle on a confirmed breach-notification obligation and a documented enforcement outcome tied to that same set of duties. Under PDPPL Articles 13 and 14, a data processor is required to immediately notify the controller upon becoming aware of a personal-data breach, and the controller is in turn required to notify the National Cyber Governance and Assurance Affairs department within 72 hours of becoming aware of the breach. This is a specific, dated obligation with an exact deadline rather than an open-ended duty, and it sits at the core of Qatar's controller/processor accountability structure.

The practical weight of this obligation is reinforced by enforcement history. In February 2026, the National Cyber Security Agency's National Data Privacy Office issued Binding Decision No. 3 of 2025 against a Qatari sports-sector company, finding violations of PDPPL Articles 8(3), 13 and 14 on the basis that the company had failed to implement adequate security measures. Article 8(3) concerns the general duty to implement appropriate security measures, while Articles 13 and 14 concern the breach-notification duty itself; a single enforcement decision citing all three articles together indicates that the regulator is prepared to find that inadequate security measures and inadequate breach-handling can be charged as related violations arising from the same underlying facts, rather than treating the security-measures duty and the notification duty as entirely separate compliance tracks. This decision predates the current cycle's recency window, having been issued in February 2026, but is carried forward here as background because it is the clearest available evidence of how Qatar's National Data Privacy Office approaches controller/processor accountability in practice, as distinct from the text of the statute alone.

The combination of a specific, time-bound breach-notification deadline and at least one documented enforcement decision applying that same provision set is a meaningfully different picture from a purely paper regime: it indicates Qatar's controller/processor duties framework has moved into an active-enforcement phase, at least with respect to breach-notification and security-measures failures, rather than remaining an untested statutory structure. This is the kind of structural, architecture-level observation that matters more than the specific sports-sector company involved: the significance lies in the demonstrated willingness of the National Data Privacy Office to issue binding decisions under these provisions, not in the identity of the sanctioned entity.

Outlook

The 72-hour controller-to-regulator breach-notification deadline under PDPPL Articles 13 and 14 is a settled, in-force obligation and no change to its substantive terms is indicated by current evidence. The more significant open question is whether the February 2026 Binding Decision No. 3 of 2025 represents an isolated enforcement action or the beginning of a more sustained enforcement pattern under the same provision set; further binding decisions citing Articles 8(3), 13 or 14, should they be issued, would be the clearest signal of a sustained active-enforcement trajectory in this domain. A documentation gap also remains around whether a formal data-protection-officer appointment threshold exists under either the PDPPL or the separate QFC Data Protection Regulations and Rules 2021, which was not located from a primary source this cycle and would be a relevant addition to the controller/processor duties picture if confirmed in a future cycle.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (16)
  1. Confirmed Qatar Financial Centre Authority — Article 26 of the QFC Data Protection Regulations 2021 requires data protection by design and by default, and Article 27 requires Data Protection Impact Assessments in certain circumstances. observed
  2. Uncertain DataGuidance — Secondary legal commentary indicates the QFC's updated Data Protection Rules lack an explicit requirement for regulated firms to appoint an internal Data Protection Officer, distinct from the QFC's own regulator-level Data Protection Office. observed
  3. Confirmed Qatar Financial Centre Authority — Article 30 of the QFC Data Protection Regulations 2021 requires controllers to maintain a record of processing operations. observed
  4. Confirmed Qatar Financial Centre Authority — Article 28 of the QFC Data Protection Regulations 2021 addresses Data Processor obligations, with a Data Processor liable for damage caused by processing only where it has not complied with obligations specifically directed to Data Processors. observed
  5. Confirmed Qatar Financial Centre Authority — Article 29 of the QFC Data Protection Regulations 2021 sets out security-of-processing requirements for Data Controllers and Data Processors. observed
  6. Confirmed MOTC — Mainland Law No. 13 of 2016 requires organizations to train data handlers and take necessary precautions to protect personal data from loss, damage, modification, disclosure, or unauthorized access. observed
  7. Confirmed Qatar Financial Centre Authority — Article 31 of the QFC Data Protection Regulations 2021 obligates Data Controllers to notify the Data Protection Office of all Personal Data Breaches within 72 hours, except where the breach is determined unlikely to result in a risk to data subjects. observed
  8. Probable Qatar Financial Centre Data Protection Office — QFC Data Protection Regulations guidance identifies storage limitation as one of the core processing principles (Principle 5), requiring data not be retained longer than necessary for its purpose. observed
  9. Probable https://www.qatarliving.com/en/article/data-protection-privacy-law-compliance-qatar-businesses — NCSA issued Binding Decision No. 3 of 2025 against a sports-sector company for PDPPL violations.
  10. Probable QFC Regulatory Authority — PDPPL Article 13 / QFC breach notification — Article 13 of the PDPPL requires a processor to notify the controller immediately when it becomes aware of a breach of safeguards; QFC entities must generally notify the QFC Data Protection Office within 72 hours unless the breach is assessed unlikely to create risk to data subjects. observed
  11. Probable https://www.recordinglaw.com/world-laws/world-data-privacy-laws/qatar-data-privacy-laws/ — PDPPL Arts 13-14 require 72-hour controller-to-NCGAA breach notification.
  12. Probable https://www.qatarliving.com/en/article/data-protection-privacy-law-compliance-qatar-businesses — PDPPL Article 13 — A security-of-processing obligation applies to controllers, and breach of Article 13's safeguards can attract a penalty of up to QAR 5 million.
  13. Probable Wattlecorp — PDPPL Arts 13-14 — processor must notify controller of a breach capable of causing 'serious damage' to an individual's privacy or data; all breaches should separately be reported to NCSA observed
  14. Confirmed Chambers and Partners — PDPPL Art 8 requires controllers to take administrative, technical and financial precautions when designing data-processing products/systems/services. observed
  15. Probable https://www.qatarliving.com/en/article/data-protection-privacy-law-compliance-qatar-businesses — PDPPL Art 14 requires breach notification to the individual and competent authority where serious damage may result.
  16. Probable QFC Regulatory Authority — The QFC Data Protection Office fined a QFC firm USD 150,000 on 8 October 2024 for a late breach notification and weak security. observed

#

Transfer mechanisms, adequacy-list governance, and SCC/BCR uptake are well-evidenced for the QFC; adequacy received from other regimes and a formal TIA requirement are unconfirmed gaps.

Primary frameworkQFC Data Protection Regulations 2021, Articles 23-24
Supervisory authorityQFC Data Protection Office
Traffic-light rationale — AmberTransfer mechanisms, adequacy-list governance, and SCC/BCR uptake are well-evidenced for the QFC; adequacy received from other regimes and a formal TIA requirement are unconfirmed gaps.

Sub-modules (6)

Transfer mechanismsGreen

QFC transfers out of the free zone require an adequate jurisdiction, QFC SCCs, or a specific Article 24 derogation/limited-circumstances basis.

Claims (6):

  • Transfers of Personal Data outside the QFC must rely on an adequate jurisdiction, appropriate safeguards such as QFC Standard Contractual Clauses, or a specific derogation under Article 24 of the QFC Data Protection Regulations 2021.
  • PDPPL Article 15 — Article 15 of the PDPPL prevents a controller from restricting cross-border personal-data flows unless overseas processing would breach the PDPPL or risk serious damage to the data or the individual's privacy.
  • QDPR 2021 Article 23 — A transfer of personal data to a recipient outside the QFC may take place if the Data Protection Office has decided that jurisdiction has an adequate level of protection; no specific authorisation or notification is required.
  • PDPPL Article 15 — A controller must not take any decision or measure that may limit cross-border data flow, unless the processing breaches the law or may cause serious damage to personal data or privacy.
  • Law No. 13 of 2016, Article 15 — PDPPL Article 15 restricts the transfer of personal data outside Qatar, permitting restriction where the receiving jurisdiction's processing would breach the Law or cause serious damage, with the Compliance and Data Protection Department assessing adequacy of the receiving jurisdiction.
  • PDPPL Art 15 — transfer of personal data outside Qatar requires prior approval from CDP/NCSA, or a statutory exception; one secondary source separately describes a 'should not block unless violation/serious violation' standard

Adequacy receivedRed

No adequacy decision received by mainland Qatar or the QFC from the EU, UK, or other major regimes was identified in the sources reviewed.

Adequacy grantedGreen

The QFC Data Protection Office maintains and can amend a published list of jurisdictions it has determined offer an adequate level of protection for outbound transfers.

Claims (2):

  • The QFC Data Protection Office publishes and may amend a list of jurisdictions determined to offer an adequate level of protection for personal data transferred out of the QFC.
  • QFC Data Protection Office — No additional authorisation from, or notification to, the DPO is required for a transfer of personal data to a recipient jurisdiction outside the QFC that the DPO has assessed as adequate; transfers to non-adequate jurisdictions instead fall under the Article 24 safeguard regime.

SCCs and BCRsGreen

The QFC provides its own Standard Contractual Clauses, and its 2023 Data Protection Rules introduced new Binding Corporate Rules requirements; the QFC, DIFC and ADGM have mutually recognized each other's data protection frameworks.

Claims (2):

  • The QFC's 2023 Data Protection Rules update introduced new Binding Corporate Rules requirements for data transfers, alongside the QFC's own Standard Contractual Clauses.
  • The QFC, DIFC, and ADGM free zones have mutually recognized each other's data protection frameworks, simplifying cross-border data flows between them.

Transfer impact assessmentAmber

No formal Transfer Impact Assessment requirement analogous to post-Schrems II EU practice was identified for either the mainland or QFC regime, though a QFC DPO thematic review flagged firms' cross-border transfer risk-identification practices as an area of continued supervisory focus.

Claims (1):

  • A QFC Data Protection Office thematic review found that a majority but not all firms have fully implemented processes to identify the jurisdictions to which they transfer personal data out of the QFC, indicating supervisory focus on transfer risk assessment without a codified TIA mandate.

Data localisationGreen

Mainland Law 13/2016 takes the position that a controller should not block a cross-border data flow unless it would violate the Law or seriously violate a data subject's right to privacy, implying no blanket data-localisation mandate.

Claims (3):

  • Mainland Law No. 13 of 2016 provides that a data controller should not block a cross-border data flow unless it would result in a violation of the Law or a serious violation of the data subject's right to privacy.
  • Qatar Central Bank Data Handling and Protection Regulation (2025) — The QCB's Data Handling and Protection Regulation (issued February 2025) requires financial institutions it supervises to keep the primary storage and processing environment for personal, sensitive personal and sensitive financial information inside Qatar (provision 7.6), permitting an offshore primary environment only with the QCB's explicit prior approval (provision 7.7).
  • The Qatar Central Bank requires licensed payment service providers to process and store all payment data within Qatar.
Category narrative 120 words

The QFC Regulations require transfers out of the QFC to rely on an adequate jurisdiction (per a DPO-maintained and publishable list), QFC Standard Contractual Clauses, Binding Corporate Rules (introduced via the 2023 Rules update), or a specific Article 24 derogation. The QFC has also established mutual recognition of data protection frameworks with the DIFC and ADGM free zones. Mainland Law 13/2016 takes a distinct approach: a controller should not block a cross-border flow unless it would violate the Law or seriously violate a data subject's privacy right. No evidence was found of Qatar (mainland or QFC) having received an adequacy decision from the EU/UK, nor of a Transfer Impact Assessment (TIA) obligation analogous to Schrems II practice in either regime.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (14)
  1. Confirmed Qatar Financial Centre — Transfers of Personal Data outside the QFC must rely on an adequate jurisdiction, appropriate safeguards such as QFC Standard Contractual Clauses, or a specific derogation under Article 24 of the QFC Data Protection Regulations 2021. observed
  2. Confirmed Qatar Financial Centre Authority — The QFC Data Protection Office publishes and may amend a list of jurisdictions determined to offer an adequate level of protection for personal data transferred out of the QFC. observed
  3. Confirmed DataGuidance — The QFC's 2023 Data Protection Rules update introduced new Binding Corporate Rules requirements for data transfers, alongside the QFC's own Standard Contractual Clauses. observed
  4. Probable DataGuidance — The QFC, DIFC, and ADGM free zones have mutually recognized each other's data protection frameworks, simplifying cross-border data flows between them. observed
  5. Probable Qatar Financial Centre Authority — A QFC Data Protection Office thematic review found that a majority but not all firms have fully implemented processes to identify the jurisdictions to which they transfer personal data out of the QFC, indicating supervisory focus on transfer risk assessment without a codified TIA mandate. observed
  6. Confirmed DataGuidance — Mainland Law No. 13 of 2016 provides that a data controller should not block a cross-border data flow unless it would result in a violation of the Law or a serious violation of the data subject's right to privacy. observed
  7. Probable Gulf Times — Qatar Central Bank Data Handling and Protection Regulation (2025) — The QCB's Data Handling and Protection Regulation (issued February 2025) requires financial institutions it supervises to keep the primary storage and processing environment for personal, sensitive personal and sensitive financial information inside Qatar (provision 7.6), permitting an offshore primary environment only with the QCB's explicit prior approval (provision 7.7). observed
  8. Probable QFC Regulatory Authority — PDPPL Article 15 — Article 15 of the PDPPL prevents a controller from restricting cross-border personal-data flows unless overseas processing would breach the PDPPL or risk serious damage to the data or the individual's privacy. observed
  9. Probable Gulf Times — QDPR 2021 Article 23 — A transfer of personal data to a recipient outside the QFC may take place if the Data Protection Office has decided that jurisdiction has an adequate level of protection; no specific authorisation or notification is required. observed
  10. Probable https://www.qatarliving.com/en/article/data-protection-privacy-law-compliance-qatar-businesses — PDPPL Article 15 — A controller must not take any decision or measure that may limit cross-border data flow, unless the processing breaches the law or may cause serious damage to personal data or privacy.
  11. Uncertain DataGuidance — Law No. 13 of 2016, Article 15 — PDPPL Article 15 restricts the transfer of personal data outside Qatar, permitting restriction where the receiving jurisdiction's processing would breach the Law or cause serious damage, with the Compliance and Data Protection Department assessing adequacy of the receiving jurisdiction. observed
  12. Disputed DataGuidance — PDPPL Art 15 — transfer of personal data outside Qatar requires prior approval from CDP/NCSA, or a statutory exception; one secondary source separately describes a 'should not block unless violation/serious violation' standard observed
  13. Probable Qatar Financial Centre Legislation Portal (Thomson Reuters, on behalf of QFC Authority) — QFC Data Protection Office — No additional authorisation from, or notification to, the DPO is required for a transfer of personal data to a recipient jurisdiction outside the QFC that the DPO has assessed as adequate; transfers to non-adequate jurisdictions instead fall under the Article 24 safeguard regime. observed
  14. Probable Finance Magnates — The Qatar Central Bank requires licensed payment service providers to process and store all payment data within Qatar. observed

#

Only the financial-sector overlay (QFC) and a limited employment-data example are evidenced; health, credit, education, and insurance sub-modules are unpopulated.

Primary frameworkQFC Data Protection Regulations 2021 (financial free-zone overlay)
Supervisory authorityQFC Data Protection Office
Traffic-light rationale — RedOnly the financial-sector overlay (QFC) and a limited employment-data example are evidenced; health, credit, education, and insurance sub-modules are unpopulated.

Sub-modules (7)

Financial sector overlayGreen

The QFC Data Protection Regulations 2021 constitute a dedicated financial free-zone data-protection overlay, separate from and not displaced by mainland Law 13/2016.

Claims (3):

  • The QFC Data Protection Regulations 2021 operate as a separate, GDPR-aligned financial free-zone data-protection regime administered by the QFC Authority/Data Protection Office, distinct from mainland Law No. 13 of 2016.
  • The Qatar Central Bank's AI Guideline regulates AI use by QCB-licensed entities, focusing on governance, risk management, and customer interactions, forming an adjacent regulatory layer for financial-sector data processing.
  • Law No. 18 of 2025 (AML/CFT amendment, Art 29) — consistency with personal data protection measures when developing AML/CFT/PWMD actions

Health sector overlayRed

No dedicated health-sector data-protection overlay was identified for mainland Qatar or the QFC.

Telecoms and eprivacyRed

No dedicated telecoms/ePrivacy overlay distinct from Law 13/2016's general direct-marketing consent rule was identified.

Employment dataAmber

QFC guidance illustrates employer obligations to provide an employee privacy notice consistent with Articles 14-15 transparency requirements.

Claims (1):

  • QFC Data Protection Regulations guidance illustrates that employers must provide an employee privacy notice consistent with the transparency requirements of Articles 14 and 15.

Credit and scoringRed

No credit-scoring-specific data-protection rules were identified.

educationRed

No education-sector-specific data-protection rules were identified beyond the general children's-website provisions addressed under children_and_vulnerable_groups.

insuranceRed

No insurance-sector-specific data-protection rules were identified.

Category narrative 86 words

The QFC itself functions as Qatar's principal financial-sector data-protection overlay, operating a GDPR-aligned regime distinct from mainland Law 13/2016 for firms licensed within the free zone. The Qatar Central Bank (QCB) separately maintains an AI Guideline for QCB-licensed entities addressing governance, risk management, and customer interactions, which is adjacent to but not itself a data-protection instrument. QFC guidance illustrates employment-data obligations (e.g., employee privacy notices under Articles 14-15). No dedicated health-sector, credit-scoring, education-sector, or insurance-sector data-protection overlay was identified for either regime in the sources reviewed.

Sources and claims (5)
  1. Confirmed Qatar Financial Centre Authority — The QFC Data Protection Regulations 2021 operate as a separate, GDPR-aligned financial free-zone data-protection regime administered by the QFC Authority/Data Protection Office, distinct from mainland Law No. 13 of 2016. observed
  2. Probable DataGuidance — The Qatar Central Bank's AI Guideline regulates AI use by QCB-licensed entities, focusing on governance, risk management, and customer interactions, forming an adjacent regulatory layer for financial-sector data processing. observed
  3. Confirmed Qatar Financial Centre Data Protection Office — QFC Data Protection Regulations guidance illustrates that employers must provide an employee privacy notice consistent with the transparency requirements of Articles 14 and 15. observed
  4. Probable QFC Regulatory Authority — Qatar data governance framework — No dedicated law, case law or published guidance establishes a cross-sector non-personal-data governance or data-access-sharing framework comparable to the EU Data Act in Qatar; available instruments address only personal-data protection. observed
  5. Probable QFCRA — Law No. 18 of 2025 (AML/CFT amendment, Art 29) — consistency with personal data protection measures when developing AML/CFT/PWMD actions observed

#

Only direct marketing is evidenced; the remaining five sub-modules (cookies, dark patterns, opt-out signals, clean rooms, cross-context advertising) are unpopulated gaps.

Primary frameworkLaw No. 13 of 2016 (mainland) - direct marketing provision only
Traffic-light rationale — RedOnly direct marketing is evidenced; the remaining five sub-modules (cookies, dark patterns, opt-out signals, clean rooms, cross-context advertising) are unpopulated gaps.

Sub-modules (6)

Cookies and trackersRed

No dedicated cookie/tracker consent regime was identified.

Dark patternsRed

No dark-pattern prohibition was identified.

Opt out signalsRed

No recognized universal opt-out signal (e.g., Global Privacy Control) mechanism was identified.

Clean rooms and dcrRed

No clean-room or data-collaboration-room rules were identified.

Cross context advertisingRed

No 'sale'/'share' or cross-context-advertising concept analogous to CPRA was identified.

Direct marketingGreen

Mainland Law 13/2016 bans sending direct electronic marketing messages without the recipient's prior consent.

Claims (1):

  • Under mainland Law No. 13 of 2016, businesses are banned from sending direct marketing messages electronically without first obtaining an individual's prior consent.
Category narrative 42 words

Mainland Law 13/2016 prohibits sending direct electronic marketing messages without prior consent. No cookie/tracker-specific consent regime, dark-pattern prohibition, recognized opt-out signal (e.g., GPC), clean-room framework, or cross-context-advertising ('sale'/'share') concept was identified for either the mainland or QFC regime in the sources reviewed.

Sources and claims (1)
  1. Confirmed MOTC — Under mainland Law No. 13 of 2016, businesses are banned from sending direct marketing messages electronically without first obtaining an individual's prior consent. observed

#

Profiling/ADM restriction is confirmed for the QFC; AI risk-assessment, biometric, genetic, and surveillance-carveout sub-modules are largely unconfirmed or absent.

Primary frameworkQFC Data Protection Regulations 2021, Article 19 (right to object, including to automated decision-making)
Supervisory authorityQFC Data Protection Office
Traffic-light rationale — AmberProfiling/ADM restriction is confirmed for the QFC; AI risk-assessment, biometric, genetic, and surveillance-carveout sub-modules are largely unconfirmed or absent.

Sub-modules (6)

Profiling restrictionsGreen

QFC data subjects have a right not to be subject to automated individual decision-making, including profiling.

Claims (1):

  • Data subjects under the QFC Data Protection Regulations 2021 have a right not to be subject to automated individual decision-making, including profiling.

Automated decision making transparencyAmber

General QFC transparency obligations (Articles 13-15) require controllers to inform data subjects about processing, but no distinct requirement to disclose ADM logic/explanation was confirmed in the sources reviewed.

AI risk assessmentsAmber

Qatar's National AI Strategy, the Cabinet-established Artificial Intelligence Committee, and NCSA/QCB AI guidance address AI governance and risk management generally, but are not data-protection-specific AI risk-assessment mandates analogous to the EU AI Act.

Claims (2):

  • Qatar's National AI Strategy and the Artificial Intelligence Committee established under Cabinet Decision No. 10 of 2021, together with NCSA and QCB AI guidance, address AI governance and risk management generally but are not data-protection-specific AI risk-assessment mandates.
  • NCSA Guidelines for Secure Adoption and Usage of Artificial Intelligence — AI systems that process personal data must comply with PDPPL requirements for data minimisation, purpose limitation and lawful processing, and must incorporate auditability, traceability and documentation.

Biometric regimeRed

No dedicated biometric-data regime (facial recognition, fingerprint, gait) was identified.

Claims (2):

  • QFC special categories — In the QFC, the special-categories definition additionally covers biometric data, genetic data and data relating to criminal convictions, beyond the mainland PDPPL's enumerated categories.
  • QFC Data Protection Regulations 2021 — biometric data, genetic data and data relating to criminal convictions, in addition to the mainland PDPPL special-nature list

Genetic dataRed

No dedicated genetic-data regime was identified, though mainland 'special nature' data provisions may implicitly capture genetic data without explicit confirmation.

State surveillance carveoutsRed

Mainland Law 13/2016 does not apply to personal data gathered for official surveys and statistics, which is scope-related rather than a dedicated state-surveillance/national-security carve-out; no explicit surveillance carve-out or its limits was identified.

Category narrative 79 words

The QFC Data Protection Regulations 2021 grant data subjects a right not to be subject to automated individual decision-making, including profiling. Qatar has separately developed a National AI Strategy and an Artificial Intelligence Committee (Cabinet Decision No. 10 of 2021), and the NCSA and QCB have issued AI-adoption/AI-governance guidance, though these are general AI-policy instruments rather than data-protection-specific AI risk-assessment mandates. No dedicated biometric-data regime, genetic-data regime, or explicit state-surveillance carve-out distinct from the mainland statistics exemption was identified.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (5)
  1. Confirmed Qatar Financial Centre — Data subjects under the QFC Data Protection Regulations 2021 have a right not to be subject to automated individual decision-making, including profiling. observed
  2. Probable DataGuidance — Qatar's National AI Strategy and the Artificial Intelligence Committee established under Cabinet Decision No. 10 of 2021, together with NCSA and QCB AI guidance, address AI governance and risk management generally but are not data-protection-specific AI risk-assessment mandates. observed
  3. Probable https://practiceguides.chambers.com/practice-guides/data-protection-privacy-2026/qatar — NCSA Guidelines for Secure Adoption and Usage of Artificial Intelligence — AI systems that process personal data must comply with PDPPL requirements for data minimisation, purpose limitation and lawful processing, and must incorporate auditability, traceability and documentation.
  4. Probable Gulf Times — QFC special categories — In the QFC, the special-categories definition additionally covers biometric data, genetic data and data relating to criminal convictions, beyond the mainland PDPPL's enumerated categories. observed
  5. Probable https://practiceguides.chambers.com/practice-guides/data-protection-privacy-2026/qatar — QFC Data Protection Regulations 2021 — biometric data, genetic data and data relating to criminal convictions, in addition to the mainland PDPPL special-nature list

#

Only the mainland parental-consent rule for children's websites is evidenced; the remaining four sub-modules are unpopulated gaps.

Primary frameworkLaw No. 13 of 2016, Article 17 (mainland)
Traffic-light rationale — RedOnly the mainland parental-consent rule for children's websites is evidenced; the remaining four sub-modules are unpopulated gaps.

Sub-modules (5)

Age verificationRed

No age-verification mechanism was identified.

Minor profiling bansRed

No minor-specific profiling ban was identified.

Education settingsRed

No education-settings-specific data-protection rule was identified.

Dependent adultsRed

No dependent-adults (elderly, mentally incapacitated) data-protection provision was identified.

Category narrative 55 words

Mainland Law No. 13 of 2016 requires operators of websites related to children to publish a policy on managing minors' information and to obtain parental consent before processing a child's data. No age-of-consent threshold distinct from this parental-consent rule, minor-profiling ban, education-settings-specific rule, or dependent-adults protection was identified for either the mainland or QFC regime.

Sources and claims (1)
  1. Confirmed MOTC — Under Article 17 of mainland Law No. 13 of 2016, the owner or operator of any website related to children must publish a policy on how it manages minors' information and must obtain the consent of the child's parent when processing that information. observed

#

Regulator powers, penalties, and enforcement activity are well-evidenced for the QFC; recent (180-day) developments, regulator funding/capacity, and collective-redress mechanisms are unconfirmed gaps.

Primary frameworkQFC Data Protection Regulations 2021, Articles 33-36
Supervisory authorityQFC Data Protection Office
Traffic-light rationale — AmberRegulator powers, penalties, and enforcement activity are well-evidenced for the QFC; recent (180-day) developments, regulator funding/capacity, and collective-redress mechanisms are unconfirmed gaps.

Sub-modules (6)

Regulator powers and penaltiesGreen

QFC Article 33 grants the Data Protection Office investigative/enforcement powers; Article 36 sets general conditions for imposing penalties, with a maximum fine of USD 1.5 million. Mainland Law 13/2016 voids contracts concluded in violation of the Law and permits corporate liability for third-party conduct.

Claims (6):

  • Article 33 of the QFC Data Protection Regulations 2021 grants the Data Protection Office investigative and enforcement powers, and Article 36 sets general conditions for imposing penalties, with a maximum fine of USD 1.5 million.
  • Mainland Law No. 13 of 2016 renders contracts or agreements concluded in violation of the Law null and void, and prescribes that corporate entities can be found liable for actions of third parties carried out on the organization's behalf.
  • PDPPL penalty bands range QAR 1,000,000-5,000,000 with no criminal imprisonment.
  • PDPPL penalty provision — QAR 1,000,000 to QAR 5,000,000 for violations
  • PDPPL fines range QAR 1M-5M by article; QFC penalty up to USD 1.5M per infringed provision.
  • PDPPL violations can attract fines up to QAR 1 million generally, rising to QAR 5 million for security/special-nature/children's-data violations; QFC entities face up to USD 1.5 million per infringed provision.

Enforcement activity indexAmber

The QFC DPO's first enforcement decision (October 2024) imposed a reprimand and USD 150,000 fine. Mainland NCSA reportedly imposed corrective measures on a sports company following a data breach.

Claims (4):

  • In October 2024, the QFC Data Protection Office imposed a reprimand and a USD 150,000 financial penalty on a QFC-licensed firm following a data breach involving late notification, security failures, and inadequate oversight, the first enforcement action of its kind in Qatar.
  • The NCSA imposed corrective measures on a sports company for violating mainland data privacy laws following a data breach.
  • NCSA Compliance and Data Protection Department (CDP/NDPO) — Substantially more active in enforcement since 2024, with three documented enforcement actions spanning ICT, e-commerce and construction sectors.
  • NDPO Binding Decision No. 1 of 2024 found an ICT-sector company violated PDPPL Arts 4, 8, 10 and 11.

Regulator funding and capacityRed

No regulator funding or headcount data was identified for either the NCSA's data-protection function or the QFC Data Protection Office.

Collective redress and class actionsRed

No collective-redress or class-action mechanism for data-protection claims was identified in either regime.

Private right of actionGreen

QFC Article 34 grants a right to lodge a complaint with the Data Protection Office, and Article 35 grants a right to compensation and establishes liability for processing that infringes the Regulations.

Claims (2):

  • Article 34 of the QFC Data Protection Regulations 2021 grants data subjects a right to lodge a complaint with the Data Protection Office, and Article 35 grants a right to compensation and establishes liability for processing that infringes the Regulations.
  • Individuals (data subjects) — Individuals can complain where they believe an organisation has failed to comply with the PDPPL, raising the issue with the controller and, per NCSA guidance, with the competent privacy authority.

Recent developments 180dRed

No development strictly within the 180 days preceding this run (since approximately February 2026) was located. The most recent identified QFC supervisory activity is a Data Protection Office thematic review of firms' cross-border transfer practices, published in December 2024, which falls outside the 180-day window.

Claims (1):

  • National Cyber Security Agency (NCSA) — NCSA publicly reaffirmed PDPPL's core personal-data-privacy-protection principles on 6 September 2026 via an awareness initiative.
Category narrative 168 words

The QFC Data Protection Office holds investigative and enforcement powers under Article 33, with general penalty conditions set at Article 36 and a maximum fine of USD 1.5 million; Article 34 grants a right to lodge a complaint with the DPO and Article 35 a right to compensation. The DPO issued its first enforcement action in October 2024, a reprimand plus a USD 150,000 fine against a QFC-licensed firm for breach-notification and security failures. On the mainland, Law 13/2016 renders contracts concluded in violation of the Law null and void and can hold corporate entities liable for third-party actions, and the NCSA has reportedly imposed corrective measures on at least one company following a data breach. No collective-redress/class-action mechanism, explicit private right of action distinct from the QFC complaint/compensation route, or regulator funding/headcount data was identified. No development within the strict 180-day window preceding this run (i.e., since approximately February 2026) was located; the most recent identified enforcement/supervisory activity (a QFC DPO thematic review) dates to December 2024.

Periodic update · new data 2026-10-25

Qatar's National Cyber Security Agency, acting through its Compliance and Data Protection Department, is reported to have become substantially more active in enforcement since 2024, with three documented enforcement actions identified across the ICT, e-commerce and construction sectors. This characterisation is drawn from secondary commentary rather than from a confirmed, directly sourced NCSA enforcement register, and should be read with that provenance in mind: the underlying actions themselves have not been independently verified from a primary regulatory source, so the trend is reported rather than confirmed.

Alongside this reported enforcement uptick, the NCSA engaged in a more directly evidenced public-facing activity on 6 September 2026, when it reaffirmed the Personal Data Privacy Protection Law's core personal-data-privacy-protection principles through a dedicated awareness initiative. This is a lower-materiality development than the enforcement-trend commentary, but it is sourced to contemporaneous Tier-2 reporting and confirms that the regulator continued to engage publicly with the statute's framework in the period covered.

Read together, the two developments describe a regulator that is simultaneously reported to be escalating its enforcement posture across a widening range of sectors, while also continuing to invest in public education about the underlying law's principles. The sectoral spread reported for the enforcement actions, touching ICT, e-commerce and construction, suggests that NCSA enforcement attention is not confined to a single sector type, though the absence of a primary enforcement register means the specific facts, penalties and legal bases of the three reported actions cannot be set out here.

The redress side of this module, meaning the mechanisms by which an individual affected by a PDPPL breach can seek a remedy, was not independently confirmed from primary sources, and no finding is made on that point.

Outlook

Whether the reported enforcement increase since 2024 is sustained or represents a cluster of several actions concentrated in a shorter period remains an open question pending the availability of a primary NCSA enforcement log. The 6 September 2026 awareness reaffirmation is confirmed and suggests continued regulator engagement with public understanding of the PDPPL's principles, a pattern that may recur in future reporting periods as the NCSA continues to build out its compliance and enforcement function.

1 earlier distinct update
Periodic update · new data 2026-10-18

Qatar's National Cyber Security Agency, acting through its Compliance and Data Protection Department, is reported to have become substantially more active in enforcement since 2024, with three documented enforcement actions identified across the ICT, e-commerce and construction sectors. This characterisation is drawn from secondary commentary rather than from a confirmed, directly sourced NCSA enforcement register, and should be read with that provenance in mind: the underlying actions themselves have not been independently verified from a primary regulatory source this cycle, so the trend is reported rather than confirmed.

Alongside this reported enforcement uptick, the NCSA engaged in a more directly evidenced public-facing activity on 6 September 2026, when it reaffirmed the Personal Data Privacy Protection Law's core personal-data-privacy-protection principles through a dedicated awareness initiative. This is a lower-materiality development than the enforcement-trend commentary, but it is sourced to contemporaneous Tier-2 reporting and confirms that the regulator continued to engage publicly with the statute's framework in the period covered.

Read together, the two developments describe a regulator that is simultaneously reported to be escalating its enforcement posture across a widening range of sectors, while also continuing to invest in public education about the underlying law's principles. The sectoral spread reported for the enforcement actions, touching ICT, e-commerce and construction, suggests that NCSA enforcement attention is not confined to a single sector type, though the absence of a primary enforcement register means the specific facts, penalties and legal bases of the three reported actions cannot be set out here.

The redress side of this module, meaning the mechanisms by which an individual affected by a PDPPL breach can seek a remedy, was not independently confirmed from primary sources this cycle, and no finding is made on that point.

Outlook

Whether the reported enforcement increase since 2024 is sustained or represents a cluster of several actions concentrated in a shorter period remains an open question pending the availability of a primary NCSA enforcement log. The 6 September 2026 awareness reaffirmation is confirmed and suggests continued regulator engagement with public understanding of the PDPPL's principles, a pattern that may recur in future reporting periods as the NCSA continues to build out its compliance and enforcement function.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (13)
  1. Confirmed DataGuidance — Article 33 of the QFC Data Protection Regulations 2021 grants the Data Protection Office investigative and enforcement powers, and Article 36 sets general conditions for imposing penalties, with a maximum fine of USD 1.5 million. observed
  2. Confirmed DataGuidance — Mainland Law No. 13 of 2016 renders contracts or agreements concluded in violation of the Law null and void, and prescribes that corporate entities can be found liable for actions of third parties carried out on the organization's behalf. observed
  3. Confirmed Qatar Financial Centre — In October 2024, the QFC Data Protection Office imposed a reprimand and a USD 150,000 financial penalty on a QFC-licensed firm following a data breach involving late notification, security failures, and inadequate oversight, the first enforcement action of its kind in Qatar. observed
  4. Probable DataGuidance — The NCSA imposed corrective measures on a sports company for violating mainland data privacy laws following a data breach. observed
  5. Confirmed Qatar Financial Centre Authority — Article 34 of the QFC Data Protection Regulations 2021 grants data subjects a right to lodge a complaint with the Data Protection Office, and Article 35 grants a right to compensation and establishes liability for processing that infringes the Regulations. observed
  6. Uncertain https://www.recordinglaw.com/world-laws/world-data-privacy-laws/qatar-data-privacy-laws/ — NCSA Compliance and Data Protection Department (CDP/NDPO) — Substantially more active in enforcement since 2024, with three documented enforcement actions spanning ICT, e-commerce and construction sectors.
  7. Probable QFC Regulatory Authority — Individuals (data subjects) — Individuals can complain where they believe an organisation has failed to comply with the PDPPL, raising the issue with the controller and, per NCSA guidance, with the competent privacy authority. observed
  8. Probable https://www.qatarliving.com/en/article/data-protection-privacy-law-compliance-qatar-businesses — PDPPL penalty bands range QAR 1,000,000-5,000,000 with no criminal imprisonment.
  9. Probable The Peninsula — National Cyber Security Agency (NCSA) — NCSA publicly reaffirmed PDPPL's core personal-data-privacy-protection principles on 6 September 2026 via an awareness initiative. observed
  10. Probable Securiti — PDPPL penalty provision — QAR 1,000,000 to QAR 5,000,000 for violations observed
  11. Probable Qatar Living — PDPPL fines range QAR 1M-5M by article; QFC penalty up to USD 1.5M per infringed provision. observed
  12. Probable The Peninsula — NDPO Binding Decision No. 1 of 2024 found an ICT-sector company violated PDPPL Arts 4, 8, 10 and 11. observed
  13. Probable Qatar Living — PDPPL violations can attract fines up to QAR 1 million generally, rising to QAR 5 million for security/special-nature/children's-data violations; QFC entities face up to USD 1.5 million per infringed provision. observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 95 claim(s) (95 category placement(s)), 40 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: not upheld (14 confirmed against the cited source; 1 contradicted by the cited source; 5 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (38 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsaccess right
Art. 14Data Subject Rightsaccess right
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrestriction and objection
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy granted
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacytransfer mechanisms
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressprivate right of action
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 81Enforcement & Redressprivate right of action
Art. 82Enforcement & Redressregulator powers and penalties
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties