Privacy & Data Protection · PD-Q06

Question: Are data-minimization and purpose-limitation principles applied in system design and operations?

Why This Matters

Collecting only what is necessary limits exposure and reinforces trust. Purpose limitation ensures data is used strictly for declared needs.

Maturity

0 — Unaware
Collect “everything just in case.”
1 — Ad Hoc
Minimalist practice on individual discretion.
2 — Defined
Policy mandates data-minimization and purpose review.
3 — Managed
Forms and APIs reviewed before deployment.
4 — Integrated
Automated field-usage checks and purpose tagging.
5 — Optimized
Continuous monitoring of purpose drift and auto-alerts.

How to Level Up

From → To Actions
0 → 1 Eliminate unnecessary fields in new forms.
1 → 2 Adopt written policy and approval checklist.
2 → 3 Include privacy review in SDLC gates.
3 → 4 Tag fields with lawful purpose metadata.
4 → 5 Automate scans for over-collection and drift.

Enablers

Evidence

KPIs

Low-Cost / Open-Source Options (MSME)

Purpose Tool Notes
Data catalog Amundsen / DataHub Open-source metadata management
Forms review Google Forms / Excel Manual audit
Automation OpenRefine Detect redundant fields

Common Pitfalls

Compliance Mapping

Standard Clauses / Notes
ISO/IEC 27701 7.4 (Data minimization)
DPDP Act 2023 Sec 6 (Limitation of Purpose)
GDPR Art. 5(1)(c) & (1)(b)
NIST CSF 2.0 ID.DP-03
NIRMATA Mapping PD-Q06 enforces collection discipline.