Contract
- Input: system architecture, data types, users, jurisdictions.
- Output: Privacy Impact Assessment + data-flow map + compliance checklist.
- Side effects: may require legal review (not done by skill alone).
- Dependencies: legal / compliance expert for final approval.
- Stop condition: PIA and checklist complete; legal review noted.
- Risk: medium — privacy violations have legal / reputation consequences; requires expert validation.
- Boundary: designs privacy controls and documents compliance gaps; does not provide legal advice.
Privacy Engineering
Design privacy-protecting systems — GDPR / CCPA / HIPAA — with explicit data minimisation, anonymisation, consent, and breach-notification controls.
Process
1. Data inventory
- What data is collected? (PII, health data, financial, behavioural, biometric, location)
- Source (user input, sensors, third party, derived).
- Classification (public, internal, confidential, restricted, secret).
Completion criterion: inventory saved.
2. Purpose and legal basis
- Why is each data needed? Can the purpose be achieved with less data?
- Legal basis: consent, contract, legal obligation, vital interest, public task, legitimate interest (with balance test).
- Users must be informed clearly.
Completion criterion: purpose and basis stated per data type.
3. Data-flow mapping
Map flows: collection → processing → storage → sharing → archive → deletion.
Mark where data crosses borders (jurisdiction change) or enters third-party systems.
Completion criterion: data-flow diagram saved.
4. Controls
- Minimisation: collect only needed fields; use pseudonymisation where possible.
- Encryption: at rest (AES-256), in transit (TLS 1.3), in use (homomorphic / secure enclaves if required).
- Access: least-privilege; role-based; audit logs.
- Retention: define retention period per data type; automatic deletion after period.
- Consent: explicit, granular, revocable; record consent state.
- Breach notification: 72-hour notification for GDPR; process for detection, containment, notification, remediation.
Completion criterion: controls matched to risks; gaps documented.
5. Impact assessment
Identify high-risk processing (systematic profiling, large-scale sensitive data, automated decision-making with legal effects). For high-risk: conduct Data Protection Impact Assessment (DPIA / PIA).
Completion criterion: PIA completed for high-risk processing; justification if low-risk.
6. Checklists and compliance
- GDPR: lawful basis, consent, data subject rights (access / rectification / erasure / portability / restriction / objection), DPO, breach notification, transfer safeguards.
- CCPA: notice at collection, opt-out of sale, non-discrimination, service-provider contracts.
- HIPAA: PHI safeguards (administrative, physical, technical), business associate agreements.
Completion criterion: checklist filled; gaps flagged for legal review.
1---2name: sec-privacy-engineering3description: Design privacy-protecting systems — GDPR / CCPA / HIPAA compliance, data minimisation, anonymisation, consent management, data retention, breach notification — with explicit privacy impact assessments.4---56## Contract78- **Input:** system architecture, data types, users, jurisdictions.9- **Output:** Privacy Impact Assessment + data-flow map + compliance checklist.10- **Side effects:** may require legal review (not done by skill alone).11- **Dependencies:** legal / compliance expert for final approval.12- **Stop condition:** PIA and checklist complete; legal review noted.13- **Risk:** medium — privacy violations have legal / reputation consequences; requires expert validation.14- **Boundary:** designs privacy controls and documents compliance gaps; does not provide legal advice.1516# Privacy Engineering1718Design **privacy-protecting systems** — GDPR / CCPA / HIPAA — with explicit data minimisation, anonymisation, consent, and breach-notification controls.1920## Process2122### 1. Data inventory23- What data is collected? (PII, health data, financial, behavioural, biometric, location)24- Source (user input, sensors, third party, derived).25- Classification (public, internal, confidential, restricted, secret).2627**Completion criterion:** inventory saved.2829### 2. Purpose and legal basis30- Why is each data needed? Can the purpose be achieved with less data?31- Legal basis: consent, contract, legal obligation, vital interest, public task, legitimate interest (with balance test).32- Users must be informed clearly.3334**Completion criterion:** purpose and basis stated per data type.3536### 3. Data-flow mapping37Map flows: collection → processing → storage → sharing → archive → deletion.38Mark where data crosses borders (jurisdiction change) or enters third-party systems.3940**Completion criterion:** data-flow diagram saved.4142### 4. Controls43- **Minimisation:** collect only needed fields; use pseudonymisation where possible.44- **Encryption:** at rest (AES-256), in transit (TLS 1.3), in use (homomorphic / secure enclaves if required).45- **Access:** least-privilege; role-based; audit logs.46- **Retention:** define retention period per data type; automatic deletion after period.47- **Consent:** explicit, granular, revocable; record consent state.48- **Breach notification:** 72-hour notification for GDPR; process for detection, containment, notification, remediation.4950**Completion criterion:** controls matched to risks; gaps documented.5152### 5. Impact assessment53Identify high-risk processing (systematic profiling, large-scale sensitive data, automated decision-making with legal effects). For high-risk: conduct Data Protection Impact Assessment (DPIA / PIA).5455**Completion criterion:** PIA completed for high-risk processing; justification if low-risk.5657### 6. Checklists and compliance58- GDPR: lawful basis, consent, data subject rights (access / rectification / erasure / portability / restriction / objection), DPO, breach notification, transfer safeguards.59- CCPA: notice at collection, opt-out of sale, non-discrimination, service-provider contracts.60- HIPAA: PHI safeguards (administrative, physical, technical), business associate agreements.6162**Completion criterion:** checklist filled; gaps flagged for legal review.
quantumquirkxyz