Regulation · United Kingdom
UK GDPR
At a glance
- Jurisdiction
- United Kingdom
- Supervisory authority
- The Information Commission (ICO)
- In force
- In its UK form since 1 January 2021 · amended by the Data (Use and Access) Act 2025
- Official name
- UK GDPR and Data Protection Act 2018
What the UK GDPR asks of you, article by article
How GovernID fits: The UK GDPR keeps the GDPR’s core duties: know your processing, explain it to people and prove it. GovernID builds that proof into collection. Your RoPA follows Art. 30, privacy notices are generated from it, and each record collected through GovernID carries the notice, consent, legal basis and retention period that applied on the day it arrived.
Recent developments: The Data (Use and Access) Act 2025 added recognised legitimate interests, new rules on response times and automated decisions, a new test for international transfers and a duty to handle complaints. The ICO became the Information Commission, and keeps the ICO name in everyday use.
| Requirement | Article | What GovernID does | What stays with you |
|---|---|---|---|
| Principles and accountability. Process lawfully, fairly and transparently, for specified purposes, with only the data needed, kept accurate and no longer than necessary, and be able to show it. | Art. 5(1), 5(2) | 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 and judging what is necessary. |
| Lawful basis. Every processing needs a lawful basis. Recognised legitimate interests, such as safeguarding, crime prevention and emergencies, do not need a balancing test. | Art. 6(1), 6(1)(ea), Annex 1 | 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. | The legal assessment, including the balancing test for other legitimate interests. |
| Conditions for consent. You must be able to show that consent was given, the request must be clear and separate, and withdrawing must be as easy as giving it. | Art. 7, Art. 4(11) | The approved consent text is shown at collection, one purpose per box, never pre-ticked, separate from the privacy notice. GovernID keeps the version on the record with the dates consent was given and withdrawn. People withdraw in the Privacy Center. | Deciding when consent is the right basis, and approving the text. |
| Special categories of data. Processing is prohibited unless an exception applies, often with a condition from the DPA 2018. | Art. 9; DPA 2018, Sch. 1 | Special category fields are marked in the RoPA and at collection, and GovernID recommends a DPIA for activities that use them. | Choosing the condition and keeping the policy document Sch. 1 asks for. |
| Transparency. Give people clear information about the controller, purposes, legal basis, recipients, transfers, retention and their rights, at the time data is collected. | Art. 12, 13, 14 | 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. |
| Data subject rights. Access, rectification, erasure, restriction, portability, objection, and safeguards for automated decisions. For access requests, make reasonable and proportionate searches. | Art. 15–21, 15(1A), 22A–22D | 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, rectification, erasure, restriction and portability requests, and requests made through other channels. |
| Response time. Reply within one month, extendable by two further months for complex requests. The clock can pause while you wait for information you need from the person. | Art. 12A | Requests made in the Privacy Center reach your team at once, with their date, and consent withdrawals are tracked until handled. | Deciding on each request and replying in time. |
| Complaints to the controller. Make it easy to complain, for example with an electronic form, acknowledge each complaint within 30 days and respond without undue delay. | DPA 2018, s. 164A–164B | Requests made in the Privacy Center are logged with their date, so you can show when each one arrived. | Providing the complaints channel, acknowledging and answering complaints. |
| Data protection by design and by default. Build protection into how processing is designed and collect only what each purpose needs. Online services likely to be used by children must give them higher protection. | Art. 25, 25(1A)–(1B) | 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, and the measures for children’s use of online services. |
| Processors. Use processors that give sufficient guarantees, under a contract with the listed terms. | Art. 28 | Processors and other recipients are recorded in each activity and shown as processing flows. | Choosing processors and signing the contracts. |
| UK representative. Controllers and processors outside the UK that are in scope appoint a representative in the UK. | Art. 27 | Privacy notices are generated from the RoPA and every section can be customised, so your representative’s details can appear in each notice. | Appointing the representative. |
| Records of processing activities. Keep a written record of each activity with the details Art. 30 lists. | Art. 30 | The RoPA is modelled on Art. 30. Process owners confirm their activities and every confirmation is logged. Compliance Reporting exports the record with its version history. | Keeping the record complete for processing outside GovernID. |
| Security of processing. Apply technical and organisational measures appropriate to the risk. | Art. 32 | 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. Notify the ICO within 72 hours where feasible, inform people when the risk to them is high, and document every breach. | Art. 33, 34 | Breach Impact Analysis shows which activities used the affected system, which data was kept there and which safeguards applied. | Assessing the breach, notifying and documenting it. |
| DPIA. Assess processing likely to result in a high risk before it starts, and consult the ICO when risk remains high. | Art. 35, 36 | GovernID recommends a DPIA for activities with special category data or transfers abroad. The assessment opens with the facts from your RoPA, ends with a risk map and report, and can be exported as PDF and JSON. | The risk judgement and any prior consultation. |
| Data protection officer. Appoint a DPO where the law requires it. | Art. 37–39 | Your DPO works from one RoPA, sees which activities are confirmed and which have changed, and can export reports for management. | Appointing the DPO. |
| Transfers outside the UK. Transfer under UK adequacy regulations, or with appropriate safeguards such as the IDTA or the UK Addendum to the EU standard contractual clauses. The safeguards must meet the data protection test: protection must not be materially lower than in the UK. | Art. 44, 45A, 45B, 46 | Transfers are recorded in each activity, and GovernID recommends a DPIA when data is sent abroad. | Choosing the transfer tool, carrying out the data protection test and signing it. |
| Storage limitation and erasure. Keep data no longer than needed and erase it when the grounds end. | Art. 5(1)(e), Art. 17 | 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. |
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 15 UK GDPR, an individual can ask whether you process their personal data and receive a copy with the same information the EU GDPR requires.
| The response must include | Article |
|---|---|
| Confirmation of processing and a copy of the personal data | Art. 15(1), 15(3) |
| Purposes, categories of data, recipients, retention period | Art. 15(1)(a)–(d) |
| Other rights, the right to complain to the ICO, the source of the data | Art. 15(1)(e)–(g) |
| Automated decision-making, including profiling | Art. 15(1)(h) |
| Safeguards for transfers outside the UK | Art. 15(2) |
| Only data found by a reasonable and proportionate search | Art. 15(1A) |
Deadline: one month from the latest of receiving the request, identity information or any fee. Extension: two further months for complex or numerous requests (Art. 12A). Fee: free in most cases.
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. The RoPA documents which systems hold which data, the basis for showing your search was reasonable and proportionate.
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.
What manual handling costs: Gartner estimates that manually fulfilling a single subject rights request costs organisations around US$1,500 (Market Guide for Subject Rights Request Automation, 2021).
Frequently asked questions
Is the UK GDPR the same as the EU GDPR?
It started from the same text, and most duties are still the same. Since the Data (Use and Access) Act 2025 the two differ in areas such as recognised legitimate interests, automated decisions, response times, complaints and international transfers.
We already comply with the EU GDPR. What do we need to add for the UK?
Typically a UK representative if you are outside the UK (Art. 27), UK transfer tools such as the IDTA or the UK Addendum, a complaints process (DPA 2018, s. 164A) and the UK’s own response-time rules (Art. 12A).
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.
- UK GDPR (consolidated text) – legislation.gov.uk, English
- Data Protection Act 2018 (consolidated text) – legislation.gov.uk, English
- Data (Use and Access) Act 2025 – legislation.gov.uk, English
- Data (Use and Access) Act 2025: Commencement Regulations No. 1 – legislation.gov.uk, English