In this post

Key Takeaways

  • Data sovereignty means data answers to the laws and governance of the place, and the people, it comes from.
  • Three parties hold claims on the same dataset: national governments, the organization that collects it, and the community it describes.
  • 137 of 194 countries have data protection and privacy laws, according to UNCTAD.
  • Server location alone settles nothing. Vendor jurisdiction, encryption keys, and admin access count just as much.
  • CommCare offers regional cloud hosting, in-country storage, and self-hosting, and in its national eCHIS deployments the government owns the data.

What is data sovereignty?

Data sovereignty is the principle that data is subject to the laws and governance of the jurisdiction where it is collected and, increasingly, of the people it describes. The concept is about authority and control over data. Where data is physically stored is a separate question, and sometimes the less important one.

Three related terms get used interchangeably, but each means something narrower:

  • Data residency is the geographic location where data is stored.
  • Data localization is a legal mandate that certain data be stored and processed inside the borders where it was collected.
  • Digital sovereignty is a state or region's broader claim to control its digital infrastructure, including its networks and software.

Until recently, the term was mostly a clause in cloud computing contracts that procurement teams and privacy lawyers argued over. A single home visit in rural Senegal can now touch Senegalese law and a European funder's data policy, with the data stored by a US cloud provider. The shift came as ministries of health built national digital systems and communities started asking who benefits from information gathered about them.

Three levels of data sovereignty

Data sovereignty operates at three levels at once. National governments, the organization collecting the data, and the community it describes each hold a separate claim on the same records, and all three have to be satisfied.

LevelWho Holds AuthorityWhere It Shows UpReference Point
NationalGovernments and regulatorsData protection laws, transfer restrictions, health data rulesGDPR Chapter V, AU Data Policy Framework
OrganizationalThe organization that collects and stores the dataHosting choices, vendor contracts, data sharing agreementsHosting region and vendor terms
CommunityThe people and communities the data describesConsent, benefit sharing, community approval of data useCARE Principles

National data sovereignty

National sovereignty is the legal layer, set by each government's data protection law. It defines personal data and decides when it can be sent abroad. Sensitive data tends to get stricter handling. Under the EU's General Data Protection Regulation, for example, data concerning health sits in a special category that can't be processed unless a specific exception applies.

Organizational data sovereignty

Organizational sovereignty belongs to whoever collected the data, and it lives in paperwork more than in laws and regulations. An NGO can follow every applicable law to the letter and still lose practical control of its records through one weak contract. The usual culprits are a hosting region picked for convenience and vendor terms nobody read closely.

Community and Indigenous data sovereignty

Community sovereignty is the claim of the people a dataset describes, and Indigenous data sovereignty is its most developed form. The CARE Principles lay out the rights of Indigenous peoples to govern and benefit from data about them. Development programs usually meet this layer in consent forms and in agreements negotiated locally.

Which countries have data sovereignty laws?

Most of the world now has some form of data sovereignty law. According to UNCTAD, 137 out of 194 countries have legislation protecting data and privacy. The gaps sit where much global health work happens, with 61% of African nations and 48% of least developed countries covered.

The laws come in a few recognizable forms:

  • Localization mandates that require certain categories, such as health or government data, to stay in-country
  • Limits on cross-border data transfers that allow them only under set conditions
  • Sector rules for health, financial, or public sector data that sit on top of general data privacy rules

GDPR is the example cited most often. Its Chapter V lets personal data leave the EU only under set conditions, and the usual route is an adequacy decision, where the European Commission confirms another jurisdiction protects data to an equivalent standard. Sixteen countries and territories have one so far, among them Japan and Brazil, though some cover commercial organizations only.

The African Union took a continental approach. Its AU Data Policy Framework, published in 2022, asks member states to harmonize data governance while protecting collective interests and digital rights. Rules change often, so the first stop for current compliance requirements should be the local data protection authority.

Why server location does not settle data sovereignty

Server location does not settle data sovereignty, because a vendor's legal obligations travel with the company. A provider incorporated in one country can be ordered under that country's law to hand over data in its control, wherever its data center sits.

The CLOUD Act and vendor jurisdiction

The US Clarifying Lawful Overseas Use of Data Act is the best-known case. The CLOUD Act was enacted in March 2018 to speed access to electronic information held by US-based global providers, and it lets the US strike data access agreements with foreign partners such as the United Kingdom and Australia. A program storing data in Ireland with a US-headquartered provider has European servers and a provider still subject to US legal orders.

Control levers beyond location

Location is one lever among several. Teams that take sovereignty seriously ask who actually has access to data:

  • Encryption key management: who holds the keys, and whether the vendor can decrypt
  • Administrator access: which staff, and from where, can log in with admin privileges
  • Audit rights: whether the data owner gets a log of who accessed what
  • Export and exit terms: whether the full dataset comes back in a usable format when the contract ends

Many governments want more control than legislation demands. A ministry of health may be free to host patient files abroad and keep them on domestic servers anyway. A sovereign cloud, meaning a cloud service run under local jurisdiction by local staff, is one way to get that control, and keeping servers in-country or running the software yourself are others.

Data sovereignty in global health and development programs

In global health and development, sovereignty gets tested at every handoff, whether records move from a community to a program or from an implementing partner to a government. Ownership gets murky fast when the funder and the software come from abroad. Medical information raises the stakes, since the patients behind it are frequently vulnerable.

Ministry-owned national health systems

A ministry-owned national health system keeps the data with the ministry instead of with the partners who helped build it. CommCare is the national electronic community health information system (eCHIS) in eight African countries, and in those government eCHIS deployments all data is owned and managed by the government. Ethiopia's Federal Ministry of Health runs its own eCHIS for more than 17,000 health extension workers, a system it built with JSI and the USAID Digital Health Activity.

Donor-funded program data after the grant ends

Donor-funded program data needs an owner named before the grant ends, or it can end up stranded. A three-year maternal health project can produce longitudinal records on thousands of women. When those files sit in the implementer's account, the ministry and the mothers themselves can lose access the day the budget closes.

Beneficiary and research data crossing borders

Beneficiary data rarely stays where it was collected. Monthly figures travel from a country office to a regional hub, then on to headquarters and the funder, and every border crossed is a transfer that may need a legal basis. Each copy is also one more place a record can leak. Aggregated or de-identified reporting usually gives funders what they need without moving anyone's personal details.

Research data carries an extra layer of rules. Ethics boards in the host country and at the sponsoring institution commonly set conditions on data storage and on whether study records can be exported.

Data sovereignty requirements for program data

Data sovereignty requirements for program data start with knowing where the data goes, then matching each stop to the rule or agreement that governs it. Six steps cover most programs:

  1. Map the data. Record where data is collected, stored, processed, and accessed, including backups and exports sitting on staff laptops.
  2. Identify compliance obligations. List the privacy statute, sector rules for medical data, and the donor's data terms for every place the program operates.
  3. Make the hosting decision. Pick a setup that lets the program comply with local laws and ministry requirements, whether that means a regional cloud or a local server.
  4. Write it into contracts. Data processing and data sharing agreements should name who owns the data and who can export it.
  5. Set community terms. Consent language and any agreements with community leaders should state how the data can be used and who benefits.
  6. Plan the exit. Confirm the full dataset can be exported in usable formats when a program or vendor relationship ends.

A written data governance policy keeps these decisions out of one person's head. Revisit it whenever the work expands to a new location or partner.

How CommCare supports data sovereignty

CommCare supports data sovereignty by letting governments and organizations choose where their data resides and who controls it, from a regional cloud up to servers they run themselves.

Hosting OptionWhere Data LivesBest Fit
Regional cloudUS (Virginia), EU (Ireland), or India (Mumbai), on AWSPrograms that need data in a specific region without running infrastructure
HybridA cloud project space, with data mirrored to an in-country database that serves as the primary storeOrganizations with residency requirements the three regions do not meet
In-country government serverA designated government server, for eCHIS deploymentsMinistries running national community health systems
Self-hostedThe organization's or government's own serversTeams with the technical capacity to run the open-source platform
  • Regional hosting: Since the EU cloud launch in September 2025, new CommCare projects can be hosted in the EU, India, or the US at the same price and with the same features. The regions are isolated from each other, so teams pick one when they create a project space.
  • Open source and self-hostable: CommCare has been open source since 2007, so governments and organizations that need their own servers can run it. Dimagi's compliance certifications do not transfer automatically to a self-hosted instance.
  • In-country storage for eCHIS: Ministries can keep eCHIS data permanently on a designated in-country server and can move fully on-premise.
  • Security and compliance: CommCare's approach to data security includes SOC 2 Type 2 certification on paid plans, AES-256 encryption, and HIPAA Business Associate Agreements on Advanced and Enterprise plans.
  • Practical guidance: The data security playbook walks data managers and field teams through managing data and protecting sensitive data at each stage of its lifecycle.

To work out which setup fits your countries and funders, talk to the CommCare team.

Frequently asked questions

What are the CARE Principles for Indigenous data governance?

The CARE Principles are four standards for Indigenous data governance: Collective benefit, Authority to control, Responsibility, and Ethics. The Global Indigenous Data Alliance drafted them in 2018 as a complement to the FAIR principles, which help data get shared but ignore power imbalances and historical context.

What is the difference between data sovereignty and data governance?

Data sovereignty decides whose laws and whose authority apply to the data. Data governance is how an organization manages data under those laws, through its own data management policies and access controls.

Does GDPR require data to stay in the EU?

No. GDPR has no blanket rule that personal data must be stored in the EU. It restricts international data transfers out of the EU, which can happen through an adequacy decision, standard contractual clauses, binding corporate rules, or the other safeguards and exceptions in Chapter V.

No, not on its own. It is a principle, and it becomes enforceable only when a data protection law or a signed agreement applies. That is why two programs working in the same country can face different obligations.

Filed under