What is data sovereignty, and how does the software support it?

The definition, and why the wording matters

Indigenous data sovereignty is the right of Indigenous peoples to govern the collection, ownership, and application of their own data. It follows from the same inherent authority a tribe holds over its people, its land, and its resources.

It stands against a mainstream principle worth naming plainly: that data is subject to the laws of the nation in which it is stored. Under that principle, a record's protection depends on the address of the server holding it. Keeping the server in your building is how you keep the record under your law.

The CARE Principles give the practice its shape: Collective Benefit, Authority to Control, Responsibility, and Ethics. They are a governance framework rather than a statute, so their force in a purchase comes from the tribe writing them into its own data-governance code and into what it requires of any vendor.

What sovereignty looks like in the software

• The records live on hardware the tribe owns. There is no copy on a company's machine, so there is no copy under another jurisdiction.
• The keys are held by the tribe. Encrypted at rest means a stolen machine or a lost backup drive is unreadable ciphertext to whoever holds it.
• The AI runs in the building. Drafting, checking, and searching happen on your machines, so no case, name, or record is sent out.
• Access follows the job. A judge, a clerk, and a treasurer each see what their role requires, and sensitive actions need a sign-off first.
• Every act is provable by the tribe itself. You do not have to ask a vendor to vouch for your history. You verify it.
• The records are yours to move. Export at any time, in a format you can open, with the sealed history intact.

The rulebook that arrives with the cloud

The moment tribal justice records sit in a commercial cloud, a second rulebook applies alongside your own. Where a justice system touches criminal justice information, the FBI CJIS Security Policy governs how that information is stored, transmitted, and accessed, and it is on a modernization schedule with real dates.

Version 6.0 of the policy, issued in December 2024, maps its controls onto the NIST 800-53 framework and phases compliance in over several years. Storage protection has its own clock: validated cryptographic modules under the older FIPS 140-2 standard move to historical status in September 2026, so systems are expected to be on FIPS 140-3 validated modules.

None of this is a reason to avoid modernizing. It is a reason to modernize on hardware you control, where the physically secure location is your building and the compliance surface is small enough to see.

Air-gap capable is the strongest version of this posture: a system with no path to an outside network at all. It is available if your IT wants it, and everything, including the AI, keeps working.

Questions tribes ask about sovereignty

Is data sovereignty a legal requirement or a policy choice?

Both, in layers. Federal rules like CJIS and grant terms set floors for handling certain records. Above that floor, the tribe's own data-governance code decides who may hold and use tribal data, and that is where the CARE Principles are typically written in.

Can we require a vendor to respect our data governance?

Yes, in contract, and it is worth doing. The stronger position is structural: a system that never holds your data cannot violate your terms about holding your data.

Does keeping records in-house make them less safe?

The records are encrypted at rest on your hardware, with an encrypted backup you keep off site, and access is set by role. What changes is the number of parties who can reach them, which drops to one: you.