State Data Hubs: Convenience Today, Control Tomorrow?

Across the country, state governments are racing to build “integrated data systems,” “state data hubs,” and “longitudinal data platforms” that link records across agencies—education, health, welfare, workforce, criminal justice, and more. The sales pitch is simple: better data means better decisions and more “whole-person” services.

But once you connect those dots, you’re not just improving customer service. You’re building a single, lifelong file on each person—from birth through school, into the workforce, through encounters with the justice system or the hospital. That file can be analyzed by algorithms, shared with “partners,” and repurposed by future officials who may not share Missouri’s respect for liberty.

The question Missourians must ask is not “How do we regulate state data hubs?” but “Should we be building them at all?”

What are state data hubs and integrated data systems?

In policy circles, these systems are often called Integrated Data Systems (IDS) or statewide longitudinal data systems (SLDS). They are designed to connect data from multiple agencies so government leaders can run cross-agency analyses and “data-driven” programs.

Common features include:

• Unique identifiers that tag each person across many databases—education, welfare, corrections, workforce, and more.
• Centralized or federated data warehouses that pull those records together into one platform for analysis and dashboards.
• Cross-agency governance boards that set rules for who can access what data, for which projects, and under what conditions.

Colorado’s Statewide Longitudinal Data System, for example, “securely connects data across state agencies and time” to support decisions on education and workforce outcomes. Similarly, the Linked Information Network of Colorado (LINC) links state administrative data for research across health, human services, and justice.

Arizona’s IDS links records across agencies for “cross-sector analysis of workforce and education,” and Iowa’s I2D2 is marketed as a way to connect leaders with “comprehensive” data from services systems to tackle social problems. The pattern is clear: collect everything, connect everything, and analyze everything.

Missouri is not immune

Missouri, like many states, is moving toward more integrated systems even if they’re not yet branded as a single “state data hub.”

• The Department of Mental Health and its partners are building a technology solution that allows health and social-care providers to access and exchange person-centered care plan data for individuals with developmental disabilities through Missouri’s Health Information Exchange ecosystem.
• Law enforcement systems like the Missouri Data Exchange already aggregate criminal-justice data across agencies, feeding into broader law enforcement data-sharing networks.

None of these efforts, by themselves, equal a full-blown, cradle-to-grave state data hub. But they are pieces of the same puzzle: health data, justice data, and social-service data being moved into more connected, more shareable digital platforms.

“Whole-person” data is also whole-life surveillance

Proponents talk about breaking down “silos” to serve the “whole person”—for example, linking child welfare, education, and Medicaid data to see which programs “work” or to identify “high-risk” children.

But that same integration means:

• A child’s school records (attendance, discipline, disabilities, test scores) can be tied directly to their family’s welfare history, housing status, and juvenile-justice encounters.
• Health and behavioral-health data (including mental-health diagnoses and medications) can be tied to criminal records, emergency-room visits, and public-benefit usage.
• Workforce and employment records can be aligned with past schooling and current benefit status to classify people as “on track” or “high risk.”

Once that full picture exists in a central or federated hub, it becomes very easy for governments—and their corporate or academic partners—to build risk scores, predictive models, and “early warning” flags for individuals and neighborhoods.

Today those tools are marketed as helping social workers and policymakers. Tomorrow they can be repurposed to justify heavier surveillance, to deny opportunities, or to target political and religious communities that do not conform.

Data hubs are magnets for mission creep

Supporters of these systems point to “governance frameworks” and privacy rules, but real-world experience shows how quickly those limits can erode when centralized data is available.

Recent reporting reveals that immigration authorities gained extensive access to state driver’s license data through Nlets—a nonprofit network that connects state, local, and federal law-enforcement databases—even in states that thought they were restricting cooperation. Lawmakers noted that the technical complexity made it hard for state officials to even understand what data they were sharing.

At the federal level, Immigration and Customs Enforcement has also gained access to a massive Centers for Medicare and Medicaid Services database containing detailed health and demographic information on tens of millions of Medicaid recipients, raising serious questions about how benefits data can be repurposed for enforcement.

Even if we agree with the ultimate goal in a particular case— this is a dangerous precedent and shows that the Federal Government can access state data hubs in ways that state officials may not anticipate or control.

Why “good governance” isn’t enough

Advocates of state data hubs insist that strong data-governance boards, memorandums of understanding (MOUs), and privacy policies can protect people. But:

• MOUs can be rewritten. New leadership can expand sharing rules or add new “authorized users.”
• Statutes and regulations can change. Crises and political shifts are often used to justify new data uses.
• Technical complexity hides what’s really happening. Even well-meaning officials may not grasp how intertwined systems have become or where data is actually flowing.

Once the data is centralized and linked, the hard part is over—for those who want to expand surveillance. All they need is a new rule, a new partner, or a new algorithm. That is why the real issue is not how to regulate state data hubs; it is whether we will tolerate their existence in the first place.

How data hubs plug into the broader control grid

State data hubs don’t operate in a vacuum. They are one piece of a larger architecture:

• Real ID and digital ID provide a common identity key that can be used across systems.
• FedNow and potential CBDCs give government live visibility and potential control over financial transactions.
• Police-tech networks like “Blue Shield” track where people go and who they meet.
• Education systems feed in long-term records on children’s performance and attitudes.

Connect those to a state data hub, and you can:

• Score neighborhoods or individuals based on combined education, welfare, and justice data.
• Target “interventions” (or scrutiny) at families who do not fit preferred patterns.
• Link behavior to financial access through a programmable digital dollar or benefits card.

That is not science fiction. It is the predictable outcome of building systems that treat everyone as a datapoint to be monitored and nudged.

What Missourians should oppose

If we want to preserve real privacy and liberty, we cannot simply ask for “better privacy policies” around state data hubs. We need to oppose the core idea of comprehensive, cradle-to-grave government files that link every part of a person’s life together.

Here are concrete positions Missourians can press on local and state leaders:

• Oppose the creation of a centralized state data hub or integrated data warehouse.
  No statutory authorization, no executive-branch “data integration” office, and no cross-agency platform that links core human-services, education, and justice data.
• Oppose unique, cross-agency person identifiers for ordinary citizens.
  Agency-specific IDs may be necessary; a single ID that ties together schooling, welfare, health, and criminal justice is a recipe for abuse.
• Oppose mandatory participation of local agencies and private providers in state data-sharing schemes.
  Counties, schools, and nonprofits should not be coerced into feeding personal data into a statewide hub.
• Oppose contracts that give private vendors control over integrated state data.
  Third-party platforms should not be allowed to aggregate, mine, or commercialize Missourians’ personal information across systems.
• Oppose tying eligibility for funding to participation in integrated data projects.
  Grants and programs should not be used as leverage to pull more data into statewide analytics.

In short: no “one file” on every Missourian.

A better direction: limited data, local control

Government will always need some data to administer justice and basic services. The question is whether that data is limited, specific, and accountable—or whether it is pooled into massive hubs that can quietly become engines of social control.

Instead of building integrated data systems, Missouri can:

• Keep agency data narrow and siloed, with strict limits on sharing outside specific, lawful investigations or clearly bounded programs.
• Favor local decision-making over statewide dashboards, trusting local communities more than distant analysts with statistical models.
• Use de-identified, aggregated statistics where possible, instead of person-level linked data that can be re-identified or misused.
• Write hard limits into law on cross-agency data sharing, with clear penalties for violations— and no “innovation waivers” that carve holes in those protections.

This article is part of our broader Surveillance State in Missouri series. Viewed alongside Real ID, programmable money, police-tech networks, and UN-driven education models, state data hubs are not “just IT projects.” They are a central pillar of a system that sees people not as free citizens, but as profiles to be managed.

Missourians can choose a different path—one where government remembers its limits, honors the privacy and dignity of the individual, and refuses to build the databases that a future surveillance state would need.