> For the complete documentation index, see [llms.txt](https://sexytrees.savimbo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sexytrees.savimbo.com/foundations/data-sovereignty.md).

# Data sovereignty

*<mark style="color:$danger;">This is a</mark>* [*<mark style="color:$danger;">bricolage</mark>*](/foundations/bricolage.md) *<mark style="color:$danger;">protocol; which means we are building it in public! Some pages are under construction — but check back soon its updating fast!</mark>*&#x20;

**Properly applying** [**data sovereignty**](#user-content-fn-1)[^1] **practices and principles significantly alters project design at all levels. Therefore, it must be understood and applied early in all collaborations.**&#x20;

Data is not like other things a project handles. It can be copied perfectly, instantly, and forever.

We treat data about, from, or concerning Indigenous, AfroDescendant, or local communities as an asset under their control — not a free resource to be extracted, aggregated, or monetized by outside parties.

This is an ethical decision, a business policy, and will eventually, in our opinion, be robust international law.&#x20;

### Data soverienty and FPIC

<mark style="color:violet;">TL:DR = FPIC is the process, data sovereignty is the substance</mark>&#x20;

Data falls under standard [Free Prior and Informed Consent (FPIC)](/appendices/fpic.md) guidelines with the caveat that it can be easily copied and used in perpetuity, making ongoing consent difficult. It also has risks of being mistranslated, and it's very difficult for grassroots communities to stay adequately informed on it. Thus, it requires additional controls, and data sovereignty could be considered the practical feasibility and rules that allow for the extensio[^2]n of FPIC principles to this specific domain, which is definitely an emerging case.

### Data versus information&#x20;

We learned quickly not to assume epistemology[^3] in data negotiations with grassroots communities. For this primer, we will use the word "data" and the word "information" as separate but related concepts.&#x20;

* **"data"** as it is understood in the industrialized world is already covering too wide a variety of topics (eg. copyright, intellectual property, genetic data, bioactive compounds, cultural practices)
* **"data"** as it is often interpreted by grassroots communities, extends into memory, history, communication between living beings, and a much broader scope than an industrial person might anticipate. For this expanded scope, we will use the word "information".

### Marching orders for current work

There is a fear of working on this topic, of being prosecuted by history.&#x20;

However, the very definition of ethics is making decisions under uncertainty, with power ([Jonas, 1984](https://amzn.to/4uikaGI)). Therefore, the ethical risks of choosing not to engage must be weighed carefully against the risks of action ([Rachels, 1975](https://doi.org/10.1056/NEJM197501092920206); [Spranca, Minsk & Baron, 1991](https://doi.org/10.1016/0022-1031\(91\)90011-T)).

In late 2025, we participated in a preliminary collective opinion from Indigenous leaders recruited from across the world, with different backgrounds and data perspectives. The following instructions from that group are the marching orders we are currently working under.&#x20;

* **A proper collective Indigenous opinion** can only be formed with an authentic Participatory Action Research (PAR) study. In the absence of that tool, which we have been unable to fund, we can only work on preliminary feedback.&#x20;
* **Inaction is not appropriate**. This work is valuable, and preliminary negotiations and education are warranted if they are narrow and not misrepresented as collective decisions.&#x20;
* **Format is critical.** Academic formats are not viable tools for collective decision-making involving traditional communities whose first languages are often rare and who may have very limited understanding. [Multimedia, multilingual content](https://www.savimbo.com/data) is required with concepts broken down into component modules.
* **Training must be funded** for advocates to begin translating the risks, benefits, and threats of data in the information age to elders, leaders, communities, and collectives. Emergent positioning should be expected, and longitudinal workgroups, case studies, and negotiating panels are required.&#x20;
* **Any work on this topic must be enforceable first**. History has shown rampant abuse on this topic because data can be copied and reused or misused. It's critical that we focus on negotiating enforceable cases with narrow scope first and avoid any broad claims to applicability.&#x20;
* **Data is too broad a term**. The feedback we have gotten from our ethics panel is extensive, ranging into the fields of quantum physics, information, and cultural practices, which significantly exceeded the realm of any Sexy Trees projects. We have decided to work from the basis of narrow case studies, like the [eDNA consent case](/appendices/edna-case-study.md) in the appendix. Then properly negotiate conscribed cases and build [a library of practical-use documents](https://www.savimbo.com/data). Broad permissions are too easy to misuse and do not account for the heterogeneity of either Indigenous thought or information-age threats on the topic. &#x20;

### Authoritative sources on data sovereignty

* The right to collect and use of community property should be guided by the [IEEE Recommended Practices on Indigenous Peoples Data Provenance Standard](https://standards.ieee.org/ieee/2890/10318/)
* Data should be stored with Local Context TK labels (knowledge) and BK notices (DSI). As in the [Cyverse database](https://www.google.com/url?q=https://user.cyverse.org/\&sa=D\&source=docs\&ust=1780233721017082\&usg=AOvVaw1ofYffUMjx6EObkNvtNkWC)

[^1]: Often referred to as Indigenous data soverienty or IDsov. When applicable to all communities we'll use the general term.&#x20;

[^2]:

[^3]: Ways of knowing about the world. For instance book learning, vs practical experience.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sexytrees.savimbo.com/foundations/data-sovereignty.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.