Study guide
6.4 FADP and Other Non-U.S. Intersections
IAPP Certified Information Privacy Professional/United States CIPP/US
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 BoK 2.6.1, Scoring, Activation, CPE, and 2026 Updates
2 Domain I: The U.S. Legal Framework
2.1 Branches of Government and Their Privacy Roles 2.2 Sources of U.S. Privacy Law 2.3 Scope, Jurisdiction, Preemption, and Private Rights of Action 2.4 Major Regulatory Authorities
3 Domain I: Self-Regulation, Liability, and Enforcement
3.1 Self-Regulatory Models 3.2 Contract, Tort, Fiduciary Duty, Negligence, and UDAP 3.3 Federal and State Enforcement Authorities 3.4 Cross-Border Enforcement, GPEN, PCI, and Trust Marks
4 Domain I: Information Management Foundations
4.1 Data Inventory, Classification, and Records of Processing 4.2 Data-Flow Mapping, Sharing, and Transfers 4.3 Privacy Program Development and Workforce Training 4.4 Vendors, Cloud, DPAs, and Third-Party Sharing
5 Domain I: Accountability, Notices, and Online Privacy
5.1 Accountability, Incident Response, and Due Diligence 5.2 User Preferences, Retention, Disposal, and Privacy Notices 5.3 Online Tracking, Profiling, and Digital Advertising Basics
6 Domain I: International Transfers and Multinational Compliance
6.1 Schrems Decisions and Transfer Requirements 6.2 SCCs and the EU-U.S. Data Privacy Framework 6.3 GDPR Requirements and Multinational Conflicts 6.4 FADP and Other Non-U.S. Intersections
7 Domain II: FTC Consumer Privacy
7.1 FTC Act and COPPA 7.2 FTC Privacy and Security Enforcement 7.3 Future Enforcement Priorities: Brokers, IoT, AI, Biometrics
8 Domain II: Healthcare and Medical Privacy
8.1 HIPAA Privacy and Security Rules 8.2 HITECH and Breach Notification 8.3 Part 2 and the 21st Century Cures Act
9 Domain II: Financial Sector Privacy
9.1 FCRA and FACTA 9.2 GLBA Privacy Rule, Safeguards Rule, and State Exemptions 9.3 Red Flags Rule, Dodd-Frank, and the CFPB 9.4 Online Banking Privacy and M&A Diligence
10 Domain II: Education, Telecom, and Marketing
10.1 FERPA and Education-Technology Risk 10.2 TCPA, TSR, CAN-SPAM, JFPA, Cable Act, VPPA, DPPA 10.3 Do-Not-Call and the Wireless Domain Registry 10.4 Digital Advertising, Web Scraping, and Data Ethics
11 Domain III: Government and Court Access
11.1 RFPA, BSA, ECPA, and CALEA 11.2 FISA 702, PATRIOT, USA Freedom, and CISA 11.3 Privacy Protection Act and E-Discovery
12 Domain IV: Workplace Privacy Foundations
12.1 Notice, AEP, CRA, ADA, and GINA 12.2 FTC, DOL, EEOC, NLRB, and OSHA 12.3 AEDTs, Background Checks, Testing, and Social Media
13 Domain IV: Monitoring, Investigations, and Post-Employment
13.1 Employee Monitoring and Employer ECPA Duties 13.2 Internal Investigations and Post-Employment Records
14 Domain V: Authority and Common State Framework
14.1 Federal/State Authority, AGs, and the CPPA 14.2 Applicability Thresholds, Exemptions, and Consumer Rights 14.3 State Privacy Notices 14.4 Assessments, Retention, Sale/Sharing, and DPAs
15 Domain V: Sectoral Rules and Enforcement
15.1 Common State Data-Security Requirements 15.2 MHMD, Nevada CHD, GIPA, and Geofencing Bans 15.3 Cure Periods and Penalties 15.4 State Cookie and Online-Tracking Rules
16 Domain V: Biometrics, AI Bias, and California
16.1 Illinois, Washington, Texas, and Facial-Recognition Limits 16.2 NAIC AIS, NYC AEDT, CA/CO ADMT, Colorado Insurance 16.3 CCPA/CPRA, CAADCA, and the Delete Act
17 Domain V: Other State Laws and Breach Notification
17.1 Other Major Comprehensive State Privacy Laws 17.2 Common Breach-Notification Elements 17.3 State Differences, PA SB 696, and Utah S.B. 127
6.4 FADP and Other Non-U.S. Intersections
Key Takeaways Explain This Topic AI
The revised Swiss Federal Act on Data Protection (revFADP / nFADP), in force 1 September 2023, applies to circumstances that have an effect in Switzerland even if they were initiated abroad
Swiss sensitive personal data is a defined list that includes health, intimacy, racial or ethnic origin, genetic and identifying biometric data, and certain proceedings, sanctions, and social-assistance data
A controller must notify the FDPIC as soon as possible of a data-security breach likely to cause a high risk to personality or fundamental rights — not a blanket 72-hour clock and not every low-risk incident
The Swiss-U.S. DPF, usable for certified importers from 15 September 2024, is an adequacy-style path under Swiss transfer rules; uncertified U.S. importers still need Swiss-adapted SCCs or another FADP safeguard
Canada's PIPEDA, Quebec's Law 25, and the UK GDPR are other non-U.S. laws a U.S. multinational will hit; CIPP/US requires that recognition, not CIPP/C or CIPP/E depth
Last updated: August 2026
FADP and Other Non-U.S. Intersections
CIPP/US is a United States credential. BoK 2.6.1 still requires the U.S. professional to recognize how U.S. programs intersect non-U.S. privacy law. The outline names two statutes expressly: the GDPR (previous sections) and Switzerland's Federal Act on Data Protection (FADP) . Canada and the United Kingdom appear here only as other laws a U.S. multinational walks into — not as a second certification.
The revised FADP in force
Parliament adopted the revised FADP on 25 September 2020 . The revised Act and its ordinances entered into force on 1 September 2023 with no multi-year private-sector grace period. English-language practice calls it revFADP or nFADP (new FADP). The official purpose is protection of the personality and fundamental rights of natural persons whose personal data are processed. Legal-person data, which the old Act covered, dropped out — a GDPR-like shift candidates should not reverse.
Article 3 is the extra-territorial hook. The Act applies to circumstances that have an effect in Switzerland, even if they were initiated abroad . That effects doctrine is broader wording than GDPR Article 3(2)'s offering/monitoring pair. A U.S. controller with no Swiss office can still be in scope if its processing produces effects in Switzerland — for example, offering services to persons in Switzerland, monitoring them, or running processing that lands on Swiss persons or Swiss infrastructure. Do not tell an examiner the FADP stops at the cantonal border or applies only to Swiss federal agencies.
Sensitive personal data is a defined Swiss list (Article 5), not a carbon copy of GDPR Article 9. It includes data on religious, philosophical, political, or trade-union views or activities; data on health , the intimate sphere , or racial or ethnic origin ; genetic data; biometric data that uniquely identifies a natural person; data on administrative or criminal proceedings or sanctions ; and data on social-assistance measures. Processing sensitive data raises the FADP's high-risk and consent/justification temperature the same way special-category processing does under the GDPR, but you must use the Swiss list on a Swiss fact pattern (social-assistance and proceedings data are easy misses).
Other operational duties a U.S. examiner can fairly expect at this depth: records of processing in defined situations, a data protection impact assessment when processing may lead to a high risk to personality or fundamental rights, privacy by design and by default, and — where Article 14's conditions are met — a representative in Switzerland for a controller with no Swiss establishment that processes personal data of persons in Switzerland in connection with offering goods or services or monitoring, when that processing is extensive, regular, or high-risk. The Swiss representative is analogous to GDPR Article 27, not identical to it, and DPF certification does not delete it by itself.
High-risk breach notice to the FDPIC
Article 24 is the breach rule the BoK expects you to contrast with U.S. state notice and with GDPR Article 33.
The controller notifies the Federal Data Protection and Information Commissioner (FDPIC) of a breach of data security that is likely to lead to a high risk to the data subject's personality or fundamental rights, as quickly as possible ("as soon as possible" / "as quickly as possible" in official English).
The notice states at least the nature of the breach, its consequences , and the measures taken or planned.
The processor notifies the controller as quickly as possible — not the FDPIC in the first instance.
The controller informs the data subject if that is required for the subject's protection or if the FDPIC so requests .
Two contrasts matter. First, the Swiss threshold is high risk , not the GDPR's "risk" to the supervisory authority. Low-risk incidents stay out of the FDPIC inbox. Second, Swiss law uses as soon as possible , not a fixed 72-hour clock. Do not import Article 33's 72 hours onto a pure FADP question. Do not send the Swiss notice to the FTC, and do not assume an FDPIC filing satisfies GDPR Article 33 for EU data subjects in the same incident — a multinational logs each statute's authority, threshold, and clock.
How the FADP intersects the Swiss-U.S. DPF
Swiss transfer rules (FADP Article 16 and related provisions) allow disclosure abroad if the Federal Council has found adequate protection or if safeguards exist (including adapted SCCs and binding corporate rules). Switzerland's recognition of the Swiss-U.S. Data Privacy Framework entered into force on 15 September 2024 . From that date, a U.S. organization that has self-certified to the Swiss-U.S. DPF on the Commerce list may receive Swiss personal data in reliance on that recognition, consistent with Swiss law.
Intersection rules for the exam:
Swiss-U.S. DPF is a separate Commerce box from EU-U.S. DPF and the UK Extension. EU-only certification does not move Swiss HR files.
DPF does not repeal the FADP. The Swiss controller (or the U.S. company, if it is itself the FADP controller) still owes Swiss lawful-processing, sensitive-data, DPIA, and Article 24 duties.
An uncertified U.S. importer needs another FADP safeguard — typically Swiss-adapted 2021 SCCs — plus an assessment of U.S. law analogous to a TIA.
Trump v. Slaughter review of the EU-U.S. adequacy file is not, as of August 2026, a published Swiss withdrawal of the Swiss-U.S. DPF. Do not invent one. Dual-track the Swiss flows the same way you dual-track EU flows: DPF if certified, adapted SCCs as fallback.
Scenario. A Zurich hospital sends patient billing data to an uncertified U.S. revenue-cycle vendor. The FADP applies (health data, effect in Switzerland). The vendor is not on the Swiss-U.S. DPF list, so Article 16 adequacy is unavailable. The hospital needs Swiss-adapted SCCs (or another safeguard) and a transfer assessment. If attackers later exfiltrate the U.S. file and the incident is likely a high risk to patients' personality rights, the hospital notifies the FDPIC as soon as possible and informs patients if needed for their protection; the U.S. vendor notifies the hospital immediately. A parallel GDPR clock may also run if some patients are in the EEA — that is a second notice, not a substitute.
Other non-U.S. laws a U.S. multinational actually hits
Stay at intersection depth. These are not CIPP/C or CIPP/E outlines.
Canada — PIPEDA. The Personal Information Protection and Electronic Documents Act is the federal private-sector statute for commercial activity (and for federal works, undertakings, and businesses). It is a consent-and-fair-information-principles statute overseen by the Office of the Privacy Commissioner of Canada (OPC) . Breach notification is triggered by a real risk of significant harm (RROSH) to the OPC and to individuals. Some provinces have substantially similar private-sector laws; PIPEDA still matters to a U.S. retailer that takes Canadian orders.
Quebec — Law 25. Law 25 (2021, chapter 25) modernized Quebec's private-sector privacy act. Core private-sector duties — a designated person in charge of personal information, privacy impact assessments for certain projects, default privacy settings, tighter consent, and breach notice to the Commission d'accès à l'information (CAI) and to individuals when there is a risk of serious injury — are in force (most provisions 22 September 2023 ). Law 25 is the Canadian statute most likely to surprise a U.S. company that thought "PIPEDA covers Canada." It is still not a CIPP/C exam inside CIPP/US.
United Kingdom — UK GDPR. After Brexit, the UK GDPR and the Data Protection Act 2018 are the UK regime, supervised by the ICO . Article 3-style extra-territorial reach, lawful bases, DPIA/DPO/representative analogues, and a restricted-transfer rule all still exist. Transfer tools are the IDTA , the UK Addendum to the EU SCCs, the UK Extension to the EU-U.S. DPF (from 12 October 2023) for certified U.S. importers, and UK derogations. The EU has its own adequacy decision for the United Kingdom; that decision helps EU-to-UK flows. It does not make a U.S. company "adequate."
- Regime Why a U.S. company hits it Transfer / notice hook to remember
- Swiss FADP Effects in Switzerland; BoK-named Swiss-U.S. DPF or adapted SCCs; FDPIC high-risk notice ASAP
- PIPEDA Canadian commercial activity OPC + individuals if RROSH
- Quebec Law 25 Persons in Quebec; not "just PIPEDA" CAI + individuals if risk of serious injury
- UK GDPR UK establishment or UK targeting IDTA / Addendum / UK Extension to DPF
- Exam traps
Do not date the revised FADP to 2020 (adoption) instead of 1 September 2023 (in force).
Do not paste GDPR's 72-hour, any-risk supervisory notice onto Article 24.
Do not treat EU-U.S. DPF certification as Swiss-U.S. DPF certification.
Do not turn this section into a CIPP/C walkthrough of every PIPEDA principle or a CIPP/E walkthrough of every UK GDPR recital.