Civil Law

How Does GDPR Affect Your Business and Customer Data?

How Does GDPR Affect Your Business and Customer Data?

GDPR — the General Data Protection Regulation — has reshaped how businesses across Europe and beyond handle personal information. Since it began applying on 25 May 2018, it has created binding obligations for any organisation that collects, stores or uses data about individuals in the European Economic Area. The regulation is not a bureaucratic formality. It defines real legal duties, real rights for customers, and real financial penalties for non-compliance. Whether you run an e-commerce platform, a professional services firm or a SaaS product, understanding what GDPR requires is not optional. Only a qualified data protection lawyer can advise on your specific situation, but every business owner and compliance manager should understand the framework before that conversation takes place.

What GDPR Means for Modern Businesses

The regulation applies to any organisation established in the European Economic Area, and also to businesses outside the EEA that offer goods or services to individuals there or monitor their behaviour. This extraterritorial reach under Article 3 means a US-based app developer, a Canadian retailer or an Australian analytics company can all fall within scope. Physical presence in Europe is not the trigger — targeting European residents is.

At its core, GDPR governs personal data: any information relating to an identified or identifiable natural person. A name, an email address, an IP address, a location ping — all qualify. The regulation draws a further distinction between controllers, who determine the purposes and means of processing, and processors, who act on a controller's instructions. A business running its own CRM is a controller. The cloud vendor hosting that CRM is typically a processor.

The regulation also identifies special categories of personal data — health records, biometric identifiers, genetic data, political opinions, religious beliefs, trade-union membership, and information about sex life or sexual orientation. Processing these categories triggers stricter conditions and, in many cases, an explicit consent requirement or a specific statutory exemption.

Understanding which role your organisation occupies matters enormously. Controllers bear the primary compliance burden. Processors carry their own obligations, including security duties and sub-processor controls, but they cannot determine how data is used. Misidentifying your role leads to gaps in contracts, accountability records and breach-response procedures that regulators notice quickly.

How GDPR Changes the Way You Collect and Use Customer Data

Before collecting a single data point, a business must identify a lawful basis for processing under Article 6. Six bases exist: consent, contract performance, legal obligation, vital interests, public task and legitimate interests. Consent is not the default — it is one option among several, and it carries specific requirements including the ability to withdraw freely at any time.

Transparency sits alongside lawful basis as a parallel obligation. Privacy notices must tell individuals who you are, why you are processing their data, how long you will keep it, who receives it and what rights they hold. Burying this information in dense legal text does not satisfy the requirement. The regulation demands clear, plain language.

Data minimisation is one of the regulation's most operationally disruptive principles. Organisations must collect only data that is adequate, relevant and limited to what is necessary for the stated purpose. Collecting fields "just in case" they become useful later violates this principle directly. The same logic applies to retention: data held longer than necessary becomes a liability, not an asset.

Privacy by design under Article 25 requires data protection to be built into systems and processes from the start, not added as an afterthought. For businesses launching new products, this means conducting a Data Protection Impact Assessment before going live whenever processing is likely to result in a high risk to individuals — particularly when deploying new technologies or processing sensitive data at scale. Marketing teams running behavioural profiling, retargeting campaigns or automated segmentation need to map their processing against these principles carefully.

Customer Rights and the Operational Duties Behind Them

GDPR grants individuals a substantial set of rights over their personal data. Businesses must build processes to handle these requests reliably, because failing to respond is itself an infringement. The standard deadline for responding to any data subject request is one month from receipt, extendable by up to two further months for complex or numerous requests — provided the individual is informed of the extension within the first month.

The main rights individuals hold include:

  • Right of access — to receive a copy of their personal data and information about how it is used
  • Right to rectification — to have inaccurate data corrected without undue delay
  • Right to erasure — to request deletion where data is no longer necessary, consent is withdrawn, or processing was unlawful
  • Right to restriction — to limit processing in defined circumstances while a dispute is resolved
  • Right to data portability — to receive data in a structured, machine-readable format and transfer it to another provider
  • Right to object — to stop processing based on legitimate interests or for direct marketing purposes
  • Rights related to automated decisions — to avoid being subject to decisions based solely on automated processing that produce significant effects

Verifying the identity of the person making a request is permitted and sometimes necessary, but businesses cannot use identity checks as a barrier to delay or avoid compliance. Requests submitted through unusual channels — a social media message, a verbal complaint — still start the clock. Operationally, this means training customer-facing staff to recognise and escalate data subject requests the moment they arrive.

Security, Breaches and Third-Party Data Processors

Article 32 requires controllers and processors to implement appropriate technical and organisational security measures, taking into account the nature of the data, the risks involved and the state of available technology. Encryption, pseudonymisation, access controls and regular testing all feature in this analysis. The standard is not perfection — it is proportionality to the risk.

When a breach occurs, the timeline becomes unforgiving. A controller must notify the competent supervisory authority within 72 hours of becoming aware of the breach, unless it is unlikely to result in a risk to individuals' rights and freedoms. Where the breach is likely to result in a high risk to those individuals, the controller must also communicate it to affected data subjects without undue delay under Article 34. These are two separate obligations with different thresholds.

Immediate steps when a breach is identified should include:

  • Containing the breach and preserving evidence
  • Assessing the scope, nature and likely impact on individuals
  • Notifying the relevant supervisory authority if the risk threshold is met
  • Communicating directly to affected individuals if a high risk to their rights exists

Third-party processors — cloud platforms, payment processors, marketing automation tools, analytics providers — 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, and impose security and confidentiality obligations on the processor. A business cannot outsource its compliance risk by signing up to a vendor's standard terms without checking whether those terms are actually GDPR-compliant.

Enforcement, International Transfers and Business Risk

The European Data Protection Board coordinates enforcement across national supervisory authorities, while each EU and EEA member state has its own authority — the ICO in the UK, the CNIL in France, the BfDI in Germany. The one-stop-shop mechanism means that businesses with cross-border processing typically deal with a lead supervisory authority based on their main establishment, though local authorities retain competence in certain situations.

Fines under GDPR operate on a two-tier structure. The most serious infringements — breaching core principles, violating data subject rights, or conducting unlawful international transfers — can attract fines of up to €20 million or 4% of total worldwide annual turnover, whichever is higher. A second tier covering obligations such as security, record-keeping and processor contracts carries a maximum of €10 million or 2% of global annual turnover. Fines are not automatic; authorities assess factors including the severity of the infringement, whether it was intentional or negligent, and the degree of cooperation shown.

International data transfers require specific legal mechanisms when personal data leaves the EEA. Adequacy decisions from the European Commission cover a defined list of countries. Where no adequacy decision exists, Standard Contractual Clauses or Binding Corporate Rules are typically used. The UK operates a parallel regime under the UK GDPR and the Data Protection Act 2018, enforced by the ICO. The EU-UK adequacy arrangement was renewed in 2025, but its ongoing status should be verified before relying on it for transfer planning.

Compensation claims from individuals add a civil dimension to the regulatory risk. Data subjects can bring claims before national courts for material or non-material damage caused by a GDPR infringement. The limitation periods for such claims depend on the procedural law of the relevant member state or, in the UK, on domestic rules. Any business processing personal data at scale should treat GDPR compliance as an ongoing operational discipline, not a one-time project — and seek specialist legal advice when processing activities change, new technologies are adopted, or a breach occurs.