Skip to content

Data colonialism

A critical framework describing extraction and control of human-generated data through infrastructures that convert everyday life into appropriable economic resources.

Version
v1 · 2026-09-08 · History
Domain-specific #
4032
Origin domain
critical data studies
Subdomain
critical data studies

Core Idea

Authors differ on continuity with historical colonialism, labor, territory and metaphor; analysis must identify concrete ownership, extraction, coercion and benefit flows rather than using the label rhetorically. Platforms instrument activity, capture traces under asymmetric terms, centralize analytic power and monetize or govern populations while externalizing labor and privacy costs. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

Scope of Application

Data colonialism belongs to critical data studies and is useful where the analyst can specify the typed critical data studies carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the author and framework, population and activities, data type and collection infrastructure, consent and terms, ownership and access, labor, value extraction and beneficiary, governance power, historical comparison and contested boundary are explicit. The scope is broad within that domain but bounded by the need for the author and framework, population and activities, data type and collection infrastructure, consent and terms, ownership and access, labor, value extraction and beneficiary, governance power, historical comparison and contested boundary are explicit.

Clarity

The abstraction clarifies a crowded vocabulary by making the author and framework, population and activities, data type and collection infrastructure, consent and terms, ownership and access, labor, value extraction and beneficiary, governance power, historical comparison and contested boundary are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Data colonialism. Data colonialism compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: the typed critical data studies carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the author and framework, population and activities, data type and collection infrastructure, consent and terms, ownership and access, labor, value extraction and beneficiary, governance power, historical comparison and contested boundary are explicit independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of critical data studies because they reuse the typed critical data studies carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, Platforms instrument activity, capture traces under asymmetric terms, centralize analytic power and monetize or govern populations while externalizing labor and privacy costs., and type the carrier, state every parameter and convention in the definition, test that the author and framework, population and activities, data type and collection infrastructure, consent and terms, ownership and access, labor, value extraction and beneficiary, governance power, historical comparison and contested boundary are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for Data colonialismParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Data colonialismDOMAINPrime abstraction: Accumulation — is a kind ofAccumulationPRIME

Current abstraction Data colonialism Domain-specific

Parents (1) — more general patterns this builds on

  • Data colonialism is a kind of Accumulation Prime

    The proposed strict upward parent is prime:accumulation.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Data colonialism sits in a crowded region of the domain-specific corpus (28th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Political Economy & Global Transformation (34 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08