Understanding GDPR: What the Financial Services Community Needs to Know

Explore GDPR essentials for financial services, focusing on data protection, compliance, and maintaining trust in a data-driven world.

The General Data Protection Regulation (GDPR) entered into force on May 24, 2016, and became applicable on May 25, 2018, heralding a new era of data protection and privacy across the European Union. These dates are distinguished in Article 99 and the official legislative record. For the financial services community, understanding and complying with GDPR is not just a regulatory requirement—it's a cornerstone of maintaining trust and integrity in an increasingly data-driven world.

The Essentials of GDPR

GDPR is a comprehensive data protection law. Its territorial scope includes processing in the context of an EU establishment, regardless of where the processing occurs. It also covers certain processing by organizations outside the EU when they offer goods or services to people in the EU or monitor their behavior there; simply processing data about someone in the EU does not automatically bring every overseas organization within scope. See the European Commission's guidance on GDPR application. Its primary goals are to give individuals more control over their personal data and to standardize data protection laws across Europe. Here are some key aspects that financial services providers must understand:

  • Data Subject Rights: Individuals have enhanced rights under GDPR, including the right to access, rectify, and, in specified circumstances, erase their personal data. Financial institutions acting as controllers must respond without undue delay and normally within one month of receiving a request. An extension of up to two further months is permitted where necessary because of the complexity or number of requests, with notice and reasons provided within the first month. Erasure is not absolute: data needed to meet an applicable legal retention obligation may be retained. See Article 12 and the European Data Protection Board's guidance on erasure requests.

  • Lawful Basis for Processing: Organizations must have a lawful basis for processing personal data. This could be consent, contractual necessity, legal obligation, vital interests, public task, or legitimate interests, subject to the conditions in Article 6.

  • Data Protection by Design and Default: GDPR requires controllers to integrate appropriate data protection measures into the design and operation of systems and processes. By default, processing must be limited to personal data necessary for each specific purpose, including limits on collection, use, retention and accessibility. See the European Commission's explanation of protection by design and default.

  • Data Breach Notification: A controller must notify the competent supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of a personal data breach, unless it is unlikely to result in a risk to individuals' rights and freedoms. Late notification must include reasons for the delay. Processors must notify the controller without undue delay. Affected individuals must also be informed without undue delay when a breach is likely to result in a high risk, subject to the exceptions in Article 34. All personal data breaches must be documented, even when notification is not required. See the European Data Protection Board's breach guidance.

In our view, GDPR is not just about compliance; it's about cultivating trust and transparency in how we handle personal data.

Challenges and Implications for Financial Services

The financial services industry faces particular GDPR challenges due to the volume and sensitivity of the data it handles. Here are some specific challenges and implications:

  • Data Inventory and Mapping: Financial services firms need a clear understanding of what personal data they hold, where it is stored, and who has access to it. Comprehensive data inventory and mapping exercises are practical ways to support this understanding and the applicable record-keeping requirements in Article 30.

  • Third-Party Management: Many financial services firms rely on third-party vendors. Where a vendor processes personal data on a firm's behalf, the controller must use a processor providing sufficient guarantees of appropriate technical and organizational measures and put in place a binding contract or other legal act meeting Article 28. Due diligence and contractual safeguards should reflect the vendor's actual role, rather than assuming every vendor is a processor. See the Irish Data Protection Commission's guide to controller-processor contracts.

  • Cross-Border Data Transfers: GDPR's international-transfer rules apply to transfers to countries outside the European Economic Area (EEA), which includes the EU, Iceland, Liechtenstein and Norway. Financial institutions must evaluate the applicable transfer mechanism, such as an adequacy decision or appropriate safeguards. See the European Commission's international-transfer guidance. When relying on safeguards such as standard contractual clauses, firms must assess whether destination-country laws and practices undermine their effectiveness and adopt supplementary measures where needed, as explained in the European Data Protection Board's transfer guidance.

Practical Steps for Compliance

Achieving GDPR compliance is a significant undertaking, but it is manageable with a structured approach. Here are some practical steps for financial services providers:

  • Conduct a GDPR Readiness Assessment: Evaluate your current data protection practices against GDPR requirements to identify gaps and areas for improvement.

  • Develop a Compliance Plan: Create a detailed roadmap that outlines the steps needed to achieve compliance, including timelines and responsibilities.

  • Train and Educate Staff: Ensure that all employees are aware of GDPR obligations and understand their role in maintaining compliance.

  • Implement Technical and Organizational Measures: Deploy appropriate security measures, such as encryption and access controls, to protect personal data.

  • Establish a Data Breach Response Plan: Develop a clear and efficient process for identifying, reporting, and mitigating data breaches.

Conclusion: Embrace GDPR as an Opportunity

While GDPR presents challenges, it also offers significant opportunities for the financial services community to enhance data management practices and strengthen customer trust. By embracing GDPR as more than a compliance obligation, organizations can position themselves as leaders in data protection and privacy.

As we continue to navigate the complexities of data regulation, remember that compliance is an ongoing journey. Stay informed, stay proactive, and above all, keep the trust of your clients at the forefront of your efforts. For further insights and guidance, consider engaging with cybersecurity experts to ensure your organization remains at the cutting edge of data protection.

Browse all insights · Contact Bart McDonough