When agencies repurpose tax data for immigration enforcement, the question that decides the case is not rhetoric about privacy or border security; it is whether the Internal Revenue Code’s confidentiality rule and its narrow exceptions actually authorize the specific disclosures the government made.
The Short Version
- The D.C. Circuit affirmed denial of a preliminary injunction against an IRS–ICE data-sharing agreement, finding challengers were unlikely to prevail on their core confidentiality theory at this stage.
- The fight turns on Section 6103 of the Internal Revenue Code: what counts as protected “return information,” and which exceptions allow disclosure for non-tax criminal investigations.
- The memorandum of understanding (MOU) lets IRS share certain identifiers—primarily names and last-known addresses—with ICE for criminal immigration enforcement tied to defined requests.
- Advocacy groups and members of Congress argue the arrangement violates Section 6103 and risks bulk misuse; the government says the statute expressly permits these limited disclosures when conditions are met.
What the court actually decided
On appeal from the denial of a preliminary injunction, the D.C. Circuit concluded plaintiffs were unlikely to succeed on the merits of their principal claim that the IRS–ICE arrangement violated tax confidentiality, and allowed the IRS to continue operating under the MOU while litigation proceeds. Appellate summaries indicate the panel’s reasoning hinged on Section 6103’s text: while “return information” is broadly confidential, Congress carved out targeted exceptions for non-tax criminal investigations and, as relevant here, permitted disclosure of certain identifiers—such as a last-known address—when those identifiers are not themselves taxpayer “return information,” or when a qualifying law-enforcement request is properly made. This was not a final merits ruling, but in federal practice a loss on likelihood of success signals the court sees the statutory footing for the program as comparatively strong at this juncture.
The posture matters. Preliminary injunction standards require a showing of likely success and irreparable harm to halt a program pending full adjudication. By affirming the denial, the D.C. Circuit preserved the status quo under the MOU; it did not announce a sweeping new doctrine. Still, in regulatory disputes like this one, how an appellate court reads the statute on interim relief often foreshadows where a final merits opinion may land if the same record and arguments persist.
The legal architecture: Section 6103’s rule–exception design
Section 6103 codifies a fundamental bargain: tax returns and “return information” are confidential, full stop—unless a specific, enumerated exception permits disclosure. Congress drafted the provision to prevent tax data from becoming a backdoor intelligence feed for unrelated programs; over decades, it has refined exceptions to balance privacy against legitimate public-safety needs. One such exception, Section 6103(i), allows disclosures to federal law-enforcement officers “personally and directly engaged” in non-tax criminal investigations, subject to strict process controls, scope limits, and use restrictions. In practice, those limits function like guardrails: they constrain what fields may be shared, with whom, and for what use, and they demand auditable compliance.
The present dispute sits precisely at that seam. The IRS–ICE MOU, executed in April 2025, frames the exchange as a tool to verify identities and locate individuals implicated in defined immigration-related criminal investigations, using narrow fields—principally names and last-known addresses—requested through documented channels that, the government contends, satisfy Section 6103(i)(2). Plaintiffs and amici respond that the program crosses the line into bulk or categorical sharing that Section 6103’s structure forbids, and that even “simple” identifiers can qualify as protected return information when derived from tax files and linked to a known taxpayer.
The memorandum of understanding: what it authorizes, and why
According to Congressional Research Service summaries and contemporary reporting, the MOU allows ICE to submit requests to IRS for limited identifiers to aid criminal immigration enforcement, including against targets subject to final removal orders or those under active investigation for specific statutory violations. The government grounds this in Section 6103’s non-tax criminal investigation exception and in the statute’s differentiation between return information and certain basic identifiers when not tied to return content. The operational logic is straightforward: a law-enforcement agent cannot execute a warrant or serve a court order if she cannot reliably find the person; last-known addresses, validated against IRS data hygiene, can be the most accurate locator available.
The challengers’ core claim is equally textual: they argue the confidentiality rule is the default, exceptions are to be narrowly construed, and the MOU’s design invites or effectuates disclosures beyond what Section 6103 authorizes. They emphasize statutory phrases like “personally and directly engaged” and “solely for” the investigation to argue that large-scale or anticipatory feeds to a broad set of officers are incompatible with the law’s precision and purpose. On preliminary review, the D.C. Circuit read the statute as more accommodating to the MOU’s design than plaintiffs urged, at least as to names and addresses within the exception’s constraints.
Advocacy, oversight, and the allegation of improper disclosures
Outside the courtroom, civil-society organizations and a coalition of 115 members of Congress filed amicus briefs criticizing the arrangement as unlawful bulk sharing that undermines taxpayer trust in the filing system—especially among mixed-status households that still file returns or seek Individual Taxpayer Identification Numbers. They stress that Section 6103’s safeguards exist to ensure tax administration is not weaponized for unrelated enforcement aims, and they warn that dialing those limits back could chill compliance and degrade the voluntary system that funds the government. In February 2026, Democracy Forward highlighted a filing asserting the IRS acknowledged an improper disclosure incident, which challengers say heightens the need for discovery and tighter judicial supervision of the program’s mechanics.
Those arguments have policy force, but the litigation’s center of gravity remains statutory. Courts will parse whether the specific fields transmitted, the request-by-request process, the number and roles of recipients, and the documented use limits track Section 6103’s text. If the program adheres to the exception—targeted requests, named investigations, officers “personally and directly” involved, and use “solely for” those cases—it tends to stand; if it strays into generalized or prophylactic data flows, it tends to fall. The D.C. Circuit’s interim ruling suggests the record presently supports the former characterization, at least in broad strokes.
Why this matters going forward
Section 6103 disputes recur whenever an agency sees operational value in tax-derived data that another statute did not originally contemplate. The stakes are systemic: America’s tax system relies on voluntary compliance underwritten by strong confidentiality; immigration enforcement, by contrast, relies on accurate identification and location of individuals subject to criminal process. Getting the balance wrong either chills lawful filing or blunts legitimate policing. The appellate court’s refusal to halt the IRS–ICE program signals that, so long as the government uses the exception architecture as designed—documented requests, narrow fields, direct investigative need, and auditable use limits—courts are prepared to let these targeted disclosures proceed while merits litigation unfolds.
Expect the next phase to turn on evidence, not slogans: the exact data elements transmitted, how often, to whom within ICE, under what case numbers, with what retention and minimization rules, and how IRS audits compliance. Plaintiffs will press any deviation as proof the program overreaches Section 6103; the government will point to the statute’s text and the MOU’s controls as adequate guardrails. For readers tracking the boundary between privacy law and public safety, that is the enduring lesson: the law already contains the balance; the outcome depends on whether practice hews to it.
Sources:
thegatewaypundit.com, congress.gov, migrantusa.com, unidosus.org, law360.com, democracyforward.org