Sovereign AI use case · Indigenous Governments and Organizations

Community-controlled data for AI in Indigenous organizations

Communities are cautious about tools that move information elsewhere, for good reason. Without a deployment they control, they either avoid AI and keep carrying heavy administrative loads, or they accept terms that do not reflect their rights. Unclear access and use rules create risk for members' personal information and for collective knowledge. Trust, once lost, is hard to rebuild.

Inaaya use-case library · Last reviewed 19 November 2026

In short

Community-controlled data for AI means that an AI assistant works under the community's own data-governance rules: the community decides what is stored, where, who can see it and how it may be used. This can support First Nations principles of ownership, control, access and possession, and the principles Inuit and Métis organizations set for themselves.

Who does this today.

Directors, IT staff, data governance committees and leadership are responsible for community information. It is hard because many tools store data outside the community's control, terms of service are written for others' benefit, and community information carries cultural and historical sensitivity.

What Inaaya can do, step by step.

  1. Documents the community's data-governance rules, sensitivity categories and access decisions with the community's data governance lead.
  2. Deploys in the location and environment the community chooses, on a model and host the community approves.
  3. Sets access by role as the community directs, including restrictions on sensitive categories.
  4. Records every action and approval in a log the community can review.
  5. Excludes data from any use the community has not approved.
  6. Supports export and removal of community data on the community's request.
  7. Prepares regular access and activity reports for the data governance committee.
You provide
  • Community data-governance policy or principles
  • Sensitivity categories and access decisions
  • Chosen hosting location
You get
  • Deployment matching the community's rules
  • Role-based access settings
  • Activity and access log
  • Periodic governance reports
Your people decide
  • Leadership or the data governance committee approves the deployment and access rules
  • Committee reviews activity reports
  • Community decides on any new use of data
Data and controls
  • Deployed so data stays in the location and environment the community chooses, with access set by the community
  • Supports First Nations principles of ownership, control, access and possession, and the data-governance principles Inuit and Métis organizations set for themselves
  • Community information is not used for any purpose the community has not approved
  • Every action, draft and approval recorded in a log the community can review
How to measure it
  • Access reviews completed
  • Requests outside approved use, refused and reported
  • Governance reports delivered on schedule
  • Data export or removal requests completed
The aim

Designed to bring the benefits of AI without giving up control of community information. Decisions stay with community leadership.

Questions people ask.

Can AI support First Nations principles of ownership, control, access and possession?

An AI assistant can be deployed where the community chooses, with access and use decided by the community and every action logged. That can support those principles, and the community decides whether a deployment meets its standards.

How should Inuit and Métis organizations approach AI and their data?

By applying the data-governance principles their own organizations set, and choosing a deployment where they control location, access and use.

Can a community take its data back from an AI deployment?

A deployment can be set up so the community can export and remove its data on request, as part of the community's control.

Related use cases.

Apply to be a founding partner