Whose Data Is It, and Who Sets the Terms?
Written by Yux Seow, Cultural Research and Development Lead
It’s not difficult to imagine that somewhere in an archive, in a government database, or in a shelf of an old office, data about an Aboriginal community and their Country sits hidden away gathering dust. It might be school attendance figures, housing statistics, or a heritage survey commissioned decades ago by a proponent who has since moved on. The community and Country remain the main subject but someone else holds the data, decides who else can access it, and decides what it means.
This situation is the clearest way that I’ve been able to explain what Indigenous Data Sovereignty is about and why it’s not an abstract idea but rather a series of practical questions with practical answers. Who holds the data, what does the data say, and who is allowed to do something with it?
Data is never neutral. It is a record of decisions someone made.
Every dataset carries the fingerprints of the choices that produced it. What was measured and what wasn't. Who was asked and who wasn't. What categories were available to choose from. Which findings were considered worth resourcing.
Those choices are usually invisible by the time the data reaches a spreadsheet. But they determine what data can be used to claim, and what it can be used to contest.
Indigenous Data Sovereignty, IDS from here on, is: the right of Indigenous peoples to exercise ownership over Indigenous data. Ownership of data can be expressed through the creation, collection, access, analysis, interpretation, management, dissemination and reuse of Indigenous data. That means deciding what gets collected, who can access it, how it is interpreted, and what it is used for. Importantly, it covers data collected about communities as much as data collected by communities.
We've already written about the risk. This series is about the value of Indigenous Data Sovereignty.
Over the past year or so, we've published on why IDS matters now more than ever, on what a data strategy actually involves, on how IDS changes the shape of a partnership, and on where the movement is heading. Read together, those posts make a case that is largely about protecting culture. Here is what you stand to lose. Here is what happens when knowledge ends up on servers you don't control, governed by rules you didn't set.
That case remains strong and I stand behind it. But it is only half the argument, and it is the half that tends to position communities as people with something to defend rather than people with the power to build and steward alternative futures.
This series takes up the other half. Data held by an Aboriginal organisation is an asset, one that can be protected and put to work. The word asset matters, so it's worth being precise about it.
A quick note on how this series is written: I explain things in threes. I’ve found it to be the easiest way to unpack things that are complex. You’ll notice it here. Each essay turns on one set of three, and this one starts with the word asset.
Three tests for an asset
An asset isn't just something valuable. It is something valuable that you can actually deploy. Three tests separate data that works as an asset from data that doesn’t, and cultural data often fails all three. The failure is rarely in the data. It's that the organisations holding it have been chronically under-resourced to treat it as one.
Your organisation knows what you have. An organisation with an asset can tell you what's in it. Most Aboriginal organisations hold far more than anyone in the general population might realise: monitoring records from ranger teams, survey results, mapping from projects that finished years ago, recordings, photographs, correspondence, and heritage surveys. Much of it is evidence about Country that carries economic and political weight. Around 58% of Australia’s critical minerals sit on land where Indigenous peoples have right to negotiate, and roughly 43% of renewable energy and transmission infrastructure required for net zero would have to sit on the Indigenous land estate. The transitions the nation is betting on run through Country, and the records describing Country sit in your organisation. If nobody can say what exists and where it sits, it isn't functioning as an asset. It's just accumulation.
Your organisation controls who uses it, on what terms, and for what purposes. Custodianship that can't be exercised isn't custodianship. This is where Indigenous Cultural and Intellectual Property (ICIP) meets the practical question of systems and cultural protocols. Who can see what, which material is open, which is restricted, and who decides that. A dataset that anyone with a login can access is not under anyone's control, no matter what the agreement says.
It produces value over time. An asset returns something. For cultural data that return is the ability to answer a question quickly and with authority. To come to a negotiation already knowing what's on Country and its value. To make a case to a funder using your own evidence rather than someone else's. To have a new ranger coordinator receive the full organisational record rather than whatever their predecessor had time to explain on their way out.
Data that passes those three tests changes an organisation's position. Data that fails them costs money to store and delivers little value.
Why this is more pressing than it was five years ago
Aboriginal organisations are now generating more data about Country than at any point in history. Ranger teams run structured monitoring on Country to a standard that holds up in reporting to funders. Field apps capture points and photographs on a phone. Satellite imagery of any given part of Australia is available at a resolution and frequency that would have been unthinkable a decade ago. At the same time, data is flowing back. There is a growing movement around data repatriation: records, recordings, photographs, maps, and heritage surveys held for decades by government agencies and institutions being returned to the communities they came from. Repatriation is a genuine win, it hands an Aboriginal organisation back its inheritance - material collected under someone else’s categories, often with no record of who the knowledge holders were, of their consent, and arriving faster than the systems are built to hold it properly. The volume of material passing through Aboriginal organisations is immense, and it’s arriving from two directions: new capture on Country, and returned data.
However, the systems consuming that data have become far less visible. Data now moves into platforms, models, and products in ways that are difficult to trace and even harder to reverse. Where two decades ago the risk was a report sitting in the wrong filing cabinet, the risk now is that material might be absorbed into systems that nobody can point to and nobody can withdraw it from.
Together, these two shifts are the reason data governance can't wait until later. More is being produced, and it is becoming harder to follow where it goes. Decisions about how community and cultural data is held are being made right now, often by default, often by whoever set up or designed the software.
Over three more essays, I'll work through the complexities of Indigenous Data Sovereignty more deeply.
I'll make the case that IDS is a need rather than a nice-to-have, and look at how the default data environment doesn't benefit communities. I'll look at what happens after data governance is settled: how technology gets shaped to fit cultural authority rather than the other way around, and why the thing that lasts is the governance, not the technology. And I'll close on what it costs: the capability all of it depends on, why the capital has not reached it, and what I am asking of the people who fund this work.
There is no single model for any of this. Every community has different obligations, different knowledge, different priorities, different people who hold the authority to decide. What I do think is that the question at the start of this essay has a right answer, and that too many organisations are currently living with the wrong one by accident rather than by choice.
If your organisation is somewhere in that position, holding a lot and sure of very little, that's a normal place to start. It's where most of this work begins.
