+150 XP

How privacy law actually constrains what banks can do with data

You open a checking account at a mid-size US bank. Buried in the account agreement, a checkbox is already ticked: "share transaction data with marketing partners." Eighteen months later, that same bank knows you bought baby furniture three times last month. Its marketing team wants to send you a personal loan offer for a nursery renovation. Legally, can they?

The answer is: it depends on exactly which data, which jurisdiction, which consent screen, and which downstream use. That "it depends" is the whole lesson. Let's trace the consent trail.

The consent trail: account opening to marketing email

Step 1: Account opening. The bank collects your name, address, Social Security Number (SSN) or national ID, income, and initial deposit. In the US, this is governed partly by the Gramm-Leach-Bliley Act (GLBA, 1999), which requires banks to give customers a privacy notice and, for certain third-party sharing, an opt-out (not opt-in) choice.

Step 2: Transactions accumulate. Every debit card swipe, direct deposit, and bill pay creates a data point. Transaction data reveals income patterns, health conditions (pharmacy purchases), religious affiliation (donations), and family status (childcare payments) without you ever declaring any of it.

Step 3: Marketing wants in. The team wants to build a "life event" model: detect a probable pregnancy or new child from spending patterns, then trigger a targeted loan offer. Technically, the transaction data already sits in the bank's warehouse. The question is whether *using it this way* is lawful.

This is the gap most non-technical bankers miss: possessing data and having a lawful basis to use it for a specific purpose are two different things.

Where GDPR blocks it (if any customer is in the EU/UK)

The General Data Protection Regulation (GDPR), enforced across the EU/EEA (and mirrored by the UK GDPR post-Brexit), requires a specific lawful basis for each processing purpose, not one blanket basis for "having a relationship with you."

Opening the account and processing payments falls under "contract necessity," so no extra consent is needed. Inferring a pregnancy from spending and using it for marketing is a *new, incompatible purpose*. Under GDPR Article 6, this generally requires freely given, specific, informed consent, or at minimum a documented legitimate interest assessment that a regulator can inspect.

GDPR also restricts special category data (Article 9): health, religion, sexual orientation and similar. If the inferred "pregnancy signal" counts as health data, it's presumptively off-limits for marketing unless the customer gave explicit consent to that specific inference. A pre-ticked box at account opening does not satisfy this. Consent must be an affirmative act, and silence or pre-ticked boxes are invalid (ICO guidance on consent).

Penalty exposure is real: GDPR fines can reach 4% of global annual turnover. In January 2023, Ireland's Data Protection Commission fined Meta 390 million euros for relying on "contract necessity" to justify personalized advertising. Not a bank, but exactly the same mistake: stretching the basis for providing a service to cover marketing.

Where CCPA/CPRA blocks it (US, California residents)

The California Consumer Privacy Act (CCPA), strengthened by the California Privacy Rights Act (CPRA, effective 2023), works differently. It's opt-out based for most data, but gives consumers the right to limit use of "sensitive personal information," a category that includes precise geolocation and, arguably, health-inferred data.

Banks get a partial carve-out: data already regulated under GLBA is exempt from CCPA in many cases. The exemption covers GLBA-regulated *financial* uses, not secondary marketing inferences layered on top. A marketing team building a pregnancy-prediction model from transaction data is arguably stepping outside the GLBA exemption and back into CCPA territory, where California residents can opt out of the "sale or sharing" of personal information, including for cross-context behavioral advertising.

Other states matter too. Virginia (VCDPA), Colorado (CPA) and a growing list of others require opt-in consent for sensitive data, yet there is still no single federal privacy law in the US.

Where open banking rules block it

Open banking frameworks govern data a bank receives *from* other institutions via API when a customer links accounts. The main ones are the UK's Open Banking standard (created under a Competition and Markets Authority order) and PSD2, the EU's revised Payment Services Directive.

The core rule: data shared under open banking consent is purpose-limited by design. If a customer connects a savings account to a budgeting app, that data flow has a specific consent scope, which in the UK the provider must reconfirm with the customer every 90 days. A bank cannot repurpose data obtained this way for unrelated internal marketing without a fresh, specific consent.

The US picture is unsettled. The CFPB finalized its Section 1033 personal financial data rights rule in October 2024, and that version barred data recipients from using consumer-authorized data for secondary purposes like targeted advertising. In 2025 the CFPB announced it would reconsider the rule, opened a new rulemaking, and pushed back compliance dates while industry litigation was paused. Treat the secondary-use limits as a moving target and check the CFPB rule page before relying on them. Even without the rule, GLBA, state laws and the FTC's unfair-practices authority still apply.

The practical governance layer: what banks actually build

Because rules differ by jurisdiction, data type, and purpose, banks can't rely on legal judgment alone at the point of each marketing campaign. They build data governance infrastructure:

  • Purpose tagging: every data field is tagged with its lawful basis and permitted uses at ingestion. Transaction data tagged "payments processing only" cannot flow into a marketing feature store without a governance override.
  • Consent management platforms (CMPs), which track what each customer consented to, when, and for what purpose, so marketing queries can filter populations before launch.
  • Data lineage tracking, which documents where a field came from and every system it touched. Banks need this to answer "right to know" requests under GDPR Article 15 or CCPA.

A simplified purpose-tagging check might look like this in a data pipeline:

python
def can_use_for_marketing(record):
    if record['data_source'] == 'open_banking_api':
        return record['consent_scope'] == 'marketing' and not record['consent_expired']
    if record['contains_sensitive_inference']:
        return record['explicit_opt_in'] is True
    return record['gdpr_lawful_basis'] in ('consent', 'legitimate_interest_documented')

This is a toy example, but it reflects the real logic banks embed: the check happens before the campaign runs, not after a regulator asks.

Knowledge check

1. A bank's data warehouse already contains transaction data that could reveal a customer's likely pregnancy. What is the key legal principle the lesson emphasizes about using this data for a targeted loan offer?

2. Why does the lesson highlight that transaction data can reveal health conditions, religious affiliation, and family status even though the customer never directly disclosed these things?

3. Under GLBA, how does the required consent mechanism for certain third-party data sharing compare to what GDPR generally requires for similar processing?

MULTIPLE CHOICE

4. Select ALL correct answers about why the answer to 'can the bank send this marketing offer?' is described as 'it depends.'

Select all the correct answers.

MULTIPLE CHOICE

5. Select ALL correct answers about what happens at each stage of the 'consent trail' described in the lesson.

Select all the correct answers.

The audits that actually catch violations

Governance policy is only as good as the audit that verifies it. Three checks a bank's data and compliance team runs regularly:

  1. Consent-to-usage reconciliation: sample marketing campaign target lists and trace each customer back to a documented, non-expired consent matching that exact purpose. Mismatches are among the most common findings in EU Data Protection Authority (DPA) investigations.
  1. Special category leakage scans: automated scans of feature stores and marketing datasets for fields correlated with health, religion, or other protected categories, even when not labeled as such. A "baby product merchant category code" flag is a proxy for a protected inference.
  1. Cross-border transfer checks: if a US bank's analytics vendor processes EU customer data, GDPR Chapter V requires a valid transfer mechanism, such as Standard Contractual Clauses or the EU-US Data Privacy Framework (adopted 2023). The EU General Court upheld the framework in September 2025, but an appeal is pending, so many banks keep SCCs in place as a fallback.

GDPR Explained in Simple Terms

Watch on YouTube

Key Takeaways

  • Possession is not permission. A bank can legally hold transaction data for payments processing while being barred from using that same data for a marketing inference, because the lawful basis depends on the *purpose*, not the dataset.
  • GDPR requires explicit, purpose-specific consent for sensitive inferences like health-adjacent life events. Pre-ticked boxes and bundled consent at account opening don't count.
  • CCPA/CPRA is opt-out by default with extra protection for sensitive personal information, and GLBA exemptions typically don't cover secondary marketing uses.
  • Open banking consent is scoped by purpose and time. In the US, the CFPB's 1033 rule is being reconsidered, so its exact limits on secondary use are still in flux.
  • Purpose tagging, consent management platforms and lineage tools turn regulatory obligations into pipeline checks that run before a campaign launches, not after a fine arrives.