Evaluates data privacy practices against GLBA, CCPA, and state privacy requirements. Use when assessing financial privacy compliance, managing opt-out requirements, or documenting data practices.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add CaseMark/skills --skill managing-privacy-compliance-financial --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Managing Privacy Compliance Financial?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/casemark-managing-privacy-compliance-financial)More formats (shields.io, HTML) on the badges page.
---
name: managing-privacy-compliance-financial
language: en
description: Evaluates data privacy practices against GLBA, CCPA, and state privacy requirements. Use when assessing financial privacy compliance, managing opt-out requirements, or documenting data practices.
tags:
- management
- financial-compliance
- compliance
metadata:
author: casemark
practice_areas:
- Regulatory Compliance
- Financial Regulation
- Compliance
document_types:
- Management Report
skill_modes:
- Management
- Coordination
---
# Managing Privacy Compliance Financial
Evaluates financial institution data privacy practices against GLBA, CCPA/CPRA, and state-level privacy requirements. Produces gap analyses, opt-out compliance assessments, and privacy notice audits for banks, broker-dealers, insurance companies, and fintech platforms.
## When To Use
- Assessing whether a financial institution's privacy notices satisfy GLBA Regulation P requirements
- Evaluating CCPA/CPRA compliance for financial data that falls outside the GLBA exemption
- Auditing opt-out/opt-in mechanisms for nonpublic personal information (NPI) sharing
- Reviewing data-sharing agreements with affiliates, nonaffiliates, and joint-marketing partners
- Preparing for state privacy law obligations (e.g., VCDPA, CPA, TDPSA) as they apply to financial entities
- Documenting a privacy compliance program ahead of regulatory examination
## Inputs To Gather
- Entity type and regulatory charter (bank, credit union, broker-dealer, insurance company, RIA, fintech) [VERIFY]
- Current privacy notice and any annual re-delivery records
- Categories of NPI collected: account numbers, transaction history, credit data, application data
- Data-sharing map: affiliates, nonaffiliated third parties, joint-marketing partners, service providers
- Existing opt-out mechanism details (mail-in form, online portal, toll-free number)
- State(s) of operation and customer residence — determines which state privacy laws layer on top of GLBA [VERIFY]
- Most recent examination findings or self-assessment results related to privacy
- Relevant exception claims (e.g., GLBA exemption from CCPA for specific data categories)
## Workflow
1. **Classify the entity and applicable regime**
- Determine whether the entity is a "financial institution" under GLBA (15 U.S.C. § 6809(3)) [VERIFY]
- Identify which data categories qualify as NPI versus publicly available information
- Map state-specific overlays: CCPA/CPRA applies to California consumers for data not covered by the GLBA exemption; check VCDPA, CPA, TDPSA thresholds [VERIFY]
2. **Audit privacy notices**
- Compare the initial and annual privacy notices against Regulation P model forms (12 CFR § 1016, Appendix)
- Check for required disclosures: categories of NPI collected, categories shared, opt-out rights, safeguarding practices
- Verify delivery method compliance: initial notice at customer relationship establishment, annual notice timing [VERIFY]
- Flag any missing or ambiguous categories in the sharing disclosure table
3. **Evaluate opt-out/opt-in mechanisms**
- Confirm opt-out notice is clear, conspicuous, and provides a reasonable method to exercise the right
- Check whether affiliate-sharing triggers FCRA affiliate-marketing opt-out (separate from GLBA opt-out) [VERIFY]
- For state laws requiring opt-in (e.g., financial health data under CCPA/CPRA), verify affirmative consent mechanisms
- Assess opt-out honoring timelines — Regulation P requires compliance within a reasonable period (generally 30 days)
4. **Review data-sharing agreements and exceptions**
- Categorize each third-party relationship: joint marketing, service provider, nonaffiliate
- Confirm service-provider and joint-marketing exceptions include required contractual provisions (confidentiality, use limitations)
- Identify any sharing that falls outside safe-harbor exceptions and requires opt-out
5. **Assess CCPA/CPRA intersection**
- Determine which data categories are exempt under CCPA § 1798.145(e) (GLBA-covered data) vs. which are not
- For non-exempt data: verify CCPA privacy policy disclosures, "Do Not Sell/Share" mechanisms, and data subject request workflows
- Evaluate whether the institution qualifies as a "business" under CCPA thresholds [VERIFY]
6. **Compile gap analysis and remediation roadmap**
- List each compliance gap with severity (critical / moderate / low)
- Assign remediation owners, deadlines, and required documentation updates
- Prioritize: notice deficiencies and opt-out failures carry direct regulatory risk
## Output
- **Privacy Compliance Assessment Report** containing:
- Regulatory applicability matrix (GLBA, Regulation P, CCPA/CPRA, state laws)
- Privacy notice audit findings with line-item deficiencies
- Opt-out mechanism evaluation and consumer-experience assessment
- Data-sharing map with exception classification for each relationship
- CCPA/CPRA gap analysis for non-GLBA-exempt data
- Prioritized remediation roadmap with owners and target dates
- Summary of [VERIFY] items requiring legal or jurisdictional confirmation
## Quality Checks
- Every data-sharing relationship is classified under an explicit GLBA exception or flagged as requiring opt-out
- Privacy notice language is compared against the Regulation P model form — deviations are specifically identified
- CCPA exemption claims cite the specific data category and collection context, not a blanket entity-level exemption
- State law applicability is determined by customer residence, not entity headquarters [VERIFY]
- Opt-out mechanisms are tested or described with sufficient specificity to confirm consumer usability
- All jurisdiction-dependent conclusions are marked [VERIFY] for legal review
- Report distinguishes between confirmed findings and assumptions clearly throughout
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!