High-risk processing documented with DPIA; mitigation strategies tracked
Why it matters
GDPR Art. 35 mandates a Data Protection Impact Assessment before commencing high-risk processing — this is not a retrospective exercise. High-risk processing categories include systematic user profiling, automated decision-making with legal effects, large-scale processing of special category data (health, biometrics, religion), and behavioral scoring. AI-built apps are especially prone to inadvertent DPIA triggers: recommendation engines, usage-based pricing tiers, and sentiment analysis of user content can all qualify. ISO-27001:2022 A.5.34 requires organizations to assess privacy risks before implementing new processing. Proceeding with high-risk processing without a DPIA is an Art. 35 violation even if no harm occurs.
Severity rationale
Low because the obligation only activates for high-risk processing activities, but when triggered, missing a DPIA is a direct Art. 35 violation that supervisory authorities can act on before any breach occurs.
Remediation
Identify whether any current or planned features trigger GDPR Art. 35 (profiling, automated decisions, special category data at scale). For each that does, document a DPIA before enabling the feature in production.
# DPIA: [Processing Activity] — e.g., "Behavioral Profiling for Feature Recommendations"
## 1. Description of Processing
What data, purpose, means, duration.
## 2. Necessity and Proportionality
Why necessary? Less privacy-invasive alternative considered?
## 3. Risks to Data Subjects
| Risk | Likelihood | Impact | Level |
|-------------------------|------------|--------|--------|
| Inaccurate profiling | Medium | High | High |
| Behavior data breach | Low | High | Medium |
## 4. Mitigations
| Risk | Mitigation | Owner | Status |
|----------------------|-------------------------------------------|-------|--------|
| Inaccurate profiling | Human review available; opt-out mechanism | PM | Done |
## 5. Residual Risk
If High residual risk: consult supervisory authority before proceeding (GDPR Art. 36).
Store DPIAs in docs/dpia/ alongside your other compliance documentation and review them when the processing purpose or scope changes.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Data Protection Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- gdpr · Art. 35 — Data protection impact assessment
- gdpr · Art. 36 — Prior consultation of supervisory authority for high-risk processing
- iso-27001:2022 · A.5.34 — Privacy and protection of PII
Taxons
History
- 2026-04-18·v1.0.0·Initial import from data-protection·automated