Privacy Law Updates
Produces a structured briefing on recent privacy and data protection developments, oriented toward compliance planning and executive decision-making.
Quick Start
Confirm before generating:
- Reporting period — default: past 12–18 months
- Jurisdictions — default: US federal + state, EU/EEA, UK
- Industry context — platform type, data categories, cross-border transfers
- Audience — legal/compliance, executive, or both
Output Workflow
Step 1: Executive Overview
| Element |
Content |
| Critical deadlines |
Compliance dates requiring immediate action |
| Major enforcement |
Fines/orders signaling regulatory priorities |
| New obligations |
Requirements not previously in effect |
| Strategic flags |
Developments affecting product roadmap or vendors |
Step 2: Jurisdiction Developments
For each jurisdiction, use this entry template:
### [Jurisdiction]
#### [Development Title]
- **Type**: Legislation | Guidance | Enforcement | Court Decision
- **Effective date**: [date or timeline]
- **Scope**: [entities, data types, activities covered]
- **Key requirements/holdings**: [bullet list]
- **Delta from prior law**: [what changed]
- **Operational impact**: [systems, processes, documentation affected]
- **Penalties**: [non-compliance consequences]
- **Exemptions/safe harbors**: [if any]
Step 3: Cross-Cutting Topics
Cover only topics with material developments:
| Topic |
Capture |
| Cross-border transfers |
New mechanisms, adequacy decisions, SCCs updates |
| Consent & notice |
Changed standards, dark-pattern enforcement |
| Data subject rights |
Access, deletion, portability changes |
| Breach notification |
Amended timelines, reporting thresholds |
| AI governance |
Automated decision-making rules, transparency mandates |
| Children's privacy |
Age verification, parental consent, design codes |
| Biometric data |
New state/national laws, consent requirements |
Step 4: Forward-Looking
- Pending legislation with expected timelines
- Open regulatory consultations
- Announced DPA enforcement priorities
- Areas of legal uncertainty warranting monitoring
Checks and Pitfalls
- Jurisdiction-first organization — cross-reference in cross-cutting section; never repeat the same development twice
- Cite primary sources — statute sections, regulation articles, case names, DPA decisions
- Mark unverified citations with
[VERIFY]
- Distinguish enacted law from proposals — clearly label pending/proposed items
- Flag jurisdictional conflicts where requirements create operational tension
- Include enforcement amounts — fines contextualize regulatory seriousness
- No editorializing on political likelihood; state procedural status only
- Note sector carve-outs (HIPAA, GLBA, COPPA, ePrivacy) where they interact with general frameworks
- Dual-audience tone — precise for compliance implementation, clear for executive briefing
1---2name: privacy-law-updates3description: Generates structured privacy and data protection law briefings across US, EU, UK, and other jurisdictions. Organizes by jurisdiction with compliance deadlines, enforcement actions, and legislative changes. Use when preparing privacy law briefings, compliance updates, regulatory change summaries, or data protection landscape reviews.4license: Apache-2.05---67# Privacy Law Updates89Produces a structured briefing on recent privacy and data protection developments, oriented toward compliance planning and executive decision-making.1011## Quick Start1213Confirm before generating:14151. **Reporting period** — default: past 12–18 months162. **Jurisdictions** — default: US federal + state, EU/EEA, UK173. **Industry context** — platform type, data categories, cross-border transfers184. **Audience** — legal/compliance, executive, or both1920## Output Workflow2122### Step 1: Executive Overview2324| Element | Content |25|---|---|26| Critical deadlines | Compliance dates requiring immediate action |27| Major enforcement | Fines/orders signaling regulatory priorities |28| New obligations | Requirements not previously in effect |29| Strategic flags | Developments affecting product roadmap or vendors |3031### Step 2: Jurisdiction Developments3233For each jurisdiction, use this entry template:3435```36### [Jurisdiction]3738#### [Development Title]39- **Type**: Legislation | Guidance | Enforcement | Court Decision40- **Effective date**: [date or timeline]41- **Scope**: [entities, data types, activities covered]42- **Key requirements/holdings**: [bullet list]43- **Delta from prior law**: [what changed]44- **Operational impact**: [systems, processes, documentation affected]45- **Penalties**: [non-compliance consequences]46- **Exemptions/safe harbors**: [if any]47```4849### Step 3: Cross-Cutting Topics5051Cover only topics with material developments:5253| Topic | Capture |54|---|---|55| Cross-border transfers | New mechanisms, adequacy decisions, SCCs updates |56| Consent & notice | Changed standards, dark-pattern enforcement |57| Data subject rights | Access, deletion, portability changes |58| Breach notification | Amended timelines, reporting thresholds |59| AI governance | Automated decision-making rules, transparency mandates |60| Children's privacy | Age verification, parental consent, design codes |61| Biometric data | New state/national laws, consent requirements |6263### Step 4: Forward-Looking6465- Pending legislation with expected timelines66- Open regulatory consultations67- Announced DPA enforcement priorities68- Areas of legal uncertainty warranting monitoring6970## Checks and Pitfalls7172- **Jurisdiction-first organization** — cross-reference in cross-cutting section; never repeat the same development twice73- **Cite primary sources** — statute sections, regulation articles, case names, DPA decisions74- **Mark unverified citations** with `[VERIFY]`75- **Distinguish enacted law from proposals** — clearly label pending/proposed items76- **Flag jurisdictional conflicts** where requirements create operational tension77- **Include enforcement amounts** — fines contextualize regulatory seriousness78- **No editorializing** on political likelihood; state procedural status only79- **Note sector carve-outs** (HIPAA, GLBA, COPPA, ePrivacy) where they interact with general frameworks80- **Dual-audience tone** — precise for compliance implementation, clear for executive briefing
ThomasMoreAI