Free course · UK GDPR · Certificate with a checkable number
Data Protection Officer Foundation: the UK GDPR in six short modules
A free online course for anyone who has been handed data protection responsibilities, is thinking about becoming a Data Protection Officer, or needs to understand what their DPO does. Read the six modules, pass a 20-question assessment, and receive a certificate with a unique number that anyone can check on this site.
Free
no account, no payment, no sales callsCost
6 modules
about 90 minutes of reading, at your own paceTime
80%
16 of 20 questions to pass, drawn from a larger bank; retake as often as you likeAssessment
Checkable
every certificate has a unique number an employer can check hereCertificate
Before you start: what this certificate is, and is not
There is no legally required qualification to be a Data Protection Officer in the UK. The law asks for expert knowledge of data protection law and practice, in proportion to the processing the organisation does. This course gives you the foundation of that knowledge. Its certificate shows you passed our assessment on a given date. It is not an accredited qualification, it is not issued or endorsed by the Information Commissioner’s Office, and it does not by itself qualify anyone to act as a DPO.
The course reflects the law as amended by the Data (Use and Access) Act 2025, most of whose data protection changes came into force on 5 February 2026, with the new complaints duty following on 19 June 2026.
Module 1: UK data protection law and key terms
Three pieces of law do most of the work. The UK GDPR sets the principles, lawful bases, rights and duties. The Data Protection Act 2018 sits alongside it, adding exemptions, conditions for sensitive data, and separate regimes for law enforcement and the intelligence services. The Privacy and Electronic Communications Regulations (PECR) cover electronic marketing and cookies. The Data (Use and Access) Act 2025 amended all three rather than replacing them.
- Personal data is any information relating to an identified or identifiable living person: a name, an email address, an employee number linked to a person, a location, an online identifier.
- Special category data needs extra protection: racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic and biometric data used for identification, health, sex life and sexual orientation. Criminal offence data has its own rules.
- Processing is almost anything you do with personal data: collecting, storing, using, sharing, deleting.
- A controller decides why and how personal data is processed. A processor processes it on the controller’s behalf and on its instructions. Two organisations deciding together are joint controllers.
- The regulator is the Information Commissioner’s Office (ICO), which the 2025 Act restructures into the Information Commission.
Module 2: Principles and lawful bases
Article 5 of the UK GDPR sets six principles. Personal data must be processed lawfully, fairly and transparently; collected for specified purposes and not used in incompatible ways (purpose limitation); adequate, relevant and limited to what is necessary (data minimisation); accurate; kept no longer than necessary (storage limitation); and kept secure (integrity and confidentiality). Over them sits accountability: the controller is responsible for compliance and must be able to demonstrate it.
Every processing activity needs one of six lawful bases in Article 6: consent, contract, legal obligation, vital interests, public task, or legitimate interests. Consent must be freely given, specific, informed and unambiguous, and as easy to withdraw as to give; pre-ticked boxes do not count. Legitimate interests normally needs a three-part test: a real interest, processing necessary for it, and a balance against the individual’s interests.
The 2025 Act added recognised legitimate interests: listed purposes, such as safeguarding vulnerable people, preventing or detecting crime, emergencies, national security, and responding to requests from bodies carrying out public tasks, where no balancing test is needed. It also clarified when further processing is compatible with the original purpose.
Special category data needs both an Article 6 lawful basis and an Article 9 condition, and many Article 9 conditions need a further condition from Schedule 1 of the Data Protection Act 2018, often with an appropriate policy document.
Module 3: Individuals’ rights and complaints
- The right to be informed: privacy information must be concise, transparent, intelligible, easily accessible and in plain language.
- The right of access: a subject access request must normally be answered within one month, extendable by up to two further months if it is complex or one of many. It is normally free, unless manifestly unfounded or excessive. The law now expects searches that are reasonable and proportionate, and the clock can pause while you ask the requester to clarify.
- Rectification, erasure and restriction: correcting, deleting or pausing the use of data in defined circumstances.
- Data portability: receiving data in a structured, machine-readable format where processing is based on consent or contract and is automated.
- The right to object: for direct marketing it is absolute; for processing based on legitimate interests or public task, you must stop unless you have compelling grounds.
- Automated decisions: since 5 February 2026, Articles 22A to 22D allow more significant decisions to be made solely by automated means, but individuals must be told, be able to make representations, obtain human intervention and contest the decision. Stricter limits remain where special category data is used.
Complaints: since 19 June 2026, controllers must make it easy to complain about their use of personal data (for example with an online form), acknowledge a complaint within 30 days, take appropriate steps to respond, and tell the complainant the outcome without undue delay. People should normally complain to the organisation before going to the ICO.
Module 4: Accountability, DPIAs, processors and transfers
- Records of processing activities: what personal data you hold, why, who it is shared with, where it goes and how long you keep it.
- Data protection by design and by default: build protection into systems and processes from the start, and process only what is necessary by default.
- Data Protection Impact Assessments: required where processing is likely to result in a high risk to people’s rights and freedoms, for example large-scale special category data, systematic monitoring, or new technologies such as AI. If a high risk remains that you cannot reduce, you must consult the ICO before starting.
- Processors: a controller may use only processors that give sufficient guarantees, under a written contract containing the terms in Article 28: acting only on instructions, confidentiality, security, sub-processor controls, assistance with rights and breaches, deletion or return at the end, and audit.
- International transfers: a transfer outside the UK needs adequacy regulations, appropriate safeguards such as the International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses (normally with a transfer risk assessment), or a narrow exception. The 2025 Act changed the adequacy test to whether protection is “not materially lower” than in the UK.
Module 5: Security and personal data breaches
Article 32 requires security appropriate to the risk: technical measures such as access control, encryption and patching, and organisational ones such as training, policies and supplier checks, tested regularly.
A personal data breach is any security incident leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. It includes an email sent to the wrong person, a lost laptop and a ransomware attack alike.
- Report a breach to the ICO within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to individuals. If you do not have all the facts yet, report what you know and follow up.
- Tell the people affected without undue delay where the breach is likely to result in a high risk to them.
- Record every breach internally, including those you decide not to report, with the facts, effects and action taken.
The maximum fines are £17.5 million or 4% of annual worldwide turnover, whichever is higher, for the most serious infringements, and £8.7 million or 2% for others. Since February 2026 PECR breaches can attract fines at the same level.
Module 6: The Data Protection Officer role
When a DPO is required: you must appoint one if you are a public authority or body (except courts acting judicially), or if your core activities involve large-scale, regular and systematic monitoring of individuals, or large-scale processing of special category or criminal offence data. Others may appoint one voluntarily, and the same rules then apply. If you decide you do not need one, record why.
What a DPO does: informs and advises the organisation and its staff about their obligations; monitors compliance, including policies, training and audits; advises on and monitors DPIAs; cooperates with the ICO and acts as its contact point; and is the contact for individuals about their data. A DPO should take a risk-based approach and focus on the highest-risk processing.
How a DPO must be positioned: involved in all data protection issues in good time; given the resources and access needed; reporting to the highest level of management; independent in performing the DPO tasks; and not dismissed or penalised for doing them. The DPO can have other duties only if they do not create a conflict of interest, so a person who decides why and how data is processed, such as a head of marketing, HR or IT, is usually a poor choice. The DPO can be internal or external, and one DPO can serve a group if they can do the job properly. The organisation, not the DPO, remains responsible for compliance.
Publishing contact details: publish the DPO’s contact details and give them to the ICO. Most organisations that process personal data must also pay the ICO data protection fee unless exempt.
The question your board should ask
“If the ICO asked us tomorrow who our DPO reports to, what they told us last quarter, and what we did about it, could we show them?”
Take the assessment
Twenty multiple-choice questions, drawn at random from a larger bank and marked on our server. You need 16 to pass. If you do not pass, we tell you which modules to revisit and you can try again with a fresh set of questions. If you pass, your certificate is issued straight away with a unique number, and we email you a link to it.
Checked on 19 October 2026 against the ICO’s guidance on data protection officers and the commencement of the Data (Use and Access) Act 2025. The ICO has said its DPO guidance is under review following the Act; we will update the course when it changes. This course is general information, not legal advice. We find the gaps, fix them with you, and give you the evidence. Where we have done the fixing, our report says so, and we do not call that review independent.