The GDPR — the General Data Protection Regulation (EU) 2016/679 — has reshaped how businesses collect, store and process personal data across Europe and beyond. Since its application in May 2018, regulators have imposed fines reaching up to €20 million or 4% of global annual turnover, whichever is higher, for the most serious violations. For businesses operating in the EU or EEA, or handling data belonging to residents of those territories, non-compliance is not a theoretical risk. It is a financial and reputational one. The rules are detailed, but they are not impossible to follow. Understanding the seven core obligations that sit at the heart of this regulation gives any organisation a practical roadmap to avoid the penalties that regulators have shown they are willing to impose.
Why GDPR Compliance Matters for Every Organisation
The GDPR applies to any organisation that processes personal data in the context of activities carried out in the EU or EEA, regardless of where that organisation is based. A US-based company offering services to German residents is subject to it. So is a London-based firm that targets French customers — though UK organisations must also account for the separate UK GDPR and the Data Protection Act 2018, which diverged from the EU framework after Brexit.
The financial exposure is structured in two tiers. Article 83(4) sets a ceiling of €10 million or 2% of global annual turnover for breaches such as failing to maintain proper records, not conducting required impact assessments, or inadequate processor contracts. Article 83(5) raises that ceiling to €20 million or 4% for more severe violations — breaching the core data protection principles, ignoring data subject rights, or making unlawful international transfers.
These are not automatic penalties. Supervisory authorities weigh factors including the nature and duration of the infringement, whether it was intentional or negligent, the degree of cooperation shown, and any prior violations. Still, the sums imposed across the EU since 2018 have run into the hundreds of millions. Reputational damage and the cost of remediation add further pressure. Compliance is not merely a legal checkbox — it is a business risk management decision.
National data protection authorities (DPAs) in each EU member state handle enforcement, coordinated at European level by the European Data Protection Board (EDPB). The EDPB issues binding decisions and guidelines that shape how the regulation is interpreted in practice. Organisations with cross-border processing activities deal with a lead supervisory authority under the one-stop-shop mechanism, though other concerned DPAs retain significant powers.
The 7 Core GDPR Rules to Follow
Breaking down compliance into seven concrete obligations makes the regulation far more manageable. Each rule addresses a different aspect of how personal data must be handled.
- Identify a lawful basis before processing. Every processing activity requires a legal ground under Article 6 — consent, contract performance, legal obligation, vital interests, public task, or legitimate interests. Processing without one is unlawful.
- Be transparent with data subjects. Privacy notices must be clear, concise and delivered at the point of collection. They must specify the purpose, legal basis, retention period, and the rights available to individuals.
- Collect only what you need. The data minimisation principle means gathering only personal data that is adequate, relevant and limited to what is necessary for the stated purpose.
- Secure personal data against breaches. Article 32 requires appropriate technical and organisational security measures, calibrated to the risk level of the processing activities involved.
- Control your processors. Any third party handling personal data on your behalf must operate under a written data processing agreement that meets the requirements of Article 28.
- Honour data subject rights without delay. Individuals can request access, rectification, erasure, portability, restriction or objection. Responses must be provided within one month as a standard deadline.
- Document everything. Accountability under Article 5(2) means being able to demonstrate compliance, not just claim it. Records, policies and evidence of decisions must exist and be maintained.
These seven rules are interdependent. A business that collects data lawfully but fails to document that lawful basis cannot demonstrate compliance. One that secures data well but ignores subject access requests faces enforcement action on a different front. The regulation demands a systemic approach, not a collection of isolated fixes.
Responding to Breaches and Data Subject Requests
Speed matters when something goes wrong. Under Article 33, a data controller must notify the competent supervisory authority within 72 hours of becoming aware of a personal data breach — provided that breach is likely to result in a risk to the rights and freedoms of individuals. Missing this window is itself a breach of the regulation, separate from the underlying security incident.
When the risk to individuals is high, Article 34 requires notifying the affected data subjects directly, without undue delay. The communication must describe the nature of the breach in plain language and explain what steps the organisation has taken or plans to take. Vague or delayed communications attract regulatory scrutiny.
Data subject rights requests follow a different timeline. Article 12(3) sets a standard response period of one month from receipt of the request. That period can be extended by a further two months where requests are complex or numerous, but the individual must be informed of the extension within the first month. Silence is not an option.
Internal procedures need to be in place before incidents occur. Organisations should have a documented breach response plan that assigns responsibility, sets internal escalation timelines shorter than 72 hours, and identifies the relevant supervisory authority. For subject access requests, a clear intake and tracking process prevents requests from being lost or overlooked in day-to-day operations.
One practical point often missed: the 72-hour clock starts when the organisation becomes aware of the breach, not when it is confirmed or investigated. Delayed internal reporting within a company can consume most of that window before any external notification begins. Training staff to escalate potential incidents immediately is not optional — it is the mechanism that makes the deadline achievable.
Documentation, Risk Assessments and Accountability in Practice
Accountability is the thread running through every obligation in the regulation. Article 30 requires controllers to maintain a record of processing activities. Organisations with fewer than 250 employees are not automatically exempt — the exception disappears if the processing is not occasional, carries risk, or involves special categories of data such as health or biometric information.
A Data Protection Impact Assessment (DPIA) is mandatory before starting any processing that is likely to result in high risk to individuals. Automated decision-making, large-scale processing of sensitive data, and systematic monitoring of public spaces are among the triggers identified in Article 35. Skipping a DPIA when one is required is a direct violation, independent of whether the processing itself causes harm.
Some organisations must appoint a Data Protection Officer (DPO). Public authorities, organisations carrying out large-scale systematic monitoring, and those processing special categories of data at scale are all required to do so. The DPO must have expert knowledge of data protection law and practice, and must be given the resources and independence to do the job properly.
Privacy by design and by default, codified in Article 25, requires that data protection is built into systems and processes from the outset — not bolted on afterwards. Default settings must be the most privacy-protective available. This applies to software, products and services alike. A checklist of documentation to maintain includes: records of lawful bases, privacy notices, processor contracts, the processing register, completed DPIAs, records of consent where applicable, rights request logs, and the breach response procedure.
Enforcement Patterns, Recourse Options and Mistakes That Invite Fines
Supervisory authorities do not apply fines mechanically. Article 83(2) sets out six categories of factors to weigh: the nature, gravity and duration of the infringement; whether it was intentional; measures taken to mitigate damage; the degree of responsibility; prior infringements; and the level of cooperation with the authority. A business that self-reports, acts quickly and demonstrates good faith will typically face different treatment than one that conceals a breach.
Individuals who believe their rights have been violated can file a complaint with any competent supervisory authority. They can also bring a claim directly before the national courts of the relevant member state under Article 79. Where damage — material or non-material — has been suffered, Article 82 creates a right to compensation, enforceable against both controllers and processors. The procedural rules and limitation periods for these claims vary by member state and should be verified with a qualified legal professional in the relevant jurisdiction.
The mistakes that most frequently attract enforcement action follow a predictable pattern. Processing personal data without a documented lawful basis. Failing to respond to subject access requests within the statutory period. Using processors without a compliant written agreement. Transferring data to third countries without an adequate legal mechanism in place. Collecting more data than the stated purpose requires. Each of these is a standalone violation, and they tend to cluster — an organisation that gets one wrong often has systemic gaps across several.
The Information Commissioner's Office (ICO) in the UK publishes detailed guidance under the UK GDPR framework, which diverges from the EU regulation in certain respects. Organisations operating across both jurisdictions need to map their obligations under each regime separately. Treating them as identical creates compliance gaps that neither authority will overlook.
Regulatory enforcement has matured considerably. DPAs now coordinate more effectively, share intelligence, and issue binding decisions through the EDPB's consistency mechanism. Any organisation that handles personal data — regardless of size — should treat GDPR compliance as an ongoing operational discipline, not a one-time project. Only a qualified data protection lawyer can provide advice tailored to a specific organisation's circumstances and risk profile.