Policies Constitutional documents
Indigenous Data Sovereignty Policy
How Map.ca handles Indigenous community data, cultural places, traditional knowledge, names, language, heritage, and map layers.
- Version
- 1.0.0
- Effective
- May 20, 2026
- Last reviewed
- May 20, 2026
- Review cycle
- every 24 months
- Master Policy Index entry
- §4 #48
Policy text
Constitution §2 principle 9 names Indigenous data sovereignty as foundational, not optional. Map.ca’s business plan already commits to OCAP principles as part of Platform Integrity. OCAP — Ownership, Control, Access, and Possession — is described by the First Nations Information Governance Centre as a framework governing how First Nations data and information are collected, protected, used, and shared. This policy operationalizes that commitment.
Operational rules: Indigenous community data is added with community permission, structured according to local protocols, and remains under community control. Map.ca does not extract, repackage, or commercialize Indigenous data. Sensitive cultural layers — sacred sites, burial places, ceremony locations, traditional gathering places — are kept removable, hide-by-default where requested, and never indexed for public search without explicit consent.
Place names, language layers, and traditional knowledge get the same treatment. A map should not erase people, and on Map.ca it does not. Where Indigenous and settler names differ, the Place Names Policy defines presentation order and authority — with Indigenous review authority on the Indigenous-named layer.
Disputes that touch Indigenous data route to a designated community-review path, not to general moderation. Where a request from law enforcement, municipality, or other government body conflicts with the community’s expressed wishes about its own data, the Constitution’s principle 9 sets the order: the community’s sovereignty over its data is honoured.
Principles this policy enforces
- People own their presence
- Public data and personal data are not the same thing
- Indigenous data sovereignty is foundational
- Community benefit must survive scale
What it requires
- Get community permission before adding cultural, sacred, or traditional-knowledge layers.
- Follow OCAP principles for any data identified as First Nations data.
- Make sensitive cultural layers removable by community request.
- Route Indigenous-data disputes to a designated community-review path.
- Honour Indigenous review authority on Indigenous-named layers.
What it forbids
- Do not extract, repackage, or commercialize Indigenous data.
- Do not publish sensitive cultural sites without explicit community consent.
- Do not override community wishes on Indigenous data to satisfy a third-party request.
- Do not index Indigenous cultural layers for public search without consent.
How it applies
- Indigenous communities and nations
- Indigenous reviewers
- Map.ca staff
- Municipal and government partners
- Researchers and developers using Map.ca
References
- First Nations Information Governance Centre — OCAP principles
- Map.ca business plan — Platform Integrity / Indigenous data sovereignty
- Map.ca Policy Constitution §2 principle 9
Related policies
Cultural Heritage Policy
How Map.ca handles cultural-heritage sites, including those identified by Indigenous communities and historic-preservation bodies.
Place Names Policy
How Indigenous, settler, and minority-language place names are presented, ordered, and updated on Map.ca.
Map.ca Policy Constitution
The non-negotiable values of the platform. Policy sits above growth, monetization, convenience, partnerships, and speed.
Sensitive Location Data Policy
Protects homes, shelters, children’s programs, places of worship, support services, vulnerable populations, and safety-sensitive locations.