Study guide

5.3 Handling Sensitive Information: PII, SPII, Privacy Laws, and Breach Reporting

ACAMS Certified AML FinTech Compliance Associate CAFCA

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CAFCA Exam Overview and Study Strategy

1.1 CAFCA Exam Format, Official Domains, and Study Strategy

2 Chapter 2: Domain 1: FinTech Business Models and Their Vulnerabilities

2.1 Neobanks, Challenger Banks, and Digital Banking Models 2.2 Payment Processors, Gateways, and Merchant Acquirers 2.3 Buy Now, Pay Later (BNPL) and Alternative Credit 2.4 BaaS Architecture, Embedded Finance, and Program Structures

3 Chapter 3: Domain 1: Financial Crime Types and the Regulatory Perimeter

3.1 Types of Financial Crime and Predicate Offences 3.2 Licensing, Registration, Charters, and Regulatory Sandboxes 3.3 Virtual Asset Service Provider (VASP) Framework & FinCEN MSB Rules

4 Chapter 4: Domain 1: Global AML Frameworks and Sources of Guidance

4.1 U.S. Regulatory Architecture: BSA, PATRIOT Act, and AMLA 2020 4.2 European Union Regulatory Framework: AMLD6, the AML Package, and MiCA 4.3 International Standards: UK FCA, Singapore MAS, and Hong Kong HKMA 4.4 Sources of Guidance for Building Anti-Financial Crime Processes

5 Chapter 5: Domain 1: Risk Management Framework, Risk-Based Approach, and Data Protection

5.1 Risk Management Framework: Lines of Defence, Policies, Assurance, and the MLRO 5.2 Risk-Based Approach, Risk Assessment, Risk Appetite, and Types of Risk 5.3 Handling Sensitive Information: PII, SPII, Privacy Laws, and Breach Reporting

6 Chapter 6: Domain 1: Bank Partners and Internal Threats

6.1 Regulatory Expectations and Enforcement on Sponsor Banks 6.2 How Banks Risk-Rate FinTechs: Onboarding, Ongoing Oversight, and De-Risking 6.3 Controlling Internal Threats: Insider Fraud, Collusion, and Data Misuse

7 Chapter 7: Domain 2: CIP, KYC, CDD, and EDD

7.1 Customer Identification Program (CIP) Under USA PATRIOT Act §326 7.2 The FinCEN CDD Rule & Beneficial Ownership Standards 7.3 KYC to EDD: Applying CDD and Enhanced Due Diligence Across Customer Types

8 Chapter 8: Domain 2: Identity Verification, Data Sources, and Device Data

8.1 Digital Onboarding & Electronic KYC (eKYC) Foundations 8.2 Biometric Face Matching and Liveness Detection 8.3 Verification Data Sources and How to Judge Their Reliability 8.4 Device Fingerprinting, Geolocation, and Behavioral Biometrics

9 Chapter 9: Domain 2: Onboarding Screening, Risk Ratings, and Fraud Red Flags

9.1 Screening at Onboarding: Sanctions Lists, PEPs, and Known Fraudsters 9.2 Customer Risk Ratings: Factors, Data Sources, and How Scoring Models Work 9.3 Detecting Synthetic Identity Fraud and Ineligible Applicants 9.4 Deepfakes, Generative AI Threats, and Scam Typologies

10 Chapter 10: Domain 3: Payment Screening

10.1 OFAC Sanctions Regimes & the 50 Percent Rule 10.2 Real-Time vs. Batch Screening Architecture in High-Velocity Rails 10.3 Screening Logic: Fuzzy Matching, Phonetics, and PEP Controls

11 Chapter 11: Domain 3: Transaction Monitoring Systems and Red Flags

11.1 Hybrid Transaction Monitoring: Rules Engines vs. Machine Learning 11.2 FinTech Typologies: Mule Networks, Funnel Accounts, and Rapid Pass-Through 11.3 Fraud-AML Convergence: BIN Attacks, ATO, and Credential Stuffing 11.4 Model Risk Management Under SR 11-7 & System Optimization

12 Chapter 12: Domain 3: Payment Methods and Transaction Risk Characteristics

12.1 Common Payment Methods, Crypto, and High-Risk Transactions Such as Aggregation 12.2 Transaction Risk Characteristics: Reversibility, Convertibility, Fund Integrity, and Privacy Coins 12.3 Wallet Types, Custody Architectures, and Counterparty Risks 12.4 Stablecoins, On/Off Ramps, and Asset-Referenced Tokens

13 Chapter 13: Domain 3: Monitoring Crypto Transactions

13.1 Blockchain Analytics & Transaction Tracing 13.2 The FATF Travel Rule for Virtual Assets 13.3 DeFi, Mixers, and Smart Contract Sanctions

14 Chapter 14: Domain 3: Alert Investigation, Audit Trails, and Monitoring MI

14.1 The Alert Investigation Process: From Unusual to Suspicious and When to Escalate 14.2 Building an Audit Trail for Suspicious Activity Reviews 14.3 Communicating Monitoring Results: KPIs, KRIs, OKRs, and Management Information

15 Chapter 15: Domain 4: Investigations and Customer Communication

15.1 Talking to Customers During Investigations and Offboarding: Financial Crime Risk vs Policy Breach 15.2 Reviewing KYC, Transactions, Open Sources, and Documents to Build an Investigation 15.3 Analytical Principles in Investigations: Avoiding Confirmation Bias and Other Traps

16 Chapter 16: Domain 4: SARs and STRs

16.1 SARs and STRs: What They Are, When and Where to File, and Why They Matter 16.2 Writing Effective SAR and STR Narratives

17 Chapter 17: Domain 4: Law Enforcement, Regulators, and Banking Partners

17.1 Operational AML Governance and Third-Party Risk Management 17.2 Working With Law Enforcement, Banking Partners, Regulators, and Other Third Parties 17.3 Types of Law Enforcement Requests: Subpoenas, Court Orders, 314(a), and International Requests 17.4 How Banking Partners' Terms of Service Relate to the FinTech's Own Terms

18 Chapter 18: Domain 5: Scaling Anti-Financial Crime Strategies

18.1 Assessing New Products and Features Before Launch 18.2 Refreshing the Financial Crime Risk Assessment as the Business Scales 18.3 Changes That Should Trigger a Financial Crime Risk Assessment Review 18.4 Record Retention Rules and Secure Data Storage 18.5 Outsourcing Controls: Surge Capacity, RegTech, and Independent Testing

5.3 Handling Sensitive Information: PII, SPII, Privacy Laws, and Breach Reporting

Key Takeaways Explain This Topic AI

NIST defines PII as information that can be used to distinguish or trace an individual's identity, alone or combined with other information.

Under GDPR, a personal data breach must be reported to the supervisory authority within 72 hours of the firm becoming aware of it, unless it is unlikely to create risk to individuals.

US banking organisations must notify their primary federal regulator within 36 hours of determining that a notification incident has occurred.

Biometric data used to uniquely identify a person is special category data under GDPR Article 9, so selfie-based eKYC needs strict protection.

Last updated: October 2026

CAFCA sub-topic 1.5 covers best practice in handling sensitive and private information . That includes definitions of PII and SPII , privacy laws such as GDPR and CCPA , reporting of cybersecurity breaches and incidents, and the consequences of mishandling data. For a FinTech this is daily work. Onboarding collects passports and selfies, monitoring processes device and location data, and investigators assemble case files full of sensitive facts.

PII and SPII

Personally identifiable information (PII) : NIST SP 800-122 defines it as information that can be used to distinguish or trace an individual's identity, alone or combined with other information. Examples include name, address, date of birth, email, phone number, IP address and device identifiers.

Sensitive PII (SPII) : a subset that would cause substantial harm, embarrassment or unfairness if lost or disclosed. US government handling rules give examples such as Social Security numbers, passport and driver's licence numbers, financial account numbers and biometrics. Combinations, such as name plus date of birth plus account number, can also be sensitive.

In AML work, identity documents, biometric templates, SSNs and national IDs, account numbers, and SAR-related information should all be handled as the most sensitive tier.

Key privacy laws

Law Scope Points most relevant to AFC teams

EU GDPR (and the UK GDPR with the Data Protection Act 2018) Personal data of people in the EU (UK) processed by firms established there or targeting them Lawful basis is needed. AML processing usually relies on "legal obligation" (Art. 6(1)(c)). Principles of purpose limitation, data minimisation, accuracy, storage limitation and security apply. Biometric data for unique identification is special category data (Art. 9). Data protection impact assessments are required for high-risk processing. Breach notice goes to the supervisory authority within 72 hours (Art. 33), and to individuals without undue delay if the risk is high (Art. 34). Fines reach €20 million or 4% of worldwide annual turnover, whichever is higher

California CCPA (as amended by the CPRA) Personal information of California residents Rights to know, delete, correct and opt out of sale or sharing, plus limits on use of sensitive personal information. Data covered by the federal GLBA financial privacy law is largely exempt from the main CCPA duties, but the law's private right of action for certain data breaches still applies

US financial privacy and security rules Banks and non-bank financial institutions GLBA privacy and safeguards rules. Under the FTC Safeguards Rule, covered non-bank firms must notify the FTC within 30 days of discovering a breach affecting 500 or more consumers. Banks follow the interagency computer-security incident rule (36 hours to notify the primary regulator) and state breach-notification laws

Privacy and AML working together

Privacy law and AML law are designed to coexist:

Legal obligation basis. CDD, monitoring and reporting are lawful because AML law requires them. Collecting more than you need, such as copying unnecessary documents or keeping device data forever, is not covered.

Retention limits. AML laws set minimum retention, typically five years. Some, such as the UK Money Laundering Regulations, also require deleting personal data after the retention period unless another law or consent applies (Chapter 18).

Subject access requests. A customer under investigation may request their data. The law lets firms withhold information where disclosure would prejudice crime prevention or amount to tipping off. In the UK this is the crime-and-taxation exemption in the Data Protection Act 2018. The decision must be documented and approved by the right people.

Travel Rule and information sharing. Share only the fields the rule requires, over secure channels, and only with counterparties whose data protection you have assessed.

Best practices

Data minimisation : collect only what the control needs and mask identifiers in case tools.

Access control : role-based, least-privilege access with logging. Case files and SAR folders get the strictest permissions.

Encryption in transit and at rest, plus secure key management.

Vendor management : data processing agreements, location and transfer safeguards (such as standard contractual clauses), security reviews, and sub-processor lists.

Secure handling habits : no personal email or unapproved cloud storage; clean-desk and screen-sharing rules; redact data before sending it internally.

Incident readiness : an incident response plan that maps each type of incident to its notification clocks (privacy regulator, prudential regulator, partner bank, affected customers) and to any SAR obligation for cyber-enabled crime.

Consequences of mishandling data

Regulatory fines and orders from data protection authorities and financial regulators.

Notification and remediation costs, litigation and class actions.

Harm to customers through identity theft and fraud using leaked data.

Loss of partner-bank or payment-network relationships.

Criminal exposure if SAR information is disclosed. Tipping off is a crime in the US, UK and many other jurisdictions.

Realistic exam scenario

An investigator emails a spreadsheet of 400 customers' names, dates of birth, SSNs and alert notes to a personal account to "finish over the weekend". The firm discovers it on Monday. The firm must treat this as a security incident and contain it by requesting deletion and preserving evidence. It must assess the notification obligations under each applicable law and regulator rule, and notify the partner bank as the contract requires. It should also consider whether SAR-related information was exposed, and take disciplinary and training action. "No harm done" is not a decision the investigator can make alone.

Common exam traps

"AML overrides privacy, so any data can be kept forever." Wrong. Retention and minimisation still apply.

Answering a subject access request by disclosing investigation notes. This risks tipping off.

Treating IP addresses and device IDs as non-personal. Under GDPR they can be personal data.

Missing the 72-hour or 36-hour clocks because the incident was not escalated.