Skip to content

JPeetz/agent-skills / skills/compliance-legal/data-privacy-compliance

data-privacy-compliance

Verified

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.

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:

PrincipleDescriptionImplementation
LawfulnessProcess data on a valid legal basisIdentify and document the basis before collection
Purpose LimitationOnly use data for the purpose it was collectedDocument purposes at collection point
Data MinimizationCollect only what's necessaryAudit collection fields regularly
AccuracyKeep data accurate and up to dateImplement verification workflows
Storage LimitationDelete when no longer neededEnforce retention schedules
Integrity & ConfidentialitySecure data appropriatelyApply encryption, access controls
AccountabilityDemonstrate complianceMaintain records of processing

GDPR Compliance Workflow

Determine Applicability

Check if GDPR applies:

  1. Does the organization have an establishment in the EU/EEA?
  2. Does the organization offer goods/services to data subjects in the EU/EEA?
  3. Does the organization monitor behavior of data subjects in the EU/EEA?
  4. 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):

FieldDescription
Processing purposeWhy is the data being processed?
Data categoriesWhat types of personal data?
Data subjectsWhose data? (customers, employees, etc.)
Legal basisArt. 6 basis (consent, contract, legal obligation, etc.)
RecipientsWho receives the data?
TransfersCross-border transfer mechanisms
Retention periodHow long is data kept?
Technical safeguardsEncryption, access controls, etc.

Data Subject Rights Handling

When receiving a DSAR, follow this workflow:

  1. Verify identity — Confirm the requestor is who they claim to be (without excessive data collection)
  2. Acknowledge receipt — Within the regulatory timeline (GDPR: without undue delay, max 1 month)
  3. Scope the request — Identify what personal data is held, where, and in what systems
  4. Retrieve data — Search across all systems (production, backups, logs, analytics)
  5. Redact third-party data — Remove or anonymize data of other individuals
  6. Format response — Machine-readable format if requested; common formats include JSON, CSV, PDF
  7. Deliver securely — Encrypted delivery, identity-verified channel
  8. Document — Log the request, steps taken, and outcome for accountability

Breach Notification

Timeline varies by jurisdiction:

JurisdictionNotification TimelineRegulatorIndividuals
GDPR (EU)72 hoursLead Supervisory AuthorityWithout undue delay
CCPA (California)No specific timelineAttorney GeneralPromptly
HIPAA (US Healthcare)60 daysHHSWithin 60 days
LGPD (Brazil)72 hoursANPDSimultaneously
PIPEDA (Canada)As soon as possibleOPC/OIPCAs soon as possible

Breach response workflow:

  1. Contain — Stop the breach from spreading (revoke credentials, isolate systems)
  2. Assess — Determine scope: what data, how many records, who is affected
  3. Notify — Inform regulator within required timeline
  4. Communicate — Inform affected data subjects with clear remediation steps
  5. Document — Record all actions taken, timelines, and decisions
  6. Remediate — Fix the root cause, update security measures
  7. Review — Post-incident review to prevent recurrence

CCPA/CPRA Compliance

Key Rights Under CCPA/CPRA

RightDescriptionTimeline
Right to KnowWhat personal data is collected, used, shared10 business days
Right to DeleteRequest deletion of personal data45 calendar days
Right to Opt-OutOpt out of sale/sharing of personal data15 business days
Right to CorrectCorrect inaccurate personal dataReasonable timeframe
Right to Limit UseLimit use of sensitive personal dataReasonable timeframe
Right to Non-DiscriminationNo price/service discrimination for exercising rightsOngoing

CCPA Assessment Checklist

  • Determine if business is subject to CCPA (revenue >$25M, 100K+ records, or 50%+ revenue from data)
  • Update privacy notice with CCPA-required disclosures
  • Implement opt-out mechanism (Do Not Sell/Share link)
  • Establish DSAR handling procedures
  • Audit data sharing with third parties
  • Review and update data processing agreements
  • Train staff on CCPA requirements
  • Document consumer request metrics

HIPAA Compliance (US Healthcare)

Key Rules

RuleFocusKey Requirements
Privacy RuleProtected Health Information (PHI) use and disclosurePatient rights, minimum necessary standard
Security RuleAdministrative, physical, technical safeguardsRisk analysis, access controls, audit controls
Breach Notification RuleNotification following breachTimelines vary by scale
Enforcement RulePenalties and proceduresTiered 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:

  1. Proactive not reactive — Anticipate privacy risks before they materialize
  2. Privacy as default — Collect minimum data; don't rely on opt-out
  3. Embedded into design — Privacy is core functionality, not a bolt-on
  4. Full functionality — Privacy doesn't mean diminished features
  5. End-to-end security — Protect data throughout its lifecycle
  6. Visibility and transparency — Data subjects should know what's collected
  7. Respect for user privacy — User-centric design, give meaningful choices

Implementation checklist for new features:

  • Data flow mapping completed
  • Legal basis identified and documented
  • Data minimization applied (collect only what's needed)
  • Privacy notice drafted at point of collection
  • Access controls designed in
  • Retention schedule determined
  • Third-party data sharing identified
  • Cross-border transfer mechanism assessed
  • Encryption standards applied
  • Incident response plan updated

Common Compliance Pitfalls

PitfallRiskPrevention
Assuming one regulation covers everythingMissing jurisdiction-specific requirementsMap all applicable regulations per data flow
Storing data indefinitelyViolates storage limitationImplement and enforce retention schedules
Relying solely on consentConsent can be withdrawn; other bases may be more appropriateIdentify primary legal basis; document alternatives
Ignoring cross-border transfersMajor fines under GDPR Schrems II frameworkMap data flows; implement SCCs or BCRs where needed
Treating anonymization as silver bulletRe-identification risks remainUse formal anonymization standards and verify
Not documenting complianceCannot prove accountability without recordsMaintain ROPA, PIAs, and processing logs
Forgetting employees' privacy rightsEmployee data is still personal dataApply same rigor to internal processing
Overlooking data processor obligationsLiability flows both waysReview 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
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall