Regulation · Qatar
Qatar PDPPL
At a glance
- Jurisdiction
- Qatar (outside the Qatar Financial Centre)
- Supervisory authority
- National Cyber Security Agency
- In force
- Issued 3 November 2016
- Official name
- Law No. (13) of 2016 on Protecting Personal Data Privacy
What the PDPPL asks of you, article by article
How GovernID fits: Qatar’s PDPPL asks you to tell people before you process, process only with consent or for a lawful purpose, protect the data and report serious breaches. GovernID builds that into collection. Your RoPA records each activity, privacy notices are generated from it in Arabic and English, and each record collected through GovernID carries the notice, consent and retention period that applied on the day it arrived.
Good to know: The Qatar Financial Centre has its own data protection regulations. Data of a special nature needs permission from the competent department before processing.
| Requirement | Article | What GovernID does | What stays with you |
|---|---|---|---|
| Scope. The law applies to personal data processed electronically, or collected to be processed electronically. | Art. 2 | Every form connected to GovernID is part of your electronic processing record from the first field. | Deciding whether the law applies to you. |
| Transparency, honesty and dignity. Personal data may be processed only in a transparent and honest way that respects human dignity. | Art. 3, 8(1) | Each processing activity in your RoPA records its purpose, data categories, legal basis and retention period. Every field is classified before the first record arrives, and each record keeps the terms it was collected under. | Deciding purposes. |
| Consent or a lawful purpose. Process only with the person’s consent, unless the processing is necessary for a lawful purpose. | Art. 4 | Legal bases come ready in the Privacy Taxonomy. Each activity records its basis, and each record keeps the basis that applied on the day it arrived. | Deciding which ground applies. |
| Information before processing. Before processing starts, tell people who the controller is, the lawful purposes, and how the data will be processed and disclosed. | Art. 9 | Privacy notices are generated from the RoPA with these items and served as a link at the moment of collection. Each record keeps the notice version the person saw. | Approving the notice and keeping it accurate. |
| Individual rights. People can withdraw consent, object, ask for erasure or correction, access their data, and be told when inaccurate data was disclosed. | Art. 5, 6 | In the Privacy Center, people see the records that contain their verified contact details, withdraw consent, object to processing and get an instant preliminary report. DSAR Automation finds every record of a person across connected collection points. | Handling access, erasure and correction requests, and requests made through other channels. |
| Purpose, accuracy and retention. Collect only data relevant and adequate for the purpose, keep it accurate and up to date, and keep it no longer than needed. | Art. 10 | Retention periods are set in the RoPA. Each record gets its own end date, records past it can be listed at any time, and GovernID’s own copy is marked for destruction when its period ends. | Deleting the data in your own systems, and keeping other data accurate. |
| Privacy by design. Take privacy controls into account when designing, changing or developing products, systems and services. | Art. 8(2) | Forms connect to GovernID so the notice, consent and classification are set before collection starts. Each field is linked to a data category approved for that activity. | Designing systems. |
| Internal procedures. Review privacy measures before new processing, identify responsible processors, train them, set up systems for complaints and requests, manage data and audit compliance. | Art. 11 | Every new or changed activity goes through the RoPA wizard and is confirmed by its process owner. Requests made in the Privacy Center reach your team at once, with their date, and consent withdrawals are tracked until handled. | Running training, audits and your complaint procedure. |
| Processors and disclosures. Make sure disclosures and transfers to processors fit the lawful purpose, and check processors follow your instructions. | Art. 11(8), 12 | Processors and other recipients are recorded in each activity and shown as processing flows. | Choosing and monitoring processors. |
| Security of processing. Protect personal data against loss, damage, change, disclosure and misuse, with measures that match its importance. Processors must report breaches to you at once. | Art. 13 | Safeguards are recorded for each activity and storage location, and Corporate Privacy Memory keeps how each activity looked on any past date. | Implementing and testing the measures. |
| Breach notification. Inform the people affected and the competent department of a breach that may cause serious damage to their data or privacy. | Art. 14 | Breach Impact Analysis shows which activities used the affected system, which data was kept there and which safeguards applied. | Assessing the breach and notifying. |
| Cross-border data flows. You may not restrict cross-border data flows unless the processing breaches the law or may cause serious damage to the data or the person’s privacy. | Art. 15 | Transfers are recorded in each activity, appear in the privacy notice built from it, and GovernID recommends a DPIA when data is sent abroad. | Assessing each transfer. |
| Data of a special nature. Data on ethnic origin, children, health, religion, marital relations and criminal offences can be processed only with permission from the competent department. | Art. 16 | Sensitive fields are marked in the RoPA and at collection, and GovernID recommends a DPIA for activities that use them. | Getting the permission. |
| Children’s websites. Websites aimed at children must publish how they use children’s data and get the guardian’s explicit consent. | Art. 17 | Consent is recorded with the text and version shown and the dates it was given and withdrawn. | Verifying the guardian. |
| Direct marketing. Electronic marketing needs prior consent, must say who sent it and must offer an easy way to stop it. | Art. 22 | Marketing consent is its own box with its own text, never pre-ticked, and people withdraw it in the Privacy Center. | Running campaigns that honour withdrawals. |
This page summarises the law to show where GovernID supports your work. It is not legal advice; your legal counsel decides how the law applies to your company.
Right of access: what a response must include
Under Article 6 PDPPL, an individual may access their personal data at any time and ask the controller to review it.
| The response must include | Article |
|---|---|
| Notification that personal data is processed, and the purposes | Art. 6(1) |
| Notification of any disclosure of inaccurate personal data | Art. 6(2) |
| A copy of the personal data, for a fee not exceeding the service charge | Art. 6(3) |
Deadline: 30 calendar days, set by the NCSA Individuals' Rights Guideline rather than the law.
What GovernID does: Every record collected through GovernID is stored with its purpose, legal basis, the notice version shown, consent scope, retention end date and collection point. These are the answers an access response has to give. In the Privacy Center, the individual sees their records instantly as a preliminary report and can export it, and your team finds a person's records across every GovernID collection point with PII Search.
What stays with you: Data held in systems outside GovernID and a copy of it, the formal response letter, identity checks beyond the verified e-mail, redaction of third-party data, and tracking the deadline.
Rectification, erasure and objection are separate rights and are handled separately; this section covers access only.
Frequently asked questions
Who supervises the PDPPL?
The law gives the role to a competent department. Today that role sits with the National Cyber Security Agency.
Does the PDPPL require a DPO?
The law has no general DPO duty. It does ask you to name who is responsible for data protection and to run internal systems for complaints and requests (Art. 11).
Can we transfer data out of Qatar?
Art. 15 says you may not restrict cross-border data flows unless the processing breaks the law or may cause serious damage. Your hosting choice is separate: GovernID hosts each company’s data in the country where it is registered.
Where is our data hosted?
GovernID hosts each company’s data in the country where it is registered.
Is this page legal advice?
No. It summarises the law to show where GovernID supports your work. Your legal counsel decides how it applies to your company.
The law and its regulations: official sources
Links go to the issuing authority's own website. Some government sites restrict access from outside their country.
- Law No. (13) of 2016 on Protecting Personal Data Privacy – Al Meezan, Arabic (binding) and English
- NCSA guidance hub for regulated entities – NCSA, English
- NCSA guideline: personal data breach notifications – NCSA, English
- NCSA guideline: individuals' rights – NCSA, English
- NCSA guideline: record of processing activities (RoPA) – NCSA, English
- NCSA guideline: data privacy impact assessment (DPIA) – NCSA, English