Policies
Map.ca policy

Data Minimization Policy

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

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.

Requirements

  • 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.

Prohibitions

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

Related policies

Privacy PolicyWhat Map.ca collects, why, how long it is kept, who it is shared with, and what rights people have.Meaningful Consent PolicyMakes consent simple, understandable, layered, and revocable. Plain language, just-in-time notices, no dark patterns, no bundled consents.Data Retention and Deletion PolicyHow long Map.ca keeps data, what happens on deletion, and how URL permanence interacts with content deletion.