Data Privacy & Compliance
Overview
Structured privacy compliance workflows for AI agents handling personal data. Covers GDPR (EU), CCPA/CPRA (California), HIPAA (US Healthcare), and general privacy engineering practices. Each workflow maps to specific regulatory requirements with verification gates.
Important: This skill provides educational reference workflows, not legal advice. Consult qualified legal counsel for compliance decisions in production.
When to Use
- Processing data subject access requests (DSARs) across jurisdictions
- Conducting privacy impact assessments (PIAs/DPIAs)
- Evaluating cross-border data transfer mechanisms
- Handling consent management and cookie compliance
- Responding to data breaches with notification obligations
- Implementing privacy by design in new features
- Auditing data processing activities
- Classifying and inventorying personal data
- Establishing data retention schedules
- Reviewing vendor data processing agreements
Core Privacy Principles
Regardless of jurisdiction, these principles apply universally:
| Principle |
Description |
Implementation |
| Lawfulness |
Process data on a valid legal basis |
Identify and document the basis before collection |
| Purpose Limitation |
Only use data for the purpose it was collected |
Document purposes at collection point |
| Data Minimization |
Collect only what's necessary |
Audit collection fields regularly |
| Accuracy |
Keep data accurate and up to date |
Implement verification workflows |
| Storage Limitation |
Delete when no longer needed |
Enforce retention schedules |
| Integrity & Confidentiality |
Secure data appropriately |
Apply encryption, access controls |
| Accountability |
Demonstrate compliance |
Maintain records of processing |
GDPR Compliance Workflow
Determine Applicability
Check if GDPR applies:
- Does the organization have an establishment in the EU/EEA?
- Does the organization offer goods/services to data subjects in the EU/EEA?
- Does the organization monitor behavior of data subjects in the EU/EEA?
- Does the processing involve personal data of EU/EEA residents?
If YES to any → GDPR applies. Proceed with compliance assessment.
Data Mapping & ROPA
Create or update the Record of Processing Activities (Article 30):
| Field |
Description |
| Processing purpose |
Why is the data being processed? |
| Data categories |
What types of personal data? |
| Data subjects |
Whose data? (customers, employees, etc.) |
| Legal basis |
Art. 6 basis (consent, contract, legal obligation, etc.) |
| Recipients |
Who receives the data? |
| Transfers |
Cross-border transfer mechanisms |
| Retention period |
How long is data kept? |
| Technical safeguards |
Encryption, access controls, etc. |
Data Subject Rights Handling
When receiving a DSAR, follow this workflow:
- Verify identity — Confirm the requestor is who they claim to be (without excessive data collection)
- Acknowledge receipt — Within the regulatory timeline (GDPR: without undue delay, max 1 month)
- Scope the request — Identify what personal data is held, where, and in what systems
- Retrieve data — Search across all systems (production, backups, logs, analytics)
- Redact third-party data — Remove or anonymize data of other individuals
- Format response — Machine-readable format if requested; common formats include JSON, CSV, PDF
- Deliver securely — Encrypted delivery, identity-verified channel
- Document — Log the request, steps taken, and outcome for accountability
Breach Notification
Timeline varies by jurisdiction:
| Jurisdiction |
Notification Timeline |
Regulator |
Individuals |
| GDPR (EU) |
72 hours |
Lead Supervisory Authority |
Without undue delay |
| CCPA (California) |
No specific timeline |
Attorney General |
Promptly |
| HIPAA (US Healthcare) |
60 days |
HHS |
Within 60 days |
| LGPD (Brazil) |
72 hours |
ANPD |
Simultaneously |
| PIPEDA (Canada) |
As soon as possible |
OPC/OIPC |
As soon as possible |
Breach response workflow:
- Contain — Stop the breach from spreading (revoke credentials, isolate systems)
- Assess — Determine scope: what data, how many records, who is affected
- Notify — Inform regulator within required timeline
- Communicate — Inform affected data subjects with clear remediation steps
- Document — Record all actions taken, timelines, and decisions
- Remediate — Fix the root cause, update security measures
- Review — Post-incident review to prevent recurrence
CCPA/CPRA Compliance
Key Rights Under CCPA/CPRA
| Right |
Description |
Timeline |
| Right to Know |
What personal data is collected, used, shared |
10 business days |
| Right to Delete |
Request deletion of personal data |
45 calendar days |
| Right to Opt-Out |
Opt out of sale/sharing of personal data |
15 business days |
| Right to Correct |
Correct inaccurate personal data |
Reasonable timeframe |
| Right to Limit Use |
Limit use of sensitive personal data |
Reasonable timeframe |
| Right to Non-Discrimination |
No price/service discrimination for exercising rights |
Ongoing |
CCPA Assessment Checklist
HIPAA Compliance (US Healthcare)
Key Rules
| Rule |
Focus |
Key Requirements |
| Privacy Rule |
Protected Health Information (PHI) use and disclosure |
Patient rights, minimum necessary standard |
| Security Rule |
Administrative, physical, technical safeguards |
Risk analysis, access controls, audit controls |
| Breach Notification Rule |
Notification following breach |
Timelines vary by scale |
| Enforcement Rule |
Penalties and procedures |
Tiered civil money penalties |
HIPAA Safeguards
Administrative:
- Designate a Security/Privacy Officer
- Conduct risk analysis
- Implement workforce training
- Establish contingency plans
- Regularly review and update policies
Physical:
- Facility access controls
- Workstation and device security
- Media controls (reuse, disposal)
Technical:
- Access controls (unique user IDs, emergency access, automatic logoff)
- Audit controls (track PHI access)
- Integrity controls (ensure PHI not improperly altered)
- Transmission security (encryption)
Privacy by Design
Embed privacy into the development lifecycle:
- Proactive not reactive — Anticipate privacy risks before they materialize
- Privacy as default — Collect minimum data; don't rely on opt-out
- Embedded into design — Privacy is core functionality, not a bolt-on
- Full functionality — Privacy doesn't mean diminished features
- End-to-end security — Protect data throughout its lifecycle
- Visibility and transparency — Data subjects should know what's collected
- Respect for user privacy — User-centric design, give meaningful choices
Implementation checklist for new features:
Common Compliance Pitfalls
| Pitfall |
Risk |
Prevention |
| Assuming one regulation covers everything |
Missing jurisdiction-specific requirements |
Map all applicable regulations per data flow |
| Storing data indefinitely |
Violates storage limitation |
Implement and enforce retention schedules |
| Relying solely on consent |
Consent can be withdrawn; other bases may be more appropriate |
Identify primary legal basis; document alternatives |
| Ignoring cross-border transfers |
Major fines under GDPR Schrems II framework |
Map data flows; implement SCCs or BCRs where needed |
| Treating anonymization as silver bullet |
Re-identification risks remain |
Use formal anonymization standards and verify |
| Not documenting compliance |
Cannot prove accountability without records |
Maintain ROPA, PIAs, and processing logs |
| Forgetting employees' privacy rights |
Employee data is still personal data |
Apply same rigor to internal processing |
| Overlooking data processor obligations |
Liability flows both ways |
Review DPAs; ensure processors have equivalent safeguards |
Red Flags
- Collecting data without a documented legal basis
- Data retention periods described as "indefinite" or "as needed"
- No process for handling DSARs
- Personal data stored in unencrypted form
- Cross-border transfers without documented safeguards
- No incident response plan for data breaches
- Cookie consent that doesn't offer equal accept/reject options
- Dark patterns that nudge users toward sharing more data
- Third-party data sharing without adequate DPAs
- Logging or analytics that capture PII unnecessarily
1---2name: data-privacy-compliance3description: Use this skill when handling PII, personal data, privacy regulations, data subject requests, consent management, data breach response, or any GDPR/CCPA/HIPAA compliance task. Provides structured privacy compliance workflows based on regulatory frameworks.4metadata:5 source: https://skillmd.com/skills/jpeetz/data-privacy-compliance6---78# Data Privacy & Compliance910## Overview1112Structured privacy compliance workflows for AI agents handling personal data. Covers GDPR (EU), CCPA/CPRA (California), HIPAA (US Healthcare), and general privacy engineering practices. Each workflow maps to specific regulatory requirements with verification gates.1314**Important:** This skill provides educational reference workflows, not legal advice. Consult qualified legal counsel for compliance decisions in production.1516## When to Use1718- Processing data subject access requests (DSARs) across jurisdictions19- Conducting privacy impact assessments (PIAs/DPIAs)20- Evaluating cross-border data transfer mechanisms21- Handling consent management and cookie compliance22- Responding to data breaches with notification obligations23- Implementing privacy by design in new features24- Auditing data processing activities25- Classifying and inventorying personal data26- Establishing data retention schedules27- Reviewing vendor data processing agreements2829## Core Privacy Principles3031Regardless of jurisdiction, these principles apply universally:3233| Principle | Description | Implementation |34|-----------|-------------|----------------|35| Lawfulness | Process data on a valid legal basis | Identify and document the basis before collection |36| Purpose Limitation | Only use data for the purpose it was collected | Document purposes at collection point |37| Data Minimization | Collect only what's necessary | Audit collection fields regularly |38| Accuracy | Keep data accurate and up to date | Implement verification workflows |39| Storage Limitation | Delete when no longer needed | Enforce retention schedules |40| Integrity & Confidentiality | Secure data appropriately | Apply encryption, access controls |41| Accountability | Demonstrate compliance | Maintain records of processing |4243## GDPR Compliance Workflow4445### Determine Applicability4647Check if GDPR applies:48491. Does the organization have an establishment in the EU/EEA?502. Does the organization offer goods/services to data subjects in the EU/EEA?513. Does the organization monitor behavior of data subjects in the EU/EEA?524. Does the processing involve personal data of EU/EEA residents?5354If YES to any → GDPR applies. Proceed with compliance assessment.5556### Data Mapping & ROPA5758Create or update the Record of Processing Activities (Article 30):5960| Field | Description |61|-------|-------------|62| Processing purpose | Why is the data being processed? |63| Data categories | What types of personal data? |64| Data subjects | Whose data? (customers, employees, etc.) |65| Legal basis | Art. 6 basis (consent, contract, legal obligation, etc.) |66| Recipients | Who receives the data? |67| Transfers | Cross-border transfer mechanisms |68| Retention period | How long is data kept? |69| Technical safeguards | Encryption, access controls, etc. |7071### Data Subject Rights Handling7273When receiving a DSAR, follow this workflow:74751. **Verify identity** — Confirm the requestor is who they claim to be (without excessive data collection)762. **Acknowledge receipt** — Within the regulatory timeline (GDPR: without undue delay, max 1 month)773. **Scope the request** — Identify what personal data is held, where, and in what systems784. **Retrieve data** — Search across all systems (production, backups, logs, analytics)795. **Redact third-party data** — Remove or anonymize data of other individuals806. **Format response** — Machine-readable format if requested; common formats include JSON, CSV, PDF817. **Deliver securely** — Encrypted delivery, identity-verified channel828. **Document** — Log the request, steps taken, and outcome for accountability8384### Breach Notification8586Timeline varies by jurisdiction:8788| Jurisdiction | Notification Timeline | Regulator | Individuals |89|-------------|---------------------|-----------|-------------|90| GDPR (EU) | 72 hours | Lead Supervisory Authority | Without undue delay |91| CCPA (California) | No specific timeline | Attorney General | Promptly |92| HIPAA (US Healthcare) | 60 days | HHS | Within 60 days |93| LGPD (Brazil) | 72 hours | ANPD | Simultaneously |94| PIPEDA (Canada) | As soon as possible | OPC/OIPC | As soon as possible |9596**Breach response workflow:**97981. **Contain** — Stop the breach from spreading (revoke credentials, isolate systems)992. **Assess** — Determine scope: what data, how many records, who is affected1003. **Notify** — Inform regulator within required timeline1014. **Communicate** — Inform affected data subjects with clear remediation steps1025. **Document** — Record all actions taken, timelines, and decisions1036. **Remediate** — Fix the root cause, update security measures1047. **Review** — Post-incident review to prevent recurrence105106## CCPA/CPRA Compliance107108### Key Rights Under CCPA/CPRA109110| Right | Description | Timeline |111|-------|-------------|----------|112| Right to Know | What personal data is collected, used, shared | 10 business days |113| Right to Delete | Request deletion of personal data | 45 calendar days |114| Right to Opt-Out | Opt out of sale/sharing of personal data | 15 business days |115| Right to Correct | Correct inaccurate personal data | Reasonable timeframe |116| Right to Limit Use | Limit use of sensitive personal data | Reasonable timeframe |117| Right to Non-Discrimination | No price/service discrimination for exercising rights | Ongoing |118119### CCPA Assessment Checklist120121- [ ] Determine if business is subject to CCPA (revenue >$25M, 100K+ records, or 50%+ revenue from data)122- [ ] Update privacy notice with CCPA-required disclosures123- [ ] Implement opt-out mechanism (Do Not Sell/Share link)124- [ ] Establish DSAR handling procedures125- [ ] Audit data sharing with third parties126- [ ] Review and update data processing agreements127- [ ] Train staff on CCPA requirements128- [ ] Document consumer request metrics129130## HIPAA Compliance (US Healthcare)131132### Key Rules133134| Rule | Focus | Key Requirements |135|------|-------|------------------|136| Privacy Rule | Protected Health Information (PHI) use and disclosure | Patient rights, minimum necessary standard |137| Security Rule | Administrative, physical, technical safeguards | Risk analysis, access controls, audit controls |138| Breach Notification Rule | Notification following breach | Timelines vary by scale |139| Enforcement Rule | Penalties and procedures | Tiered civil money penalties |140141### HIPAA Safeguards142143**Administrative:**144- Designate a Security/Privacy Officer145- Conduct risk analysis146- Implement workforce training147- Establish contingency plans148- Regularly review and update policies149150**Physical:**151- Facility access controls152- Workstation and device security153- Media controls (reuse, disposal)154155**Technical:**156- Access controls (unique user IDs, emergency access, automatic logoff)157- Audit controls (track PHI access)158- Integrity controls (ensure PHI not improperly altered)159- Transmission security (encryption)160161## Privacy by Design162163Embed privacy into the development lifecycle:1641651. **Proactive not reactive** — Anticipate privacy risks before they materialize1662. **Privacy as default** — Collect minimum data; don't rely on opt-out1673. **Embedded into design** — Privacy is core functionality, not a bolt-on1684. **Full functionality** — Privacy doesn't mean diminished features1695. **End-to-end security** — Protect data throughout its lifecycle1706. **Visibility and transparency** — Data subjects should know what's collected1717. **Respect for user privacy** — User-centric design, give meaningful choices172173**Implementation checklist for new features:**174- [ ] Data flow mapping completed175- [ ] Legal basis identified and documented176- [ ] Data minimization applied (collect only what's needed)177- [ ] Privacy notice drafted at point of collection178- [ ] Access controls designed in179- [ ] Retention schedule determined180- [ ] Third-party data sharing identified181- [ ] Cross-border transfer mechanism assessed182- [ ] Encryption standards applied183- [ ] Incident response plan updated184185## Common Compliance Pitfalls186187| Pitfall | Risk | Prevention |188|---------|------|------------|189| Assuming one regulation covers everything | Missing jurisdiction-specific requirements | Map all applicable regulations per data flow |190| Storing data indefinitely | Violates storage limitation | Implement and enforce retention schedules |191| Relying solely on consent | Consent can be withdrawn; other bases may be more appropriate | Identify primary legal basis; document alternatives |192| Ignoring cross-border transfers | Major fines under GDPR Schrems II framework | Map data flows; implement SCCs or BCRs where needed |193| Treating anonymization as silver bullet | Re-identification risks remain | Use formal anonymization standards and verify |194| Not documenting compliance | Cannot prove accountability without records | Maintain ROPA, PIAs, and processing logs |195| Forgetting employees' privacy rights | Employee data is still personal data | Apply same rigor to internal processing |196| Overlooking data processor obligations | Liability flows both ways | Review DPAs; ensure processors have equivalent safeguards |197198## Red Flags199200- Collecting data without a documented legal basis201- Data retention periods described as "indefinite" or "as needed"202- No process for handling DSARs203- Personal data stored in unencrypted form204- Cross-border transfers without documented safeguards205- No incident response plan for data breaches206- Cookie consent that doesn't offer equal accept/reject options207- Dark patterns that nudge users toward sharing more data208- Third-party data sharing without adequate DPAs209- Logging or analytics that capture PII unnecessarily