- Latest available (Revised)
- Point in Time (25/05/2018)
- Original (As enacted)
Version Superseded: 31/12/2020
Point in time view as at 25/05/2018.
Data Protection Act 2018, Cross Heading: Enforcement notices is up to date with all changes known to be in force on or before 22 November 2024. There are changes that may be brought into force at a future date. Changes that have been made appear in the content and are referenced with annotations.
Changes and effects yet to be applied by the editorial team are only applicable when viewing the latest version or prospective version of legislation. They are therefore not accessible when viewing legislation as at a specific point in time. To view the ‘Changes to Legislation’ information for this provision return to the latest version view using the options provided in the ‘What Version’ box above.
(1)Where the Commissioner is satisfied that a person has failed, or is failing, as described in subsection (2), (3), (4) or (5), the Commissioner may give the person a written notice (an “enforcement notice”) which requires the person—
(a)to take steps specified in the notice, or
(b)to refrain from taking steps specified in the notice,
or both (and see also sections 150 and 151).
(2)The first type of failure is where a controller or processor has failed, or is failing, to comply with any of the following—
(a)a provision of Chapter II of the GDPR or Chapter 2 of Part 3 or Chapter 2 of Part 4 of this Act (principles of processing);
(b)a provision of Articles 12 to 22 of the GDPR or Part 3 or 4 of this Act conferring rights on a data subject;
(c)a provision of Articles 25 to 39 of the GDPR or section 64 or 65 of this Act (obligations of controllers and processors);
(d)a requirement to communicate a personal data breach to the Commissioner or a data subject under section 67, 68 or 108 of this Act;
(e)the principles for transfers of personal data to third countries, non-Convention countries and international organisations in Articles 44 to 49 of the GDPR or in sections 73 to 78 or 109 of this Act.
(3)The second type of failure is where a monitoring body has failed, or is failing, to comply with an obligation under Article 41 of the GDPR (monitoring of approved codes of conduct).
(4)The third type of failure is where a person who is a certification provider—
(a)does not meet the requirements for accreditation,
(b)has failed, or is failing, to comply with an obligation under Article 42 or 43 of the GDPR (certification of controllers and processors), or
(c)has failed, or is failing, to comply with any other provision of the GDPR (whether in the person's capacity as a certification provider or otherwise).
(5)The fourth type of failure is where a controller has failed, or is failing, to comply with regulations under section 137.
(6)An enforcement notice given in reliance on subsection (2), (3) or (5) may only impose requirements which the Commissioner considers appropriate for the purpose of remedying the failure.
(7)An enforcement notice given in reliance on subsection (4) may only impose requirements which the Commissioner considers appropriate having regard to the failure (whether or not for the purpose of remedying the failure).
(8)The Secretary of State may by regulations confer power on the Commissioner to give an enforcement notice in respect of other failures to comply with the data protection legislation.
(9)Regulations under this section—
(a)may make provision about the giving of an enforcement notice in respect of the failure, including by amending this section and sections 150 to 152,
(b)may make provision about the giving of an information notice, an assessment notice or a penalty notice, or about powers of entry and inspection, in connection with the failure, including by amending sections 142, 143, 146, 147 and 155 to 157 and Schedules 15 and 16, and
(c)are subject to the affirmative resolution procedure.
Modifications etc. (not altering text)
C1S. 149 applied (with modifications) by S.I. 2016/696, Sch. 2 (as substituted (25.5.2018) by Data Protection Act 2018 (c. 12), s. 212(1), Sch. 19 para. 406 (with ss. 117, 209, 210); S.I. 2018/625, reg. 2(1)(g) (with reg. 4))
Commencement Information
I1S. 149 in force at Royal Assent for specified purposes, see s. 212(2)(f)
I2S. 149 in force at 25.5.2018 in so far as not already in force by S.I. 2018/625, reg. 2(1)(f)
(1)An enforcement notice must—
(a)state what the person has failed or is failing to do, and
(b)give the Commissioner's reasons for reaching that opinion.
(2)In deciding whether to give an enforcement notice in reliance on section 149(2), the Commissioner must consider whether the failure has caused or is likely to cause any person damage or distress.
(3)In relation to an enforcement notice given in reliance on section 149(2), the Commissioner's power under section 149(1)(b) to require a person to refrain from taking specified steps includes power—
(a)to impose a ban relating to all processing of personal data, or
(b)to impose a ban relating only to a specified description of processing of personal data, including by specifying one or more of the following—
(i)a description of personal data;
(ii)the purpose or manner of the processing;
(iii)the time when the processing takes place.
(4)An enforcement notice may specify the time or times at which, or period or periods within which, a requirement imposed by the notice must be complied with (but see the restrictions in subsections (6) to (8)).
(5)An enforcement notice must provide information about—
(a)the consequences of failure to comply with it, and
(b)the rights under sections 162 and 164 (appeals etc).
(6)An enforcement notice must not specify a time for compliance with a requirement in the notice which falls before the end of the period within which an appeal can be brought against the notice.
(7)If an appeal is brought against an enforcement notice, a requirement in the notice need not be complied with pending the determination or withdrawal of the appeal.
(8)If an enforcement notice—
(a)states that, in the Commissioner's opinion, it is necessary for a requirement to be complied with urgently, and
(b)gives the Commissioner's reasons for reaching that opinion,
subsections (6) and (7) do not apply but the notice must not require the requirement to be complied with before the end of the period of 24 hours beginning when the notice is given.
(9)In this section, “specified” means specified in an enforcement notice.
Modifications etc. (not altering text)
C2S. 150 applied (with modifications) by S.I. 2016/696, Sch. 2 (as substituted (25.5.2018) by Data Protection Act 2018 (c. 12), s. 212(1), Sch. 19 para. 406 (with ss. 117, 209, 210); S.I. 2018/625, reg. 2(1)(g) (with reg. 4))
Commencement Information
I3S. 150 in force at 25.5.2018 by S.I. 2018/625, reg. 2(1)(f)
(1)Subsections (2) and (3) apply where an enforcement notice is given in respect of a failure by a controller or processor—
(a)to comply with a data protection principle relating to accuracy, or
(b)to comply with a data subject's request to exercise rights under Article 16, 17 or 18 of the GDPR (right to rectification, erasure or restriction on processing) or section 46, 47 or 100 of this Act.
(2)If the enforcement notice requires the controller or processor to rectify or erase inaccurate personal data, it may also require the controller or processor to rectify or erase any other data which—
(a)is held by the controller or processor, and
(b)contains an expression of opinion which appears to the Commissioner to be based on the inaccurate personal data.
(3)Where a controller or processor has accurately recorded personal data provided by the data subject or a third party but the data is inaccurate, the enforcement notice may require the controller or processor—
(a)to take steps specified in the notice to ensure the accuracy of the data,
(b)if relevant, to secure that the data indicates the data subject's view that the data is inaccurate, and
(c)to supplement the data with a statement of the true facts relating to the matters dealt with by the data that is approved by the Commissioner,
(as well as imposing requirements under subsection (2)).
(4)When deciding what steps it is reasonable to specify under subsection (3)(a), the Commissioner must have regard to the purpose for which the data was obtained and further processed.
(5)Subsections (6) and (7) apply where—
(a)an enforcement notice requires a controller or processor to rectify or erase personal data, or
(b)the Commissioner is satisfied that the processing of personal data which has been rectified or erased by the controller or processor involved a failure described in subsection (1).
(6)An enforcement notice may, if reasonably practicable, require the controller or processor to notify third parties to whom the data has been disclosed of the rectification or erasure.
(7)In determining whether it is reasonably practicable to require such notification, the Commissioner must have regard, in particular, to the number of people who would have to be notified.
(8)In this section, “data protection principle relating to accuracy” means the principle in—
(a)Article 5(1)(d) of the GDPR,
(b)section 38(1) of this Act, or
(c)section 89 of this Act.
Commencement Information
I4S. 151 in force at 25.5.2018 by S.I. 2018/625, reg. 2(1)(f)
(1)The Commissioner may not give a controller or processor an enforcement notice in reliance on section 149(2) with respect to the processing of personal data for the special purposes unless—
(a)a determination under section 174 with respect to the data or the processing has taken effect, and
(b)a court has granted leave for the notice to be given.
(2)A court must not grant leave for the purposes of subsection (1)(b) unless it is satisfied that—
(a)the Commissioner has reason to suspect a failure described in section 149(2) which is of substantial public importance, and
(b)the controller or processor has been given notice of the application for leave in accordance with rules of court or the case is urgent.
(3)An enforcement notice does not require a person to do something to the extent that requiring the person to do it would involve an infringement of the privileges of either House of Parliament.
(4)In the case of a joint controller in respect of the processing of personal data to which Part 3 or 4 applies whose responsibilities for compliance with that Part are determined in an arrangement under section 58 or 104, the Commissioner may only give the controller an enforcement notice in reliance on section 149(2) if the controller is responsible for compliance with the provision, requirement or principle in question.
Modifications etc. (not altering text)
C3S. 152 applied (with modifications) by S.I. 2016/696, Sch. 2 (as substituted (25.5.2018) by Data Protection Act 2018 (c. 12), s. 212(1), Sch. 19 para. 406 (with ss. 117, 209, 210); S.I. 2018/625, reg. 2(1)(g) (with reg. 4))
Commencement Information
I5S. 152 in force at 25.5.2018 by S.I. 2018/625, reg. 2(1)(f)
(1)The Commissioner may cancel or vary an enforcement notice by giving written notice to the person to whom it was given.
(2)A person to whom an enforcement notice is given may apply in writing to the Commissioner for the cancellation or variation of the notice.
(3)An application under subsection (2) may be made only—
(a)after the end of the period within which an appeal can be brought against the notice, and
(b)on the ground that, by reason of a change of circumstances, one or more of the provisions of that notice need not be complied with in order to remedy the failure identified in the notice.
Modifications etc. (not altering text)
C4S. 153 applied (with modifications) by S.I. 2016/696, Sch. 2 (as substituted (25.5.2018) by Data Protection Act 2018 (c. 12), s. 212(1), Sch. 19 para. 406 (with ss. 117, 209, 210); S.I. 2018/625, reg. 2(1)(g) (with reg. 4))
Commencement Information
I6S. 153 in force at 25.5.2018 by S.I. 2018/625, reg. 2(1)(f)
The Whole Act you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.
Would you like to continue?
The Whole Act you have selected contains over 200 provisions and might take some time to download.
Would you like to continue?
The Whole Act without Schedules you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.
Would you like to continue?
The Whole Act without Schedules you have selected contains over 200 provisions and might take some time to download.
Would you like to continue?
The Whole Act you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.
Would you like to continue?
The Whole Act without Schedules you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.
Would you like to continue?
The Schedules you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.
Would you like to continue?
Latest Available (revised):The latest available updated version of the legislation incorporating changes made by subsequent legislation and applied by our editorial team. Changes we have not yet applied to the text, can be found in the ‘Changes to Legislation’ area.
Original (As Enacted or Made): The original version of the legislation as it stood when it was enacted or made. No changes have been applied to the text.
Point in Time: This becomes available after navigating to view revised legislation as it stood at a certain point in time via Advanced Features > Show Timeline of Changes or via a point in time advanced search.
Geographical Extent: Indicates the geographical area that this provision applies to. For further information see ‘Frequently Asked Questions’.
Show Timeline of Changes: See how this legislation has or could change over time. Turning this feature on will show extra navigation options to go to these specific points in time. Return to the latest available version by using the controls above in the What Version box.
Text created by the government department responsible for the subject matter of the Act to explain what the Act sets out to achieve and to make the Act accessible to readers who are not legally qualified. Explanatory Notes were introduced in 1999 and accompany all Public Acts except Appropriation, Consolidated Fund, Finance and Consolidation Acts.
Access essential accompanying documents and information for this legislation item from this tab. Dependent on the legislation item being viewed this may include:
This timeline shows the different points in time where a change occurred. The dates will coincide with the earliest date on which the change (e.g an insertion, a repeal or a substitution) that was applied came into force. The first date in the timeline will usually be the earliest date when the provision came into force. In some cases the first date is 01/02/1991 (or for Northern Ireland legislation 01/01/2006). This date is our basedate. No versions before this date are available. For further information see the Editorial Practice Guide and Glossary under Help.
Use this menu to access essential accompanying documents and information for this legislation item. Dependent on the legislation item being viewed this may include:
Click 'View More' or select 'More Resources' tab for additional information including: