+150 XP

Banking · Consent, purpose limitation and the wall between products

Your mortgage servicer knows your income, your payment history, and how close you've come to missing a payment. Your bank's auto lending unit would love that data to price your next car loan. In the EU and UK it often can't simply take it, and in the US the bank's own privacy notice, fair lending rules and credit reporting law put real limits on how it does. The data may sit inside the same bank. The problem is that it was collected to originate and service your mortgage, and that purpose follows it around.

This is purpose limitation, one of the quieter but most operationally demanding principles in data privacy law. The question regulators ask is whether this specific use is covered by what the customer was told and agreed to. Possession of the data doesn't settle it. For a bank running dozens of products across retail, wealth, cards and lending, answering that question at scale takes engineering work. A compliance memo won't do it.

The legal wall, in plain terms

Purpose limitation means personal data collected for a specified, explicit purpose cannot be reused for an incompatible purpose without a new legal basis, such as fresh consent or another lawful ground.

In the EU, this is codified in the GDPR (General Data Protection Regulation), Article 5(1)(b). It sits alongside data minimization and storage limitation as a core principle. The UK GDPR kept the same principle after Brexit, but the Data (Use and Access) Act 2025 amended it. The Act sets out when a new purpose counts as compatible and lists some purposes treated as compatible by default, such as certain crime prevention and safeguarding uses. Marketing a different product is not on that list, so a UK bank still needs a proper basis to repurpose mortgage data for cross-selling.

In the US, there's no single federal privacy law as sweeping as GDPR, and the rules are looser inside one legal entity. The wall is built from several pieces:

  • The Gramm-Leach-Bliley Act (GLBA, 1999) requires financial institutions to give customers a privacy notice and an opt-out right before sharing certain nonpublic personal information with non-affiliated third parties. It does not restrict a bank's use of data across its own product lines within the same entity.
  • The Fair Credit Reporting Act (FCRA) limits sharing certain consumer report information with affiliates, and its affiliate marketing rule requires notice and an opt-out before an affiliate uses that data to market to you.
  • Whatever the bank promised in its privacy notice binds it. Using data in a way the notice didn't disclose can be treated as deceptive by the FTC or the Consumer Financial Protection Bureau (CFPB).
  • State laws add more: the California Consumer Privacy Act (CCPA), as amended by the CPRA, gives consumers rights to limit use of sensitive data. Note that data already covered by GLBA is largely exempt from CCPA.

In the EU, national Data Protection Authorities (DPAs), coordinated through the European Data Protection Board (EDPB), enforce GDPR. The UK's regulator is the ICO.

Why "we already have the data" isn't a defense

A common misconception, even among experienced bankers, is that once data sits inside "the bank," it's fair game internally. Under GDPR, regulators reject this outright. The mortgage unit and the auto lending unit may be the same legal entity, but the purpose under which the data was captured still binds it.

Concretely: if a customer's mortgage application discloses a debt-to-income ratio, that figure was collected to underwrite a mortgage. Feeding it, without the right basis, into an auto-loan pricing model could:

  1. Contradict the privacy notice the customer received, which is a deception risk in the US.
  2. Breach GDPR or UK GDPR purpose limitation if EU or UK customers are involved.
  3. Raise fair lending questions, since regulators look at whether new data inputs to pricing disproportionately affect protected groups.

This is also why consent is not a single checkbox. Under GDPR it must be specific, informed and freely given, and consent tied to a mortgage doesn't automatically cover cross-selling an auto loan. A separate, clear opt-in is generally needed for the new purpose.

How the wall gets built into the data pipeline

Legal principles only work if they survive contact with production systems. Banks operationalize purpose limitation through purpose tagging: metadata attached to data at the point of collection that travels with it through every downstream system.

A simplified version looks like this:

customer_data_record:
  customer_id: 88213
  field: "monthly_income"
  value: 7200
  source_purpose: "mortgage_underwriting"
  consent_id: "CNS-2024-0091"
  allowed_uses: ["mortgage_servicing", "mortgage_risk_reporting"]
  cross_product_use: false
  retention_expiry: "2031-06-01"

Any system, model or analyst querying this field has to check cross_product_use and allowed_uses before ingesting it. If the auto loan pricing model's data pull doesn't filter on purpose tags, it can silently ingest out-of-scope data. Auditors look for exactly that failure.

This is enforced through:

  • Data lineage tools that trace a field from source system to every downstream table, dashboard or model feature. Collibra and Informatica are common in banking; see OECD's overview of data governance frameworks for the policy context.
  • Consent management platforms (CMPs) that store which consent ID authorizes which use, and revoke access when consent is withdrawn.
  • Access control layers in the data warehouse that block queries joining tables across "purpose domains" unless an explicit new consent record exists.

The practical checks and audits

For a data governance team, purpose limitation is a recurring audit cycle. Typical checks:

  • Purpose-tag coverage audit: what percentage of customer data fields have a valid, non-null purpose tag? Untagged legacy data is a common finding in regulatory exams.
  • Cross-domain query monitoring: logging and reviewing any query that joins data from two product purposes, for example mortgage and auto lending schemas.
  • Consent-to-use reconciliation: sampling live model features and tracing each back to a valid consent record.
  • Model feature audits: for any ML model, a documented feature list mapped to its permitted purpose, reviewed before deployment. This overlaps with model risk management under the Fed's SR 11-7 guidance in the US.
  • Withdrawal propagation test: when a customer revokes consent, does the field get excluded from the next model retrain, or does it linger in a cached feature store?

That last one is where many banks get caught out. A consent withdrawal recorded in a CRM doesn't help if the machine learning feature store refreshes weekly from a stale snapshot.

Knowledge check

1. A bank's mortgage servicing unit wants to share a customer's payment history with the bank's auto lending unit to price a car loan. Why does purpose limitation block this by default?

2. What is the key question purpose limitation asks, as distinguished from a simple data-access question?

3. Why does enforcing purpose limitation at a large bank require 'real engineering, not just a compliance memo'?

MULTIPLE CHOICE

4. Select ALL correct answers about how purpose limitation is enforced in the US financial sector, given the absence of a single sweeping federal privacy law like GDPR.

Select all the correct answers.

MULTIPLE CHOICE

5. Select ALL correct answers about the GDPR's treatment of purpose limitation.

Select all the correct answers.

Where this gets tested: cross-selling and open banking

Two live pressure points in 2026 make this more than theoretical.

Cross-selling analytics. Banks want unified customer views to recommend products. That's legitimate, but it usually requires a distinct marketing and cross-sell consent, separate from the consent to service an account. Building a single customer data platform (CDP) without segmenting by purpose is a common audit failure.

Open banking and data sharing. Under the EU's PSD2 and its planned successors (PSD3 and the Payment Services Regulation), and the UK's Open Banking regime, customers authorize third parties to access account data via APIs. Consent here is directional (which third party) and time-bound. In the UK, since 2022, the customer reconfirms access with the third-party provider every 90 days instead of reauthenticating with the bank.

The US picture is unsettled. The CFPB finalized its Section 1033 open banking rule in October 2024, requiring purpose-specific, revocable authorization for data sharing. In 2025 the bureau said it would reconsider the rule and opened a new rulemaking, and a federal court stayed the compliance dates. Check the CFPB's Section 1033 page for current status before building compliance plans around the 2024 text.

🎬 [VIDEO: "GDPR Explained: Purpose Limitation and Data Minimization" - youtube.com/results?search_query=gdpr+purpose+limitation+explained - search for a short explainer that walks through Article 5 principles with concrete examples, useful as a primer before applying them to banking data flows]

Key Takeaways

  • Purpose limitation means data collected for one purpose (mortgage underwriting) can't be reused for an incompatible one (auto loan pricing) without a new legal basis, usually fresh, specific consent.
  • In the EU the rule is GDPR Article 5(1)(b). The UK version was amended by the Data (Use and Access) Act 2025, which clarifies compatible purposes but doesn't open the door to cross-selling.
  • US limits are patchier: GLBA covers sharing with non-affiliated third parties, FCRA covers affiliate sharing and marketing, and the bank's own privacy notice binds internal use.
  • Purpose tagging, lineage tools and recurring audits (tag coverage, cross-domain queries, consent-to-feature reconciliation, withdrawal propagation) are how the wall holds in practice.
  • Open banking adds directional, time-bound consent. The US Section 1033 rule is under reconsideration, so treat its 2024 requirements as provisional.

Frequently asked questions

What does purpose limitation actually mean for a bank?

Purpose limitation means personal data collected for a specified, explicit purpose cannot be reused for a materially different purpose without a new legal basis, usually fresh consent. For a bank, that means mortgage underwriting data cannot feed an auto loan pricing model just because both units sit inside the same legal entity. The question regulators ask is not "do you hold the data?" but "did the customer agree to this specific use?"

Can a bank reuse mortgage data for auto loan pricing if it's the same legal entity?

No, not without a new legal basis. The purpose under which the data was captured continues to bind it, even inside one entity, so an unconsented cross-use can breach the original privacy notice (GLBA and CCPA in the US), GDPR Article 5(1)(b) purpose limitation where EU data is involved, and fair lending expectations that the CFPB examines. "We already have the data" is not a defense regulators accept.

What's the difference between GDPR purpose limitation and US rules like GLBA and FCRA?

GDPR Article 5(1)(b) states purpose limitation as a general principle applying to all personal data, with the UK GDPR mirroring it. The US has no single equivalent: GLBA requires a privacy notice and an opt-out before sharing nonpublic personal information with non-affiliated third parties, FCRA restricts using credit-report-sourced data beyond what was disclosed, and state laws like CCPA/CPRA add rights to limit use of sensitive data. Enforcement also splits, DPAs coordinated by the EDPB in Europe, the CFPB on the US banking side.

How do you enforce purpose limitation technically in a data pipeline?

Through purpose tagging: metadata attached to each data field at collection that travels downstream, recording the source purpose, the consent ID, the allowed uses, whether cross-product use is permitted, and a retention expiry. Any model or query has to filter on those tags before ingesting the field. This is backed by data lineage tools, consent management platforms that revoke access when consent is withdrawn, and warehouse access controls that block joins across purpose domains without a new consent record.

Which audits should a bank's data governance team run to prove purpose limitation?

Five recurring checks: purpose-tag coverage (what share of customer fields carry a valid, non-null tag, since untagged legacy data is a frequent exam finding), cross-domain query monitoring for joins between two product purposes, consent-to-use reconciliation by sampling live model features back to a consent record, model feature audits mapping each feature to its permitted purpose before deployment, and consent-withdrawal propagation tests. The last one catches the most banks: a withdrawal logged in the CRM is useless if the machine learning feature store still refreshes from a stale snapshot.

Does a bank need separate consent for cross-selling and for open banking data sharing?

Yes, both are distinct purposes. Cross-sell analytics and unified customer views generally require a "marketing and cross-sell" consent separate from the "service this account" consent, which is why building a single customer data platform without segmenting by purpose is a common audit failure. Open banking adds directionality and time limits: PSD2 and UK Open Banking consents name a specific third party and expire, often every 90 days under UK rules, while the CFPB's Section 1033 rule finalized in 2024 likewise requires purpose-specific, revocable authorization.