Divorce

GDPR Compliance: What Every Business Needs to Know Today

GDPR Compliance: What Every Business Needs to Know Today

GDPR — the General Data Protection Regulation — has reshaped how organizations worldwide handle personal data since it became enforceable in May 2018. Eight years on, compliance remains a live operational challenge, not a one-time project. Regulators are issuing larger fines, pursuing cross-border investigations, and scrutinizing digital practices with greater precision. Any business that collects, stores, or processes data about individuals in the European Economic Area must understand its obligations under this regulation. The stakes are financial, legal, and reputational. This article sets out what controllers, processors, and their legal advisers need to understand about the current state of GDPR obligations, from territorial scope to breach response, vendor management to enforcement priorities.

GDPR compliance: who must comply and why it matters

The regulation's territorial reach is broader than many businesses assume. Article 3 of Regulation (EU) 2016/679 applies the rules not only to organizations established in the European Economic Area but also to any organization outside the EEA that offers goods or services to individuals in the EU, or that monitors their behavior. A US-based SaaS company with no European office still falls within scope if it targets European customers. Applicability depends on actual activities, not on where a company is incorporated.

The UK GDPR, retained in domestic law alongside the Data Protection Act 2018, applies parallel requirements for processing activities affecting individuals in the United Kingdom. The Information Commissioner's Office (ICO) supervises enforcement there. Businesses operating across both jurisdictions must treat them as distinct legal frameworks with their own supervisory authorities, transfer mechanisms, and potential divergences as UK law continues to evolve.

Why does this matter beyond regulatory risk? A data breach or enforcement action triggers consequences that extend well past any administrative fine. Customer trust erodes quickly when personal data is mishandled. Contractual relationships with enterprise clients increasingly include data protection warranties, and a failure to comply can void those agreements. Investors and insurers now routinely assess data governance maturity during due diligence. The European Data Protection Board (EDPB) coordinates enforcement across EU supervisory authorities, meaning a complaint filed in one member state can trigger investigations in others through the one-stop-shop mechanism.

Smaller organizations sometimes assume the regulation does not apply to them. That assumption is wrong. Exemptions are narrow and specific. The regulation applies to any controller or processor, regardless of size, when processing falls within scope. Only certain record-keeping obligations carry a limited exemption for organizations with fewer than 250 employees, and even that exemption has conditions attached.

The core obligations businesses must operationalize

The seven principles in Article 5 form the backbone of the regulation. Personal data must be processed lawfully, fairly, and transparently. It must be collected for specified, explicit, and legitimate purposes. Controllers must limit collection to what is actually necessary, keep data accurate, store it no longer than needed, and protect it with appropriate security. The final principle — accountability — requires controllers to demonstrate compliance, not merely assert it.

Every processing activity needs a lawful basis. The six available bases include consent, contract performance, legal obligation, vital interests, public task, and legitimate interests. Choosing the right basis matters because it determines what rights data subjects can exercise. Consent, for example, must be freely given, specific, informed, and unambiguous. Under Article 7(3), individuals must be able to withdraw consent as easily as they gave it. Pre-ticked boxes and bundled agreements do not meet this standard.

Transparency means providing clear, accessible privacy information at the point of data collection. Privacy notices must explain who is collecting data, why, on what legal basis, how long it will be kept, and with whom it will be shared. Layered notices work well for digital interfaces where space is limited.

Processors — vendors, cloud providers, payroll services — must be governed by written data processing agreements that meet the requirements of Article 28. These contracts must specify the subject matter, duration, nature, and purpose of processing, the type of data and categories of data subjects, and the obligations and rights of the controller. Relying on a vendor's standard terms without reviewing them against Article 28 requirements is a common compliance gap.

Data subject rights, breach response and accountability

The regulation grants individuals a defined set of rights: access, rectification, erasure, restriction of processing, data portability, and the right to object. Controllers must respond to requests within one month under Article 12(3). Where requests are complex or numerous, that deadline can be extended by a further two months, provided the individual is notified within the initial one-month period.

Building a functioning rights-response workflow requires more than a contact email address. Organizations need documented procedures, staff training, and the technical ability to locate, export, or delete data on request. Failure to respond in time is itself a breach of the regulation and a trigger for regulatory complaints.

When a personal data breach occurs — whether through a cyberattack, accidental disclosure, or lost device — the clock starts immediately. Article 33 requires notification to the competent supervisory authority within 72 hours of the controller becoming aware, where the breach is likely to result in a risk to individuals' rights and freedoms. Late notifications must be accompanied by reasons for the delay. Where the breach is likely to result in a high risk to individuals, Article 34 requires direct notification to those affected without undue delay.

Accountability documentation is not optional. Controllers must maintain Records of Processing Activities (RoPA) under Article 30. Where processing is likely to result in a high risk to individuals, a Data Protection Impact Assessment (DPIA) must be conducted before processing begins. Organizations that process special categories of data at scale, conduct systematic large-scale monitoring, or qualify as public authorities must appoint a Data Protection Officer (DPO) under Article 37.

International transfers, vendors and digital operations

Transferring personal data outside the EEA requires a legal mechanism. The European Commission issues adequacy decisions for countries deemed to provide equivalent protection — the list includes countries such as Japan, Canada (for commercial organizations), and the UK (currently). For transfers to countries without an adequacy decision, organizations typically rely on Standard Contractual Clauses (SCCs) approved by the Commission, supplemented where necessary by technical and organizational measures identified through a transfer impact assessment.

The EU-U.S. Data Privacy Framework, adopted in July 2023, provides a mechanism for transfers to certified US organizations. Its legal stability has been questioned by privacy advocates, and organizations relying on it should monitor CJEU developments and EDPB guidance closely. Transfers to US cloud providers remain one of the most scrutinized areas of enforcement across European supervisory authorities.

Digital operations deserve particular attention. Cookie consent must meet the same standard as consent under the regulation — freely given, specific, and withdrawable. Analytics tools, advertising pixels, and session recording software all involve personal data processing. Email marketing to individuals in the EU also intersects with the ePrivacy Directive, which requires prior consent for direct marketing communications in most circumstances. Vendor onboarding processes should include a data protection review as a standard step, not an afterthought.

Enforcement, penalties and practical compliance priorities

Supervisory authorities across the EU have issued substantial fines under Articles 83(4) and 83(5). For serious violations — breaches of core principles, data subject rights, or international transfer rules — fines can reach €20 million or 4% of total annual worldwide turnover, whichever is higher. Less severe violations carry a ceiling of €10 million or 2% of global annual turnover. The Irish Data Protection Commission has been particularly active in enforcing against large technology companies established in Ireland.

Beyond fines, individuals can bring compensation claims under Article 82 for material or non-material damage resulting from a breach of the regulation. Supervisory authorities can also issue reprimands, order processing to cease, and impose temporary or permanent bans. Only qualified legal professionals can advise on the specific exposure a business faces in any given situation — the analysis depends on the nature of processing, jurisdiction, and the facts of any incident.

Practical compliance is best approached as a prioritized programme rather than an exhaustive simultaneous effort. The following actions address the highest-risk gaps for most organizations:

  • Audit all processing activities and build or update the Records of Processing Activities to reflect current data flows.
  • Verify the lawful basis for each processing purpose and document the reasoning in writing.
  • Review all vendor contracts against Article 28 requirements and address gaps before renewing agreements.
  • Test the breach response procedure with a tabletop exercise, ensuring the 72-hour notification window is understood across the IT, legal, and communications teams.
  • Audit cookie banners and consent mechanisms on all digital properties to confirm they meet the freely-given, withdrawable standard.
  • Confirm the legal basis for any international data transfers and document transfer impact assessments where SCCs are in use.

The regulation rewards organizations that treat data protection as an ongoing governance discipline. Supervisory authorities consistently apply lower penalties and take a more cooperative stance with controllers who can demonstrate documented accountability, proactive risk management, and good-faith engagement. Getting the fundamentals right — lawful basis, transparency, vendor contracts, breach readiness — reduces exposure significantly and builds the foundation for more advanced compliance work as regulatory expectations continue to develop.