ADGM DPR vs GDPR Denmark
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 1 of 1 topics. Each verdict names what it rests on; read the wording before relying on it.
- ADGM DPR Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
- GDPR Denmark Asks more on 0 topics Alone on 0 topics More detailed on 1 topic
| Topic | ADGM DPR | GDPR Denmark | Verdict |
|---|---|---|---|
| Detection and response | |||
| Reporting to authorities | ADGM DPR: 1 | GDPR Denmark: 3 | GDPR Denmark more detailedmore requirements on this, not necessarily stricter |
What This Covers
The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.
Key Numbers
Deadline
ADGM DPR: Not in the acts covered
GDPR Denmark: At the time the data are obtained (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
Threshold
ADGM DPR: Not in the acts covered
GDPR Denmark: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)
Goes to
ADGM DPR: Not in the acts covered
GDPR Denmark: Controller (Processors); Data subjects (Controllers)
Evidence to keep
ADGM DPR: Not in the acts covered
GDPR Denmark: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
Incident reports go to
ADGM DPR: ADGM Commissioner of Data Protection
GDPR Denmark: Competent supervisory authority (Controllers)
First notice of an incident
ADGM DPR: Not in the acts covered
GDPR Denmark: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)
Incident notification
ADGM DPR: Without undue delay and, where feasible, within 72 hours of becoming aware
GDPR Denmark: Not in the acts covered
Intermediate report
ADGM DPR: Not in the acts covered
GDPR Denmark: In phases, without undue further delay (Controllers)
External assessment or certification
ADGM DPR: Not in the acts covered
GDPR Denmark: Approved code of conduct or certification may help show compliance (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
Review of the risk framework
ADGM DPR: Not in the acts covered
GDPR Denmark: Where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
Testing of critical systems
ADGM DPR: Not in the acts covered
GDPR Denmark: Regularly
Maximum fines
ADGM DPR: Not in the acts covered
GDPR Denmark: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher
Detection and response
Reporting to authorities
GDPR Denmark more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5
Notify Personal Data Breaches
Notify the Commissioner of Data Protection of a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to the rights of individuals.
Notify a personal data breach
Applies to: Controllers
Notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to risk people's rights and freedoms. Give reasons if the notice is late.
GDPR, Article 33(1) · applies as in the Directive
Processor tells the controller
Applies to: Processors
Tell the controller of a personal data breach without undue delay after becoming aware of it.
GDPR, Article 33(2) · applies as in the Directive
What the breach notice contains
Applies to: Controllers
Describe the breach, including the categories and approximate numbers of people and records where possible, the DPO or other contact point, the likely consequences, and the measures taken or proposed. Information not yet available may follow in phases.
GDPR, Article 33(3) and (4) · applies as in the Directive
Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022. 22 topics where all apply the Directive as it is are not shown.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.