Maryland Voter Data Claims Ledger: Federal Court Shut Down DOJ’s Demand For The Full File, But The Public Still Needs The Receipts

BadPD source-check, June 27, 2026; source dates June 18 through June 23, 2026: This is the Maryland election story that is turning into claim soup online. The actual record is cleaner than the noise. The U.S. Department of Justice sued Maryland election administrator Jared DeMarinis seeking Maryland's statewide voter registration list. The court record says DOJ wanted the computerized statewide voter registration list with all fields, including full names, dates of birth, residential addresses, and either state driver's license numbers or the last four digits of Social Security numbers. U.S. District Judge Stephanie A. Gallagher denied DOJ's motion to compel and granted the defendants' motions to dismiss.

That does not mean voter rolls are fake. It does not mean Maryland has no duty to maintain voter lists. It does not mean every concern about election administration is automatically disinformation. It means the federal government failed in this case to show that the specific statutes it invoked gave it authority to force Maryland to turn over the unredacted statewide voter file demanded in this lawsuit. That is the difference between a records-based public accountability story and a social-media shouting match.

BadPD is publishing this as a claims-vs-records ledger because the political frame around voter files tends to collapse into two lazy extremes. One side wants to call every privacy objection a coverup. Another side wants to treat every election-integrity question as bad faith. The court did neither. The opinion looked at what DOJ asked for, what statutes DOJ invoked, what Maryland refused to provide, and whether the demand fit the law. The answer in Maryland was no.

What The Court Record Says DOJ Asked For

The memorandum opinion in United States v. DeMarinis states that DOJ brought one of thirty similar lawsuits around the country seeking statewide voter registration lists. In the Maryland case, the July 14, 2025 letter asked for Maryland's computerized statewide voter registration list and requested all fields contained in the list. Maryland's election administrator responded by directing DOJ to publicly available portions of the list and later asked DOJ to identify the purpose of the request.

The August 18 letter sharpened the demand. According to the court opinion, DOJ cited the National Voter Registration Act, the Help America Vote Act, and Title III of the Civil Rights Act of 1960, and said the purpose was to ascertain Maryland's compliance with list-maintenance requirements. The opinion says DOJ wanted full name, date of birth, residential address, and a state driver's license number or the last four digits of a Social Security number. Those fields are not the same as the public-facing portions of a voter file. They are sensitive data points that can create identity-theft, intimidation, doxxing, targeting, and improper data-sharing risks.

The court did not say Maryland could ignore federal election law. The court said the Civil Rights Act claim DOJ actually filed did not give it the power it claimed. The opinion says DOJ filed a single claim under the Civil Rights Act and then sought a compelled production order immediately after filing. The judge denied that motion and dismissed the case.

AP and PBS both reported the Maryland dismissal as another loss in the broader DOJ voter-data campaign. AP reported that DOJ has sued in thirty states and the District of Columbia, and that Maryland was the ninth state where judges had rejected similar attempts at the time of AP's June 23 story. AP also reported that some states had provided or promised to provide voter registration lists, naming Alaska, Arkansas, Indiana, Louisiana, Mississippi, Nebraska, Ohio, Oklahoma, South Carolina, South Dakota, Tennessee, Texas, and Wyoming based on Brennan Center and AP reporting. That means Maryland is part of a national records fight, not an isolated local dustup.

What Was Confirmed, What Was Claimed, And What Still Needs Receipts

Confirmed by the court opinion: DOJ sued Jared DeMarinis in his official capacity as Maryland's State Administrator of Elections. DOJ sought Maryland's statewide voter registration list. The request included all fields in the computerized list. The court denied DOJ's motion to compel. The court granted the defendants' motions to dismiss. The court identified the case as one of thirty similar lawsuits.

Confirmed by AP/PBS reporting: The case was dismissed by U.S. District Judge Stephanie Gallagher. The demand was part of a broader Trump administration effort to obtain state-level voter data. The detailed data sought included dates of birth, addresses, driver's license numbers, and partial Social Security numbers. DOJ had lost similar cases in multiple states by the time of publication. DOJ officials have said the data was sought to check compliance with federal election laws.

Confirmed by ACLU and Elias Law releases, treated as advocacy-source receipts: The ACLU, ACLU of Maryland, Common Cause, Out for Justice, and individual voters intervened or participated in defense of voter privacy. Elias Law Group says it represented the Maryland/DC Alliance for Retired Americans. These groups frame the ruling as protection against federal overreach and an attempted national voter database. That is their advocacy frame, not a neutral court finding by itself, but the dismissal and the data fields at issue are court-record facts.

Claim requiring care: Some online chatter turns this into proof that Maryland had something to hide. The source record reviewed here does not establish that. Maryland directed DOJ to publicly available portions of the list and disputed DOJ's authority to obtain the unredacted confidential fields. A privacy objection is not automatically evidence of voter fraud.

Opposite claim requiring care: Some chatter turns the dismissal into proof that voter-roll maintenance questions are illegitimate. The opinion does not say that either. States still have federal and state obligations around voter registration, list maintenance, eligibility, transparency, and equal access. The ruling is about this demand, this lawsuit, and the statutes DOJ used.

Pending and missing receipts: DOJ's appeal decision, if any; the full docket beyond the opinion; any DOJ internal guidance that explains why the same theory was filed in so many states; state-by-state data-sharing agreements for states that did turn over files; privacy impact assessments; and any DHS/SAVE data-matching policy documents tied to voter-roll use.

The Civil Rights Act Argument Did Not Carry The Day

The court's reasoning matters because this was not just a political press-release fight. DOJ pointed to legal authority. The judge read the cited statutes. The court said the unredacted statewide voter registration file was not the kind of record or paper a state must produce to the United States under the Civil Rights Act theory DOJ advanced. AP and PBS highlighted the court's rejection of DOJ's attempt to lean on an opinion written by DOJ's own Office of Legal Counsel. The court was not required to accept an agency's self-serving interpretation simply because the same federal government entity generated it.

That is an accountability point on both sides. If the federal government wants sensitive voter data, the authority should be clear, narrow, and externally reviewable. It should not be built on a broad reading that courts around the country are rejecting. If a state refuses to hand over a full file, the state should still be able to show what public portions are available, what privacy restrictions apply, and how its own list-maintenance process works. Secrecy cannot be the answer to federal overreach. Records have to answer records.

This is where BadPD's political lane is different from a campaign meme. The question is not whether readers like DOJ, Maryland election officials, Trump, Democrats, Republicans, ACLU, Elias, or AP. The question is whether the receipts show authority, limits, privacy protection, and public accountability. In this case the court record says the compelled unredacted file demand failed.

The Privacy Problem Is Real Even If The Politics Are Loud

A voter file with names, residential addresses, birth dates, driver's license numbers, and partial Social Security numbers is not just a spreadsheet. It is a high-value data set. If such a file is copied across agencies, vendors, political offices, law-enforcement interfaces, or poorly secured storage, the risk does not stop when the lawsuit ends. It follows voters.

That risk is not hypothetical. Driver's license numbers and partial Social Security numbers are identity-verification fields. Residential addresses can endanger domestic-violence survivors, judges, prosecutors, witnesses, officers, public employees, activists, and ordinary people who simply do not want their household information moved into an unclear federal data environment. Dates of birth can be matched with other leaked data to build richer identity profiles.

The federal government can have legitimate election-law enforcement needs and still be required to use a lawful, proportionate, privacy-respecting process. Maryland can have legitimate privacy concerns and still be required to maintain accurate rolls and produce lawful records. Those propositions are not contradictory. They are the baseline for a constitutional government that is supposed to handle sensitive public records without turning every voter into a data target.

The DHS/SAVE Citizenship-Matching Lane Needs Its Own Records

AP reported that in a Rhode Island case, a DOJ attorney acknowledged the department was seeking unredacted voter-roll information so it could be shared with the Department of Homeland Security to check citizenship status. AP also reported that a federal judge found a DHS citizenship-checking program violated privacy laws and was wrongly identifying eligible voters as noncitizens, and ruled the system could no longer be used.

BadPD is not merging the Rhode Island/SAVE ruling into the Maryland holding. They are separate cases. But the policy connection matters because it explains why an unredacted state voter file is not a routine paperwork ask. If voter files are being used or proposed for citizenship matching, the public needs the matching logic, error rates, appeal rights, notice process, data-retention policy, agency-sharing chain, and correction process.

A false noncitizen flag can hurt an eligible voter. A sloppy data match can chill voting. A secret data-sharing chain can undermine trust even when a state does everything else correctly. If DOJ wants broad voter data to check compliance, it should be able to produce a clean public record showing legal authority, privacy controls, audit logs, and error correction. If it cannot, courts are right to ask why the sensitive fields are being demanded.

What Maryland Still Owes The Public

The dismissal should not be a permission slip for Maryland to avoid ordinary transparency. Maryland election officials should make it easy for residents to find public voter-file rules, list-maintenance schedules, duplicate-check procedures, death-record matching procedures, address-confirmation processes, inactive voter rules, data-security standards, and complaint channels. If Maryland's position is that the full unredacted file cannot be handed over to DOJ under this theory, Maryland should still explain the public-record boundaries in plain English.

The state should also explain what fields are public, what fields are confidential, who can access each category, whether vendors touch the data, what breach-notification rules apply, and how a voter can protect or update their record. That is how a privacy victory becomes public-service work instead of a partisan victory lap.

For BadPD readers, the practical takeaway is simple. Do not repeat claims that Maryland was ordered to turn over everything. It was not. Do not repeat claims that the court found voter rolls do not matter. It did not. Do not repeat claims that every data request is a coup or every refusal is fraud. The record is narrower and stronger: the court rejected DOJ's demand for Maryland's unredacted statewide voter data under the legal theory DOJ used.

What To Watch Next

The next receipts are appeal notices, similar-state rulings, any new DOJ letters, state data-sharing acknowledgments, and DHS/SAVE policy changes. Watch whether DOJ narrows future demands, whether Congress tries to create clearer authority, whether states that provided data disclose what they provided, and whether voters receive notice that sensitive fields moved outside state custody.

BadPD should also track whether Maryland voters or advocacy groups seek public records about outside access to Maryland voter data. The court case tells us DOJ could not compel the full file in this lawsuit. It does not answer every access question. State vendors, interstate systems, law-enforcement agencies, campaign data brokers, and public-record requesters can all create separate privacy lanes.

This article is not legal advice. Maryland voters should use official Maryland Board of Elections resources for registration status, privacy questions, corrections, and deadlines. But as an accountability record, the current source trail is strong enough for one conclusion: the weird Maryland claims are overblown unless they stay attached to the court file. The court file says DOJ asked for sensitive voter data, Maryland resisted, intervenors joined, and the federal court dismissed DOJ's case.

Records Checklist For A Real Maryland Follow-Up

The voter-data story needs a public-record checklist because otherwise people will keep arguing from slogans. The first receipt is the court opinion. The second receipt should be the DOJ demand letter package. The third receipt should be Maryland's response letters. The fourth receipt should be the public voter-file access rules Maryland already uses. The fifth receipt should be any federal data-handling policy describing where requested files would be stored, who would access them, how long they would be retained, and whether they would be matched against immigration, criminal, motor-vehicle, or benefit databases.

Maryland officials should post or clearly link the public portions of the voter-list process in plain language. Residents should be able to answer basic questions without hiring counsel: what data is public, what data is confidential, what can campaigns buy, what can researchers inspect, what can agencies receive, what can law enforcement request, what happens after a breach, and what a voter should do if a record is wrong. If officials want the public to reject bad claims, they need to make the correct record easy to find.

DOJ should be held to the same standard. If it says state voter files are needed for compliance, it should identify the legal authority, the narrow purpose, the exact fields needed, the minimum data necessary, the privacy safeguards, and the correction process for bad matches. A government agency should not be able to ask for sensitive files first and explain the controls later. That order is backwards.

The advocacy groups also need to keep receipts attached. Strong privacy language is useful only when the underlying court record stays visible. If the claim is federal overreach, attach the demand letter and order. If the claim is voter intimidation, show the mechanism. If the claim is risk of an unlawful national database, identify the data flow and agency custody. Public-interest litigation is stronger when it gives readers documents, not just statements.

Why BadPD Is Publishing This In A Police-And-Government Accountability Site

Some readers will ask why a voter-file lawsuit belongs on a police-accountability website. The answer is that public power is public power. BadPD covers police, courts, government officials, public records, civil-rights violations, and official data systems because they share one risk: the state can turn records into consequences. A police report can shape a criminal case. A voter file can shape who gets investigated, challenged, purged, contacted, or exposed. A bad database is not less dangerous because it lives in an election office instead of a squad car.

That does not mean Maryland's election file was misused in this case. It means the demand for sensitive data has to be treated with the same seriousness as any other government demand for personal records. When the government wants people's data, BadPD asks three questions: what is the legal authority, what is the public purpose, and what prevents abuse? The Maryland court answered the first question against DOJ in this case. The other two questions still deserve public records.

The useful post is not "DOJ bad" or "Maryland hiding." The useful post is the ledger: demand, refusal, lawsuit, intervention, motion to compel, dismissal, privacy fields, appeal watch, state transparency owed, and next public documents to obtain. That structure lets readers test claims instead of joining another online food fight.

Send Receipts

Have a source document, docket link, bodycam release, official statement, public-record response, or firsthand video that fits BadPD police, government, court, civil-rights, recall, or public-safety focus? Use the BadPD contact form and include the date, location, source, and how the record was obtained. BadPD does not publish rumors as facts; send receipts.

Source Trail

• U.S. District Court memorandum opinion, United States v. DeMarinis (Filed June 18, 2026; accessed June 27, 2026) – Primary court opinion denying DOJ motion to compel and granting motions to dismiss in Maryland voter-list case.
• Associated Press report on Maryland DOJ voter-data dismissal (Published June 23, 2026; accessed June 27, 2026) – Independent report on dismissal, national context, data fields sought, and similar state cases.
• PBS NewsHour AP republish (Published June 23, 2026; accessed June 27, 2026) – Accessible AP text cross-check on the Maryland dismissal and broader DOJ voter-data campaign.
• ACLU release: Federal court rejects DOJ attempt to obtain Maryland voter data (June 22, 2026; accessed June 27, 2026) – Advocacy-source receipt identifying intervenors and privacy arguments; used for party/status context, not as neutral finding.
• ACLU of Maryland release (June 22, 2026; accessed June 27, 2026) – Maryland affiliate release with local privacy framing and case context.
• Elias Law Group release (June 22, 2026; accessed June 27, 2026) – Counsel-side receipt for Maryland/DC Alliance for Retired Americans intervention and order framing.

Featured image is symbolic editorial artwork created for BadPD. It is not a depiction of the source event, people, victims, suspects, or scene.