Policies Internal operating policies

Data Minimization Policy

Do not collect data because it might be useful later. Collect it only because it is necessary now.

Version
0.1.0
Effective
May 20, 2026
Last reviewed
May 20, 2026
Review cycle
every 6 months
Master Policy Index entry
§4 #8

Policy text

Data minimization is the second-safest position after collecting nothing. Map.ca’s default for every new feature is to ask whether the same outcome is possible with less data, fewer fields, shorter retention, or a less precise location. The doctrinal rule is short: do not collect data because it might be useful later; collect it only because it is necessary now.

It applies to product teams, vendors, AI agents, and anyone designing a Map.ca data collection. It is enforced by the Policy Impact Review (Constitution §7) and by code-level controls in the Data Classification Standard.

Principles this policy enforces

  • Consent must be meaningful
  • Collect less, protect more
  • Public data and personal data are not the same thing

What it requires

  • Document the necessity of every personal data field at design time.
  • Set a retention clock on every collected field before it ships.
  • Choose the least precise location accuracy that still serves the feature.

What it forbids

  • Do not collect data because it might be useful later.
  • Do not retain data beyond its documented retention period.

How it applies

References