Fourth Circuit Finds Journalist LinkedIn Records Order Overbroad

The U.S. Court of Appeals for the Fourth Circuit held on November 10, 2026 that a federal judge may not approve a government demand for journalists' LinkedIn records without measuring how far it overreaches. The panel found both the records order and the accompanying gag order substantially overbroad and remanded.

Information last verified on November 12, 2026. This is a developing story; we update it as the record changes.

Status: Decided and published. The Fourth Circuit reversed in part on November 10, 2026 and remanded for the district court to draw both orders more narrowly; it expressly declined to quash them, and it affirmed the denial of LinkedIn's request for the government's ex parte materials. As of our November 12, 2026 verification we found no district court order on remand and no amended opinion or rehearing order, though we could not read the appellate docket directly.

Where this applies: This decision binds federal district courts in the Fourth Circuit, which covers Maryland, Virginia, West Virginia, North Carolina and South Carolina. Everywhere else it is persuasive authority only. It governs orders under the federal Stored Communications Act for stored account records, and the nondisclosure orders that accompany them. It does not address live wiretapping, demands issued under state law, or civil subpoenas, and it decides nothing about whether anyone committed a crime.

What Happened

The appeal, In re: Application of the United States of America for an Order Pursuant to 18 U.S.C. Section 2703(d), No. 26-4303, grew out of a leak investigation. A news organization that the opinion calls the "News Outlet" published an article "purporting to describe a top-secret United States military operation in a foreign country," and the government went looking for the source. The opinion deliberately withholds identifying detail, explaining that it "must, by necessity, speak generally and omit extraneous detail."

The government served LinkedIn with two orders obtained in the Eastern District of Virginia at Newport News, before District Judge Elizabeth W. Hanes (No. 4:25-dm-00001-EWH-DEM-1). The first, the Disclosure Order, issued under 18 U.S.C. § 2703(d), a provision of the Stored Communications Act. It "ordered LinkedIn to assemble and divulge the targeted journalists' metadata records from an eighteen-month period." Slip op. at 5. On LinkedIn, both connection requests and private messages "create metadata that record the sender, recipient, date, and time."

Scale is what drove the result. Across those eighteen months the targeted journalists "collectively published nearly 1,000 different articles on a variety of topics, less than five percent of which appear to have anything to do with the subject at issue here." Slip op. at 5. The records sought would identify "every user (and, necessarily, every confidential source) the targeted journalists corresponded with on LinkedIn concerning any of those stories."

The second order, the Secrecy Order, issued under 18 U.S.C. § 2705(b). It barred LinkedIn for one year from revealing the existence of the Disclosure Order, the Secrecy Order, or the government's application for either one. That bar ran not only to the journalists and the News Outlet but to "any other person" at all, "with the sole exception of legal counsel." Slip op. at 21.

LinkedIn moved to narrow both orders. On the gag it asked for a single carve-out: permission to tell one lawyer for the News Outlet, an attorney the government had already vetted, so that lawyer could help identify ways to trim the records demand. LinkedIn also asked for the ex parte materials the government had filed to obtain the orders.

A magistrate judge found that LinkedIn had standing but sided with the government, reading the statute to allow a provider to object only on grounds of "logistical or practical burden." The district court adopted that recommendation in full, concluding that LinkedIn "does not fall within one of the limited grounds in which a responding party may move to quash an order that is entered pursuant to § 2703(d)." Slip op. at 7.

The Fourth Circuit rejected that framing. Writing for a unanimous panel, Judge Wilkinson, joined by Judges Wynn and Berner, held that overbreadth is a limit a district court must actually apply. There is no concurrence or dissent.

Plainly irrelevant or immaterial records encompassed in a § 2703(d) order constitute impermissible overbreadth. While some degree of overbreadth may be inevitable, the SCA and the Constitution require the district court to analyze the degree of overbreadth and trim the more far-fetched reaches of the government's records request.

Slip op. at 13.

Two moves made that enforceable. First, the panel located the duty in the statute's own words: § 2703(d) says an order "shall issue only if" the government makes its showing, and that obligation "is unqualified. There is no express exception for national security." Second, it held that overbreadth fits the statute's quash-or-modify ground, reasoning that "[a]s a logical matter, lack of relevance and materiality is itself an 'undue burden.'" Slip op. at 14. An order that should never have issued imposes a burden that is by definition undue.

The First Amendment did not supply a separate test. It reinforced the statutory one. "Rather than creating a distinct test, the First Amendment inquiry merges with and strengthens the tailoring requirements in 18 U.S.C. § 2703(d). The two are joined at the hip." Slip op. at 19. Where a demand reaches records bearing only a "remote and tenuous" relationship to the investigation, and especially where it "implicates confidential source relationship[s]," the district court "must conduct a balancing analysis," drawing on Justice Powell's concurrence in Branzburg v. Hayes, 408 U.S. 665, 710 (1972), as this circuit applied it in In re Grand Jury 87-3 Subpoena Duces Tecum, 955 F.2d 229, 232 (4th Cir. 1992). "Confidentiality of sources is the lifeblood of a free press," the court wrote. Slip op. at 17.

The panel was emphatic that the government's interest was real and weighty. "The government is entitled to discovery to the full extent permitted by law. It is entitled to a disclosure order. It is even entitled to a broad disclosure order. But it is not entitled to carte blanche." Slip op. at 11. The failure below was as much procedural as substantive: "It was error for the district court to forgo this analysis and offer blanket approval to the government's broad request." Slip op. at 14.

On the Disclosure Order the court concluded that "in its present form, it is substantially overbroad," and remanded. Slip op. at 19. It pointedly declined to go further: "We reject LinkedIn's request to quash the orders entirely. That goes much too far." Slip op. at 3.

On the Secrecy Order the court began from the premise that a § 2703(d) order "is presumptively public," slip op. at 20, and noted that both parties agreed the gag was a prior restraint, which Nebraska Press Ass'n v. Stuart, 427 U.S. 539, 559 (1976), calls "the most serious and least tolerable infringement on First Amendment rights." The weight of the government's interest, the panel held, "does not absolve the court of the need to engage with the substance of LinkedIn's proposed alternative." It then left the district court little room: "Unless the government's response to LinkedIn's proposal is more persuasive than anything the government has presented thus far, LinkedIn's narrow exception to the breadth of the Secrecy Order must be adopted." Slip op. at 23.

Part V went the government's way. Reviewing the refusal to give LinkedIn the government's ex parte filings for abuse of discretion, the panel wrote: "We discern no such abuse." Slip op. at 24. Turning over materials "the government believed would be limited to the court's eyes alone" was, in the panel's view, a different matter from relaxing the gag.

The opinion closes: "Serious security and speech claims are in tension in this case. There is space under law for both." Slip op. at 24. Amici supporting LinkedIn included the Reporters Committee for Freedom of the Press, the American Civil Liberties Union and the ACLU of Virginia, Apple, and Amazon, Google and Meta jointly.

What the Law Actually Says

A § 2703(d) order is a creature of the Stored Communications Act, the 1986 statute that governs when the government can reach records an online service holds about you rather than records you hold yourself. It is not a warrant.

Here is the issuance standard:

A court order for disclosure under subsection (b) or (c) may be issued by any court that is a court of competent jurisdiction and shall issue only if the governmental entity offers specific and articulable facts showing that there are reasonable grounds to believe that the contents of a wire or electronic communication, or the records or other information sought, are relevant and material to an ongoing criminal investigation.

That is the first sentence of 18 U.S.C. § 2703(d); the subsection goes on to bar such an order sought by a state authority where that state's law prohibits it, and then sets out the provider's quash-or-modify route quoted below. The Fourth Circuit has characterized the showing as a "reasonable suspicion" standard, citing its earlier decision in In re Application of the United States for an Order Pursuant to 18 U.S.C. Section 2703(d), 707 F.3d 283, 287 (4th Cir. 2013). Slip op. at 13.

What such an order can reach is defined in § 2703(c)(1): "a record or other information pertaining to a subscriber to or customer of such service (not including the contents of communications)." That is the metadata category, meaning who corresponded with whom, when, and on what account. Section 2703(d) also authorizes orders under subsection (b), which can reach communications content in defined circumstances; the order in this case sought metadata.

The same subsection carries the provision that explains why most people never learn any of this happened. Section 2703(c)(3) states: "A governmental entity receiving records or information under this subsection is not required to provide notice to a subscriber or customer."

The statute does give the provider a way to push back, and it is the clause the Fourth Circuit construed:

A court issuing an order pursuant to this section, on a motion made promptly by the service provider, may quash or modify such order, if the information or records requested are unusually voluminous in nature or compliance with such order otherwise would cause an undue burden on such provider.

LinkedIn never argued the records were "unusually voluminous." The entire fight was over "undue burden," which is why the panel's holding that an irrelevant records demand is itself an undue burden matters: it gives a provider a statutory foothold to argue scope rather than only logistics.

The gag order comes from a different section. Under 18 U.S.C. § 2705(b), the government may apply for an order commanding a provider, "for such period as the court deems appropriate, not to notify any other person of the existence of the warrant, subpoena, or court order." The court "shall enter such an order if it determines that there is reason to believe" that notification will result in one of five enumerated harms, which the statute lists as endangering the life or physical safety of an individual; flight from prosecution; destruction of or tampering with evidence; intimidation of potential witnesses; or otherwise seriously jeopardizing an investigation or unduly delaying a trial.

Note what § 2705(b) does not contain: a national security exception as such. The Fourth Circuit said exactly that, while adding that leak investigations "will frequently satisfy the statutory factors of § 2705," with subsection (b)(5) the clearest fit. Slip op. at 21.

This is also where the Stored Communications Act parts company with the wiretap rules people more often have in mind. Live interception of a communication as it happens runs through the Wiretap Act and its much higher threshold, while the SCA governs records already sitting on a provider's servers. Both halves live inside the 1986 privacy statute that still frames this whole area, and the thresholds differ sharply between them. For the wider federal picture, see our overview of how federal law treats recording, interception and stored communications.

What Happens Next

The case returns to Judge Hanes. On the Disclosure Order the panel directed the district court to consider four things: "(1) the government's need for the Disclosure Order, (2) the breadth of the records sought and whether any subdivisions might feasibly be drawn, (3) that the government cannot know precisely what is relevant at early stages of an investigation, and (4) any First Amendment and SCA standards implicated by the Disclosure Order." Slip op. at 20.

On the Secrecy Order, the government "should be given an opportunity to explain why LinkedIn's narrow disclosure would somehow compromise its investigation." Slip op. at 23. If it cannot do better than it has so far, the panel said LinkedIn's single-lawyer exception "must be adopted."

Neither order was quashed, and the opinion sets no deadline for the district court to act. We found no district court ruling on remand as of November 12, 2026.

The appellate side is not formally closed either. A party may seek panel rehearing or rehearing en banc within the window set by the Federal Rules of Appellate Procedure, and the mandate returning the case to the district court issues after that window runs. The official opinion posted at ca4.uscourts.gov is textually identical to the copy on CourtListener and carries no amendment notation.

We could not read the appellate docket directly. The Fourth Circuit's own list of opinions posted in the last 30 days carries a single entry for No. 26-4303, dated November 10, 2026 and recorded there as "Affirmed in part, reversed in part, and remanded," with no amended opinion beside it. A rehearing petition is not an opinion and would not appear on that list, and CourtListener refused anonymous docket and search queries, so treat the absence of a rehearing petition as unverified rather than confirmed.

The developments that would change this picture: an amended or withdrawn opinion, an order granting rehearing, a district court order on remand narrowing or declining to narrow either order, a petition for certiorari, or the expiration of the Secrecy Order's one-year term. The opinion does not say when that year began.

Analysis: Why This Matters

The following is analysis from the Recording Law Editorial Team.

The holding is about scope, not authority. Nothing here stops the government from using § 2703(d) to reach a journalist's account records, and the panel went out of its way to say so. What changed is that a district court must now do work it was previously allowed to skip. Where a provider makes a prima facie showing that some category of requested records "bears little, if any, relationship to the investigation," the court "may not dismiss it out of hand," must ask the government to justify the breadth, and "[i]f the district court is not persuaded, however, it must narrow the order." Slip op. at 14.

The gag order is the part worth sitting with. A § 2705(b) order is what makes this class of demand invisible to the people whose records are being handed over. Pair it with § 2703(c)(3), which relieves the government of any duty to notify the subscriber, and the structural result is that the journalists here could not object because they did not know. The panel said as much in its standing analysis: "The Secrecy Order keeps them entirely in the dark. Without LinkedIn's intervention, the risk to their First Amendment rights is significant." Slip op. at 10.

Here is our observation rather than the court's holding. When notice is barred and no duty-of-notice backstop exists, a provider's willingness to spend money litigating becomes the only practical check on scope. LinkedIn chose to litigate, and the overbreadth went unexamined until it did. Many providers, in many cases, make the other choice, and nothing in this decision requires anyone to litigate.

Part V cuts the other way and is easy to under-read. LinkedIn must now argue that a records demand is overbroad while still being denied the ex parte materials explaining why the government thinks it is not. The panel found no abuse of discretion in that. The practical consequence, again our reading, is that scope litigation under § 2703(d) proceeds with one side reasoning from the shape of the request rather than from the government's stated justification. The district court sees both; the provider does not.

The reasoning also travels well. The panel's route to a scope limit ran through the statutory phrases "relevant and material" and "undue burden," not through freestanding First Amendment doctrine, and it described the constitutional inquiry as merging with and strengthening that text. Courts outside Maryland, Virginia, West Virginia, North Carolina and South Carolina are not bound by any of it, but a statutory-construction argument tends to port across circuits more easily than a press-freedom balancing test.

The same structural tension is live elsewhere. How precisely a court must cabin a demand aimed at a provider's records, rather than at a suspect directly, is also the question running through the long fight over geofence warrants.

One note on sourcing. LinkedIn's parent, Microsoft, published a post on November 11, 2026 welcoming the ruling and calling on Congress to rewrite the rules on nondisclosure orders. That is a statement by a party about a case it largely won, not an independent reading of the opinion, and we treat it only as evidence of public reaction.

How This Affects You

This decision is about what a court must do before approving a demand, not about a right you can assert on your own. A few features of the statutory scheme are still worth understanding in general terms.

The records at issue are usually not the contents of your messages. A § 2703(d) order of the kind used here reaches "a record or other information pertaining to a subscriber to or customer of such service (not including the contents of communications)": account identifiers, who you connected with or messaged, and the dates and times. The opinion notes that on LinkedIn both connection requests and private messages "create metadata that record the sender, recipient, date, and time."

You often are not told, and that is by statute rather than oversight. Section 2703(c)(3) says the government "is not required to provide notice to a subscriber or customer" for records obtained under that subsection. A § 2705(b) order goes further and forbids the provider from telling you, for whatever period the court sets.

The showing required is lower than a warrant's. The government must offer "specific and articulable facts showing that there are reasonable grounds to believe" the records are "relevant and material to an ongoing criminal investigation," which the Fourth Circuit has called a reasonable suspicion standard. That is the bar Congress set in 1986 for this category of records, and only Congress can raise it.

What this ruling adds is a check inside the courthouse. In Maryland, Virginia, West Virginia, North Carolina and South Carolina, a district court approving a § 2703(d) order must analyze how much of the demand is plainly irrelevant and trim it, and must engage with a narrowing proposal before imposing a near-total gag. Whether that happens in any given case still depends on someone being present to raise it, and under this scheme that is ordinarily the provider. For how the states are separately legislating around data and account privacy, our state-by-state privacy law tracker follows that side of the picture.

This article is information, not legal advice. We are not a law firm and reading this does not create an attorney-client relationship. Court orders of this kind are sealed and fact-specific, and nothing above describes your situation or tells you what to do about it. If a records demand, a nondisclosure order, or a source-protection question affects you, consult a licensed attorney in your jurisdiction.

Related articles

• Stored Communications Act Explained: 18 U.S.C. § 2701
• What Is the ECPA? Electronic Communications Privacy Act
• Federal Recording Laws: ECPA, SCA, and CIPA Explained
• Federal Wiretap Act and ECPA: The Complete Guide (2026)
• Geofence warrants, Google, and the Supreme Court
• US State Privacy Laws Comparison

Last updated: 2026-11-12. This is a developing story; details verified as of 2026-11-12.

Frequently Asked Questions

What is a 2703(d) order?

It is a court order under 18 U.S.C. § 2703(d), part of the Stored Communications Act, that directs an online service to hand the government records about a subscriber. The statute says such an order 'shall issue only if the governmental entity offers specific and articulable facts showing that there are reasonable grounds to believe' the information sought is 'relevant and material to an ongoing criminal investigation.' A judge signs it, but on a lower showing than a search warrant requires.

Can police get my LinkedIn records?

Federal law allows the government to compel a provider such as LinkedIn to disclose 'a record or other information pertaining to a subscriber to or customer of such service (not including the contents of communications)' through one of the routes listed in 18 U.S.C. § 2703(c)(1), which include a warrant, a § 2703(d) court order, or your consent. In the Fourth Circuit case decided November 10, 2026, the government used a § 2703(d) order to seek journalists' LinkedIn metadata.

Do I get notified if my account records are subpoenaed?

Often not. Section 2703(c)(3) states that 'a governmental entity receiving records or information under this subsection is not required to provide notice to a subscriber or customer.' Separately, a court can issue a nondisclosure order under 18 U.S.C. § 2705(b) that forbids the provider from telling you. Whether you are ever told depends on the legal route used and on whether a nondisclosure order is in place.

What is a gag order on a subpoena?

In this context it is an order under 18 U.S.C. § 2705(b) directing the provider, 'for such period as the court deems appropriate, not to notify any other person of the existence of the warrant, subpoena, or court order.' The statute says a court shall enter one if there is reason to believe notice would cause one of five listed harms, such as destruction of evidence, witness intimidation, or otherwise seriously jeopardizing an investigation.

Is a 2703(d) order the same as a search warrant?

No. A warrant is one of the separate routes listed in § 2703(c)(1)(A), issued using the procedures in the Federal Rules of Criminal Procedure. A § 2703(d) order issues on the statute's 'specific and articulable facts' showing, which the Fourth Circuit has characterized as a reasonable suspicion standard, citing its 2013 decision in In re Application of the United States for an Order Pursuant to 18 U.S.C. Section 2703(d), 707 F.3d 283.

Did the Fourth Circuit stop the government from getting the journalists' records?

No. The panel reversed in part and remanded for the orders to be drawn more narrowly, and it rejected LinkedIn's request to quash them outright as going 'much too far.' The opinion states that the government 'is entitled to a disclosure order' and 'is even entitled to a broad disclosure order,' just 'not entitled to carte blanche.' What the district court must now do is analyze the degree of overbreadth and trim it.

Can a company refuse a 2703(d) order?

It cannot simply refuse, but the statute lets it ask the issuing court to intervene: a provider may move promptly to 'quash or modify such order, if the information or records requested are unusually voluminous in nature or compliance with such order otherwise would cause an undue burden on such provider.' The November 10, 2026 decision held that an order reaching plainly irrelevant records is itself an undue burden, so scope is a permissible ground and not just logistics.

Does this ruling apply in my state?

It binds federal district courts in the Fourth Circuit, which covers Maryland, Virginia, West Virginia, North Carolina and South Carolina. In other circuits it is persuasive authority that a party can cite but no court is obliged to follow. It also addresses federal Stored Communications Act orders, not demands issued under state law.