Understand the overlap, not a supposed conflict

The FCA and ICO’s joint statement explains that data protection law does not prevent firms from supporting customers in vulnerable circumstances. It also makes clear that firms must meet privacy requirements while delivering good consumer outcomes. Consumer Duty is not permission to collect every potentially useful detail, and UK GDPR is not a reason to refuse all vulnerability information.

First establish which regulated activities, products and customers are involved. The Consumer Duty’s scope and other FCA requirements need a proper assessment; they should not be assumed to apply identically to every business calling itself a financial adviser or service provider. This guide addresses the handling of personal information alongside that assessment. It is not product, investment or regulatory-perimeter advice.

Translate a disclosure into a useful support action

Our suggested starting point is the service adjustment: what needs to happen differently? A customer may need written follow-up, additional explanation or an alternative communication channel. Record what staff need to provide that support, with enough context to avoid misunderstanding. Do not automatically convert a request for accessible correspondence into an extensive medical questionnaire.

Train staff to distinguish what the customer said, what the firm observed and what remains uncertain. Avoid loaded labels such as “difficult” or “incapable”. A hypothetical good record might specify an agreed communication preference and review date rather than a diagnosis inferred by a call handler. Even a short preference can reveal sensitive information in context, so minimising detail does not remove the need to assess it.

Apply the correct conditions to the actual information

Financial information is personal data when it relates to an identifiable person, but it is not automatically special-category data under Article 9. A record about health or an inference revealing health can be. Where Article 9 applies, the firm needs both an Article 6 lawful basis and an applicable special-category condition. Criminal-offence information has a separate framework and should not be treated as another health-data category.

Do not assume that ordinary contractual necessity covers every support note, or that a general reference to regulatory duties supplies the complete answer. Identify the concrete obligation or interest and explain necessity. If relying on a substantial-public-interest condition in domestic law, check the exact Schedule 1 requirements and whether an appropriate policy document is required. Explicit consent must be suitable and valid, not a box added after collection.

Design permissions around the purpose

A practical architecture separates the support action visible to front-line staff from more detailed information available only where necessary. Test whether marketing teams, external administrators or ordinary customer-service searches can see the full record. Where the system cannot separate permissions, consider whether the sensitive detail belongs there at all. Convenience is not the same as necessity.

Review exports, call recordings and support transcripts as well as structured fields. Information carefully protected inside one application can become widely accessible in a spreadsheet. Keep a process for corrections and changing circumstances: a temporary difficulty should not become an indefinite assessment of someone’s ability. Set retention by record type and purpose, recognising any specific regulatory obligations rather than adopting one period for everything.

Share across firms only with a defined reason

A broker, product manufacturer and servicing firm may each need different information to support a customer. Before sharing, establish the recipient’s role, purpose, lawful basis and minimum required content. Explain the relevant sharing to the individual, subject to any properly applicable exception. A group structure or distribution agreement does not by itself authorise unrestricted access to the customer’s full history.

Our recommended handover test is to ask the receiving firm what action it will take with each proposed field. If a communication adjustment is sufficient, ask why diagnostic information is included. Verify recipient details and agree how corrections will be passed on. Avoid a process in which an obsolete vulnerability flag is copied between systems while responsibility for checking it belongs to nobody.

Monitor outcomes without creating another uncontrolled dataset

Firms may need evidence that customers in vulnerable circumstances receive appropriate outcomes. Choose measures that answer an actual service question, such as whether an agreed communication adjustment was provided or whether a customer repeatedly abandoned a process. Use suitably aggregated outputs where possible, but remember that small groups or detailed breakdowns may still identify people.

If analytics infer vulnerability from transactions or behaviour, assess accuracy, fairness, transparency and potential impact before using them. A model can be wrong or reinforce disadvantage. Determine whether a DPIA is required and assess the rules for significant solely automated decisions where applicable. A human reviewing a dashboard must have genuine authority and sufficient information to challenge the inference, not merely approve it by default.

Keep fraud, complaints and other duties distinct

Fraud prevention, anti-money-laundering checks, support and marketing are different purposes. Document their separate requirements rather than treating all financial information as available for all of them. Some disclosures or explanations may be restricted by specific law, but the existence of a fraud team does not create a general exemption from transparency or access rights. Escalate difficult cases to appropriately qualified advisers.

Run a short scenario review across customer service, compliance, privacy and technology teams. Can a customer see and correct an inaccurate note? Can staff deliver an adjustment without exposing unnecessary detail? Can a supplier return or delete the relevant record? Can the firm explain why it retained information after a relationship ended? These operational checks reveal whether policies translate into workable support.

Make accountability visible

Assign a named owner to the vulnerability-data process, define the evidence needed for changes and review a sample of actual records. Include both failures to provide support and excessive disclosure in quality assurance. Record decisions about purpose, legal conditions, access and review dates so that a change of staff does not erase the reasoning.

Specialist financial-services advice is needed where this work affects regulated obligations, automated eligibility decisions or contested disclosures. The aim is not to collect a complete biography. It is to ensure that relevant information reaches the people who can help, while preventing the same information from becoming a source of avoidable harm.

Sources and further reading

Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.

This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.