A classroom pack for Fair Information Practice Principles (FIPPs), the Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule, General Data Protection Regulation (GDPR) principles, and the Saudi Personal Data Protection Law (PDPL). Built for short group work, quick checks, and discussion.
Lecture Map
Use this first. It shows the main legal ideas in the same order as the lecture: basic principles, health privacy, EU privacy law, Saudi law, and design choices.
Group timer
Use for the 8-minute breakout activity from the slides.
08:00
Timer ready: 8 minutes.
Class question:
Which ideas repeat across the two eight-principle frameworks, HIPAA, GDPR, and Saudi privacy law—and where does scope change the answer?
Principles
Search or filter the principles. Ask students to give one system design action for each principle.
Compare Laws
This view helps students see common ideas, not just memorize separate laws.
Law or framework
Who or what it covers
Main privacy idea
Classroom example
Roles, Electronic Communications, and Transfers
Keep scope, role, and transfer mechanism separate. These distinctions correct three common mistakes in system requirements.
European Union ePrivacy Directive
Directive 2002/58/EC, as amended by Directive 2009/136/EC, focuses on privacy in electronic communications, including confidentiality of communications and rules affecting cookies or access to terminal equipment. It is not the rule that authorizes every international transfer.
General Data Protection Regulation
Regulation (EU) 2016/679 governs processing of personal data more broadly. It addresses legal bases, principles, rights, controllers and processors, security, breach duties, impact assessments, and international transfers.
U.S. privacy is sectoral and increasingly state-based
The United States has federal laws for sectors or data types—such as HIPAA for covered health information, the Gramm-Leach-Bliley Act for financial institutions, the Fair Credit Reporting Act for consumer reports, the Children's Online Privacy Protection Act for certain online services directed to children, and the Family Educational Rights and Privacy Act for education records—alongside a growing set of comprehensive state privacy laws.
European Union–United States transfer sequence
2015
Safe Harbor
The Court of Justice of the European Union invalidated the earlier adequacy arrangement in Schrems I.
Invalidated
2020
Privacy Shield
The Court invalidated the replacement in Schrems II. Organizations using other tools still had to assess surveillance risk and supplementary safeguards.
Invalidated
2023
EU–U.S. Data Privacy Framework
The European Commission adopted a new adequacy decision. Eligible U.S. organizations may self-certify. This decision has been litigated since adoption, so teams must confirm both the recipient's participation and the decision's current legal status before relying on it.
Current framework
Role map
Framework
Primary decision maker
Service role
Person
GDPR
Controller decides purposes and means
Processor acts on documented instructions
Data subject
HIPAA Privacy Rule
Covered entity is directly regulated
Business associate performs covered functions involving protected health information
Individual or patient
Saudi Personal Data Protection Law
Controller determines purpose and manner of processing
Processor processes data for the controller
Data subject
From Legal Rule to System Design
A privacy requirement should affect the full information life cycle and leave evidence that the design works.
Capture
Define purpose and legal basis, minimize fields, provide notice, and obtain valid consent where consent is the basis.
Store
Inventory data, restrict access, encrypt appropriately, define retention, and govern processor contracts.
Use and share
Enforce purpose and use limits, record disclosures, handle subject requests, and review international transfers.
Destroy
Delete or anonymize on schedule, propagate deletion to copies where required, and retain evidence of disposal.
Engineering readiness checklist
Maintain a data inventory and name owners.
Run a Privacy Impact Assessment (PIA) or Data Protection Impact Assessment (DPIA) when risk warrants it.
Use privacy by design and privacy-protective defaults.
Build access, correction, objection, erasure, and portability workflows where applicable.
Detect, assess, document, and notify breaches under the applicable rule.
Test retention, deletion, processor, and transfer controls rather than relying on policy text.
Generative artificial intelligence and large language models
Training data
Web scraping may collect personal data without a clear legal basis or adequate transparency. Inventory sources, remove unnecessary personal data, and document the basis and limitations.
Erasure and memorization
Deleting a source row does not necessarily remove memorized content from model weights. Prevention, privacy testing, and machine-unlearning research do not yet provide a universal deletion mechanism.
Prompts and logs
Source code, health records, or customer data pasted into a model may create new processing and retention. Use approved services, minimize input, scrub identifiers, and configure retention.
Accuracy and correction
False statements about a real person create accuracy and redress problems. Ground outputs in reliable sources, expose uncertainty, keep citations, and provide a correction path.
Scenario Lab
Pick a case. Students decide which data is involved, which rule matters, and what should be changed.
Group notes
Quick Quiz
Fourteen fast questions for the last 15 minutes of class. The feedback explains the answer in simple terms.
0/0
Useful class prompt
A privacy rule is not only a legal sentence. It should become a design choice: collect less, explain clearly, limit use, protect data, allow access, and keep proof.
Sources used
Legal content last reviewed: August 2026. Adequacy decisions, state privacy statutes, and implementing regulations change. Verify each source before reusing this material in a later term.