
GDPR Fundamentals and Obligations
The General Data Protection Regulation (GDPR) is the cornerstone of data‑privacy law across the European Union. This course breaks down the most frequently tested concepts, from the legal…

Under Art. 6 GDPR, processing is lawful when it is necessary for the performance of a contract. What does this condition require?
What is the maximum administrative fine for a serious infringement under the GDPR?
Which role must be appointed when a company’s core activity involves systematic large‑scale monitoring of data subjects?
When may a data controller rely on a legitimate interest as a lawful basis for processing?
Which of the following is NOT a principle listed in Art. 5 §1 of the GDPR?
What must a data controller do before collecting personal data from a data subject?
Which type of consent is considered invalid under the GDPR?
When does the GDPR require a Data Protection Impact Assessment (DPIA)?
Which right allows a data subject to receive a copy of their personal data in a structured, commonly used format?
Understanding GDPR: Core Concepts and Obligations
The General Data Protection Regulation (GDPR) is the cornerstone of data‑privacy law across the European Union. This course breaks down the most frequently tested concepts, from the legal hierarchy of EU instruments to the practical steps organisations must take to comply. By the end of the module, you will be able to explain key provisions, identify lawful bases for processing, and implement the necessary safeguards to avoid hefty fines.
1. The Legal Hierarchy: Why the GDPR Is a Regulation
EU law is built on several types of legal instruments. Among them, a Regulation has the strongest direct effect because it applies uniformly in all member states without the need for national transposition. This distinguishes it from a Directive, which requires each country to adopt its own implementing legislation, and from non‑binding instruments such as Recommendations or Guidelines.
- Regulation: Directly applicable, supreme over national law.
- Directive: Sets objectives; each state must achieve them through its own laws.
- Recommendation / Guideline: Advisory, no legal force.
Understanding this hierarchy helps you appreciate why GDPR compliance is mandatory for any entity processing EU residents’ data, regardless of where the organisation is based.
2. Lawful Bases for Processing Under Article 6
Article 6 lists six lawful bases. One of the most common is the necessity of processing for the performance of a contract. This basis does not require the data subject’s explicit consent; instead, it hinges on the existence of a contractual relationship.
Key points to remember:
- The controller must be able to demonstrate that the processing is essential to fulfil the contract.
- Processing that is merely convenient, but not required, does not qualify.
- When the contract ends, the lawful basis may cease, unless another basis (e.g., legal obligation) applies.
3. Administrative Fines: The Financial Stakes
GDPR enforcement is backed by substantial penalties designed to incentivise compliance. For a "serious infringement"—such as failing to obtain valid consent or neglecting data‑subject rights—the maximum administrative fine is €20 million or 4 % of the company’s worldwide annual turnover, whichever is higher. This tiered approach ensures that both small and large organisations face proportionate consequences.
Examples of serious infringements include:
- Processing special categories of data without a valid basis.
- Neglecting to appoint a Data Protection Officer (DPO) when required.
- Failing to provide transparent privacy notices.
4. The Role of the Data Protection Officer (DPO)
When a company’s core activities involve systematic, large‑scale monitoring of individuals—or when it processes special categories of data on a large scale—a Data Protection Officer must be appointed. The DPO acts as an independent advisor, monitors compliance, and serves as the point of contact for supervisory authorities.
Key responsibilities include:
- Advising on data‑protection impact assessments (DPIAs).
- Conducting training and awareness programmes.
- Cooperating with supervisory authorities during investigations.
5. Legitimate Interest as a Lawful Basis
Legitimate interest is a flexible basis but can only be used when the controller’s interest does not override the data subject’s fundamental rights and freedoms. A three‑step test is recommended:
- Identify a legitimate interest (e.g., fraud prevention, direct marketing).
- Assess necessity—is the processing required to achieve that interest?
- Balance test—consider the impact on the data subject and implement safeguards.
If the balance tips in favour of the data subject, the controller must choose another lawful basis, typically consent.
6. Core Principles of Article 5 §1
Article 5 outlines seven fundamental principles that guide all processing activities. One common misconception is that "Retention limitation" is a principle; however, the correct principle is "Integrity and confidentiality", often referred to as the security principle.
The seven principles are:
- Lawfulness, fairness, and transparency
- Purpose limitation
- Data minimisation
- Accuracy
- Integrity and confidentiality (security)
- Accountability
Retention limitation is actually a requirement derived from the storage limitation principle, not a standalone principle.
7. Transparency: The Privacy Notice Requirement
Before collecting personal data, a controller must provide a clear, concise, and easily accessible privacy notice. This notice must include:
- Identity of the controller and, where applicable, the DPO.
- Purpose(s) of processing and the lawful basis.
- Data retention periods.
- Rights of the data subject (access, rectification, erasure, etc.).
- Information on international data transfers, if any.
While a Data Protection Impact Assessment (DPIA) and registration with a national authority (e.g., CNIL in France) may be required in specific contexts, the privacy notice is the universal first step.
8. Valid vs. Invalid Consent
Consent must be a freely given, specific, informed, and unambiguous indication of the data subject’s wishes. The GDPR explicitly rejects "pre‑checked opt‑out" boxes because they do not constitute an active choice. Valid consent typically looks like an unchecked opt‑in box that the user must tick after being presented with clear information.
Best practices for obtaining consent:
- Use separate tick boxes for each distinct purpose.
- Provide a link to the full privacy policy next to the consent element.
- Record the timestamp and version of the consent statement.
- Allow easy withdrawal of consent at any time.
9. Putting It All Together: A Compliance Checklist
Use the following checklist to audit your organisation’s GDPR readiness:
- Identify all personal data flows and map them to lawful bases.
- Confirm that a DPO is appointed where required.
- Draft or update privacy notices to meet transparency requirements.
- Review consent mechanisms; eliminate any pre‑checked opt‑out boxes.
- Conduct DPIAs for high‑risk processing activities.
- Implement technical and organisational measures to ensure data integrity and confidentiality.
- Establish procedures for data‑subject rights requests and breach notifications.
Regularly revisit this checklist, especially after launching new services or entering new markets, to stay ahead of regulatory expectations.
10. Frequently Asked Questions (FAQ)
- Q: Does the GDPR apply to non‑EU companies?
A: Yes, if they offer goods or services to EU residents or monitor their behaviour within the EU. - Q: Can I rely on legitimate interest for direct marketing?
A: Possibly, but you must perform a balance test and provide an easy opt‑out mechanism. - Q: What triggers a “serious infringement” fine?
A: Violations of core principles (e.g., lack of consent, inadequate security) or failure to cooperate with supervisory authorities.
By mastering these concepts, you will be equipped to navigate the GDPR landscape confidently, protect data subjects’ rights, and safeguard your organisation against costly penalties.
