The Constitutional Limits on Federal Coercion of State Cooperation

Last updated 5 months ago. Our resources are updated regularly but please keep in mind that links, programs, policies, and contact information do change.

On January 25, 2026, Attorney General Pam Bondi sent Governor Tim Walz a letter demanding Minnesota’s complete voter registration database, Medicaid records, and food assistance program data. The offer: hand over the information, and federal immigration enforcement operations in Minnesota would stop. Refuse, and they would continue. The letter arrived the same day a federal immigration officer shot and killed a Minneapolis resident during an immigration raid.

Secretary of State Steve Simon called it “an apparent ransom to pay for our state’s peace and security.” He refused.

What followed was a constitutional question that courts haven’t fully answered: Can the federal government demand that states surrender sensitive personal information about their residents? Can it leverage ongoing law enforcement operations—or the threat of withholding federal funds—to extract compliance?

The legal framework governing federal-state data sharing remains murky, with different statutes and constitutional doctrines pointing in conflicting directions.

What the Federal Government Cannot Order States to Do

The constitutional principle at stake has an ungainly name—the rule against forcing states to do federal work—but a straightforward premise. The federal government cannot force state legislators to pass laws, cannot require state officials to enforce federal regulations, and cannot conscript state administrative systems to accomplish federal objectives.

The Supreme Court has developed this doctrine over the past three decades, in cases involving radioactive waste disposal and gun background checks. In 1992, the Court struck down a federal law that required states to either adopt federal waste disposal regulations or take title to radioactive waste themselves. Five years later, it invalidated provisions of the Brady Act that required state law enforcement officers to conduct background checks on gun purchasers.

The Court’s reasoning in both cases emphasized that forcing states to do federal work violates a constitutional rule that protects state power to protect individual liberty. When the federal government forces states to implement federal policy, it makes it hard for voters to know who’s responsible. Citizens can’t tell whether unpopular policies originate with state or federal officials. That confusion undermines democratic governance.

This rule doesn’t apply when Congress applies the same rules to states and private companies. If the DOJ can argue that its demands apply generally to anyone maintaining election records—not to states specifically—it might escape the constraint.

Whether that argument works depends on whether courts view bulk data demands as special treatment of states (impermissible) or application of generally applicable federal requirements (permissible). That distinction will likely determine whether Minnesota’s refusal stands on solid constitutional ground.

Federal Funding as Coercive Pressure

Another constitutional limit might constrain Bondi’s demands: a rule against using financial pressure to force compliance.

Congress has broad authority to spend federal money and attach conditions to those funds. States can accept the conditions and take the money, or reject both. The constitutional line gets crossed when the financial pressure becomes so severe that states have no realistic choice but to comply.

The Supreme Court established this principle in 2012 when it reviewed the Affordable Care Act’s expansion of health coverage for low-income Americans. A seven-justice majority agreed that some level of coercion existed. Chief Justice John Roberts explained that this was fundamentally different from earlier cases where Congress offered states money contingent on adopting a minimum drinking age, with threatened losses representing less than half of one percent of state budgets.

If the DOJ is implicitly threatening to withhold federal funding for health coverage or food assistance—programs through which the federal government provides billions of dollars annually to Minnesota—in exchange for data access, that could constitute unconstitutional coercion.

Whether the letter’s reference to federal immigration enforcement activities and state compliance constitutes a hidden threat to cut off federal money depends partly on what evidence emerges about what federal officials said to state officials, and whether any explicit threats were made.

Voter Registration Data: Public Records vs. Bulk Transfer

The DOJ has claimed that “voter rolls are typically public records,” implying that demands for Minnesota’s complete file are merely requests for information already publicly available. This framing obscures critical legal distinctions.

The National Voter Registration Act of 1993 requires states to maintain records and make them available for public inspection. “Available for public inspection” means something specific in statutory language. A 2024 First Circuit decision clarified that Maine’s file must be disclosed for public inspection under the NVRA, but the court also affirmed that Maine could redact “especially private information like Social Security numbers” and full birthdates.

Another federal court held that the NVRA permits only in-person inspection or physical copying—not necessarily electronic bulk transfer of data. Minnesota residents, journalists, and election monitors can presumably visit the Secretary of State’s office and inspect files. The federal government demanding that Minnesota electronically transfer millions of files including Social Security numbers, driver’s license numbers, and dates of birth is an entirely different proposition.

The DOJ appears to be relying instead on the Civil Rights Act of 1960, which authorizes the Attorney General to request records “relating to any application, registration, payment of poll tax, or other act requisite to voting.” The statute appears broad on its face, but it includes an important limitation: the DOJ must explain why it needs the data and what it will do with it.

State officials and election law experts have questioned whether the DOJ has satisfied this requirement. The department’s stated purpose—ensuring state compliance with list maintenance obligations—doesn’t logically require access to bulk files. One snapshot of rolls won’t show whether a state is properly maintaining its list over time. Checking maintenance procedures would give much better evidence.

The state can argue that no statute unambiguously authorizes the DOJ to demand bulk electronic transfer of sensitive personal identifiers from databases.

Welfare Data: Stated Purposes vs. Actual Use

Bondi’s letter requested that Minnesota share all health coverage and food assistance program files with the federal government, framing the request as necessary to investigate welfare fraud. The real-world context suggests otherwise.

Federal law strictly limits how agencies can use and share data from benefit programs, precisely because Congress recognized that immigrants and families with both citizens and undocumented immigrants might forgo necessary health care and nutrition assistance if they fear the data will be used for immigration enforcement.

The statute governing food assistance data sharing explicitly restricts USDA’s access to and use of household data. Federal law similarly restricts how health coverage data can be shared. The health coverage context involves different federal privacy protections under Medicaid regulations that restrict how states can use and share beneficiary data.

If the administration intends to use food assistance and health coverage data for immigration enforcement purposes, federal statutes and regulations may prohibit such use without specific authorization by law.

The Privacy Act of 1974 restricts federal agencies’ access to files maintained by other agencies, with limited exceptions. When HHS or USDA shares data with the Department of Homeland Security for immigration enforcement, the Privacy Act requires procedures that require notice and public comment.

Minnesota’s legal position on welfare data is stronger than on registration data. The state can argue that federal law prohibits bulk sharing of health coverage and food assistance files with DHS for immigration enforcement purposes without appropriate Privacy Act procedures that require notice and public comment. The state can refuse the demand on statutory grounds, citing the restrictions on data use embedded in the federal statutes that govern these programs.

Minnesota’s Available Options

Minnesota has several options, each with different legal and political consequences.

First, the state can simply refuse compliance. This establishes the factual record that the state has refused a federal demand and can be used to support subsequent legal arguments.

Second, Minnesota can file a lawsuit asking a court to declare that the demands are illegal. Nebraska citizens and advocacy organizations filed suit in Nebraska state court to prevent the Secretary of State from transferring data to the federal government, arguing that Nebraska law prohibits disclosure of birthdates, driver’s license information, and Social Security numbers to third parties, including the federal government. Minnesota could file similar litigation in state or federal court, seeking declarations that state privacy law prevents the disclosure and that any attempt to compel such disclosure would violate constitutional protections and federal constitutional limits on coercion.

Third, Minnesota can work with other states to present a unified front. The Brennan Center found that the DOJ demanded data from at least twenty-seven states, and most have refused to provide unredacted copies of their files. When multiple states face similar federal demands and coordinate their legal responses, they generate significant litigation risk for the federal government.

Fourth, the Attorney General can formally advise state officials that compliance with the federal demands would violate state law and expose state employees to potential liability. This legal opinion, if issued formally, protects state officials from liability if they refuse.

Fifth, if the DOJ attempts to enforce its demands through coercive mechanisms—withholding federal funding, threatening criminal prosecution of state officials, or filing litigation—Minnesota can mount a full constitutional defense. The health coverage coercion rule lets Minnesota argue that any attempt to link federal funding or law enforcement operations to data sharing violates the anti-coercion doctrine.

How Other States Have Responded

Minnesota isn’t the first state to resist federal demands for sensitive information. When the Trump administration attempted to implement the Deferred Action for Parents of Americans program in 2014, a coalition of twenty-seven states, led by Texas, challenged the program in federal court. The states argued that the program would impose costs on them through increased demand for state services and that it exceeded the President’s authority. The Fifth Circuit Court of Appeals agreed.

Similarly, when the Obama administration attempted to implement the “Waters of the United States” rule under the Clean Water Act, a coalition of thirty-one states challenged the regulation. The Sixth Circuit agreed the government went beyond what the law allowed, stopping the rule from going into effect anywhere in the country.

When states organize coordinated legal challenges, they frequently prevail, particularly when they argue that federal agencies have exceeded their statutory or constitutional authority.

In the context of registration data specifically, federal judges have already begun ruling against DOJ. In January 2026, U.S. District Judge David O. Carter in California dismissed the DOJ’s lawsuit against California, holding that the DOJ’s claims were insufficient under federal election law and that its demands violated privacy laws. Judge Carter wrote that “the Department of Justice seeks to use civil rights legislation which was enacted for an entirely different purpose to amass and retain a large amount of confidential data” and that “this effort goes far beyond what Congress intended when it passed the underlying legislation.”

A judge in Oregon indicated from the bench that he would rule similarly against the DOJ. A judge in Georgia dismissed the DOJ’s suit on jurisdictional grounds but expressed skepticism about the federal government’s legal theory.

Multiple federal judges have independently reached conclusions that align with Minnesota’s legal position. At least eleven states have provided data to federal authorities, though many provided only publicly available information rather than the full unredacted files the DOJ requested.

Likely Litigation Path

If Minnesota stands firm and the DOJ attempts to enforce its demands through litigation, the most probable scenario is that the DOJ would file a civil enforcement action in federal district court in Minnesota, trying to force the state to comply by threatening to punish it for defying the court. The DOJ would argue it’s enforcing the Civil Rights Act of 1960, saying that the state is violating federal voting rights law by preventing federal investigation of potential voting irregularities.

Minnesota would mount a defense arguing that no statute clearly authorizes such demands, that constitutional limits on federal power prevent such demands, and that applying coercive pressure to obtain such data violates the anti-coercion doctrine.

A federal judge would have to answer several new legal questions: Does the Civil Rights Act allow the government to demand all this data including Social Security numbers and driver’s license information? If the law is unclear, should courts side with federal power or state power? Does the Privacy Act restrict federal agency access to sensitive information? Has the DOJ explained why it needs this data and what it will do with it?

Based on recent judicial decisions rejecting the DOJ’s demands, a Minnesota federal judge would likely find at least some of these questions favor the state. Judge Carter’s California decision explains step-by-step why the DOJ’s statutory interpretation is questionable and why privacy laws constrain federal authority.

The litigation would almost certainly not resolve all questions finally. The DOJ would likely appeal. The question might eventually reach the Eighth Circuit Court of Appeals, which covers Minnesota. An appellate court decision would establish binding precedent for all states within that circuit, making it a high-stakes case for the broader question of federal authority over state data.

The immediate legal outcome depends not only on the law but on how much pressure the DOJ applies and what happens as a result. If the DOJ aggressively pursues enforcement, threatening criminal prosecution of state officials or attempting to withhold federal funding, the political pressure will intensify. If other states continue to resist and courts continue to rule against the DOJ, other states may feel encouraged to keep refusing.

The Welfare Data Argument

The state’s legal position may be strongest not on registration data—where the statutory authority is genuinely ambiguous—but on welfare data.

Federal statute explicitly restricts how USDA can use food assistance data. The Food and Nutrition Act of 2008 and implementing regulations strictly limit what agencies can do with household data, especially to protect people’s privacy. When USDA demanded that states provide five years of complete personal information like names and Social Security numbers on all applicants and participants, nonprofits, state attorneys general, and privacy groups challenged the demand in federal court. A federal judge in California issued a court order temporarily stopping the demand, showing serious doubts about whether such broad demands are legal.

Health coverage data is subject to strict federal privacy protections. Federal Medicaid regulations restrict how states can use and share beneficiary data, and any sharing with immigration authorities requires specific compliance with Privacy Act procedures that require notice and public comment.

Minnesota can argue credibly that complying with Bondi’s demand for complete health coverage and food assistance files would force the state to violate federal law. If the state provides the data knowing that the federal government will use it for immigration enforcement, and federal law restricts such use, the state could be breaking federal privacy law. This argument relies on clear federal law, not unclear statutes.

National Implications

Minnesota’s decision will affect other states. Multiple states are facing similar demands for registration data and welfare files. The strategies Minnesota adopts, the legal arguments it advances, and the judicial outcomes it achieves will influence how other states respond and how courts throughout the country approach federal-state data conflicts.

If Minnesota successfully resists the demands through litigation or political pressure, it will establish precedent suggesting that states have meaningful authority to decline federal data requests when those requests lack clear statutory authorization or threaten to violate state and federal privacy laws.

Conversely, if the DOJ successfully compels Minnesota to provide the data through litigation or coercive pressure, the federal government could collect all state data for its own use, giving the federal government much more power over states.

The outcome matters for privacy protection broadly. Registration data, health coverage files, and food assistance files contain some of the most sensitive personal information citizens entrust to government. If the federal government successfully compels states to surrender complete, unredacted databases containing Social Security numbers, driver’s license numbers, and health or welfare information, an important privacy protection is eliminated.

Millions of citizens have assumed that their state-held data is protected by state privacy law and cannot be unilaterally transferred to federal authorities without judicial process. A federal victory would show citizens that their state data isn’t protected.

The Constitutional Question

The confrontation between Attorney General Bondi and Minnesota represents a serious constitutional question about who gets to make decisions—the federal government or states.

The Constitution is fairly clear about what the federal government can’t directly order states to do: Congress cannot order states to pass laws or force state officials to enforce federal law. It’s much less clear whether the federal government can demand that states hand over sensitive personal information to federal authorities, particularly when such transfer appears designed to serve federal purposes unrelated to state regulatory responsibilities.

Minnesota’s refusal is based on real legal arguments about what the Constitution and laws allow. The state can argue that no statute clearly authorizes the DOJ to demand bulk transfer of sensitive data. It can argue that such a demand, if enforced through coercive pressure, would violate the anti-coercion doctrine established in the health coverage expansion case. It can argue that attempting to obtain welfare data for immigration enforcement violates federal privacy statutes that restrict data use.

Whether courts agree depends on how seriously they take states’ rights. The recent decisions by federal judges in California, Oregon, and Georgia rejecting the DOJ’s demands suggest that courts are taking such principles seriously. The question has not yet reached the Supreme Court, and the Court’s rulings on state power have been inconsistent.

For Minnesota, for other states facing similar federal demands, and for citizens concerned about government power and privacy protection, the next months will be consequential. The legal battle over rolls and welfare data is fundamentally about whether the federal government can leverage its superior resources and coercive power to consolidate information about citizens that states have traditionally protected.

The constitutional limits on federal coercion are real, though they have limits themselves—particularly when federal officials prove willing to test those boundaries and press their legal arguments vigorously through litigation. The outcome will likely determine not only Minnesota’s immediate fate but how the federal government and states will interact in the future, when sensitive personal information is both valuable to government and risky for citizens’ privacy.

Our articles make government information more accessible. Please consult a qualified professional for financial, legal, or health advice specific to your circumstances.