United States v. Richard Brillhart

Court of Appeals for the Eleventh Circuit·Decided July 9, 2026·No. 24-13232·Published

Opinion

FOR PUBLICATION

In the

United States Court of Appeals For the Eleventh Circuit

No. 24-13226

UNITED STATES OF AMERICA, Plaintiff-Appellee,

versus

RICHARD EDWARD BRILLHART, Defendant-Appellant.

Appeal from the United States District Court for the Middle District of Florida D.C. Docket No. 2:22-cr-00053-SPC-NPM-1

No. 24-13232

UNITED STATES OF AMERICA, Plaintiff-Appellee,

versus

USCA11 Case: 24-13226 Document: 55-1 Date Filed: 07/09/2026 Page: 2 of 37

2 Opinion of the Court 24-13226

RICHARD EDWARD BRILLHART, Defendant-Appellant.

Appeal from the United States District Court for the Middle District of Florida D.C. Docket No. 2:03-cr-00121-JES-KCD-1

Before NEWSOM, LUCK, Circuit Judges, and LEIBOWITZ,* District Judge. NEWSOM, Circuit Judge:

Richard Brillhart was convicted of possessing and distributing child pornography and sentenced to 480 months’ imprisonment . On appeal, he raises a host of challenges arising out of the investigation and prosecution of his crimes.

Most prominently, Brillhart argues that law-enforcement agents violated his Fourth Amendment rights when they searched a file that Google had found in his Gmail account and turned over to the National Center for Missing and Exploited Children. The key question before us is whether Google’s initial determination that the file contained child pornography—which it reached by employing an automated “hash-value matching” protocol—was the sort of “private search” that may, in appropriate circumstances, authorize a later government search. For reasons we’ll explain, we

* Honorable David S. Leibowitz, United States District Judge for the Southern

District of Florida, sitting by designation.

24-13226 Opinion of the Court 3

hold that it was and, therefore, that the government’s subsequent search of the file, which revealed no new material information, didn’t violate the Fourth Amendment.

Brillhart separately challenges the government’s decision to charge him with both distribution and possession of child pornography , as well as the district court’s admission (or exclusion) of various pieces of evidence, its denial of his motion for judgment of acquittal, and several of its sentencing decisions. On these issues, we affirm the district court in all respects save one: its application of a five-level “pattern of activity” sentencing enhancement under U.S.S.G. § 2G2.2(b)(5). Because we vacate and remand for resentencing to correct that error, we needn’t address Brillhart’s challenges to his supervised-release-revocation sentence.

I

A

Tech companies face an issue that social-media users know to be all too real: A non-negligible amount of unlawful activity occurs on their platforms. That creates legal and reputational risks. To combat the posting and sharing of harmful content, and to mitigate the associated perils, the companies have developed a variety of tools—some manual, others automated. This case turns, at least in part, on the particulars of one of the tools that Google has deployed to thwart the proliferation of child pornography.

Google apprises users of its anti-pornography initiatives in two ways. First, and most directly, its “terms of service,” to which customers must consent, expressly prohibit the use of its service

4 Opinion of the Court 24-13226

“in violation of the law”—and, more expressly still, prohibit the distribution of “child pornography.” Tr. of Mot. to Suppress Hr’g at 90, Dkt. No. 192. Second, and more indirectly, Google issues “transparency report[s]” that publicize its efforts to “identify, remove and report” child pornography using a “combination” of human review and “automated detection tools.” Id. at 97.

Specifically at issue here is one of those “automated detection tools” called hash-value matching. A hash value is a string of characters that together represent a file’s unique, algorithmically generated “digital fingerprint.” Id. at 121. 123. As relevant here, that means that if a photographic file is altered in any way, the hash value will change. Id. at 172. By contrast—and we’ll elaborate on the nuances in good time—if “two files ha[ve] the same hash value, they’re the same file[.]” Id. at 20. To be sure, our flesh-and-blood senses rebel at the notion that a digital image can be reduced to a collection of non-visual characters. But the fact is that a computer never “sees” the image as we do. To the computer, a hash value is a perfectly adequate—and accurate—digital stand-in.

Here’s how Google’s hash-value matching protocol works:

When the company detects a suspicious file—whether through a user report, automated scanning, or some other process—it immediately compares the file’s hash value to those in an internal “CSAM” (i.e., child sexual abuse material) repository. That repository contains the hash values of files previously determined by Google’s expert human reviewers to depict child pornography. Ac-

24-13226 Opinion of the Court 5

companying these hash values are standard “industry classification [s]”—jointly established by several internet service providers— that categorize the type of content in the file. So, for example, the classification “B1” means that the file depicts a “[p]ubescent minor involved in [an] overt sex act.” Id. at 114.

If the hash value of the suspect file matches one in the repository designated and classified as child pornography, then Google sends the file, along with its hash and classification, to the National Center for Missing and Exploited Children (NCMEC)—which, in turn, forwards the material to the appropriate law-enforcement officials . If the file’s hash value doesn’t match one in the repository, a Google employee will conduct a manual review. If he determines that it depicts child pornography, he may note the hash value and add it to the company’s internal repository along with his judgment about the image’s proper categorization. But the information he relays to NCMEC—file, hash value, categorization—are the same as that he would have conveyed had there been a hash match.

B

Enter Richard Brillhart. In May 2021, Yahoo and Google independently flagged email accounts transmitting what the companies believed to be child pornography. Two of those accounts— reb3280e@yahoo.com and reb3280@gmail.com—had a few common , revealing identifiers pointing to Brillhart: Both were created under the name “Reb Reb,” both listed the same recovery phone number tied to Brillhart, both used his birthdate (March 2, 1980) in

6 Opinion of the Court 24-13226

the usernames, and one listed his birthdate in its subscriber information .

Reviews of the email accounts yielded a lot of incriminating material. Brillhart’s Yahoo accounts were used to transmit 241 videos and images of suspected child pornography, including some depicting toddlers and prepubescent children engaged in sexual acts with adult men. One message included a selfie, which company investigators used to identify Brillhart. Consistent with Yahoo corporate policy, each file was manually reviewed by a human being and confirmed to be child pornography. The company then sent the files, along with Brillhart’s identifying information and sex-offender status, to NCMEC.

Google’s investigation determined that three of Brillhart’s email accounts contained a total of four illicit files. Three files were confirmed to depict child pornography by way of human review, the fourth through the hash-matching protocol already described. Like Yahoo, Google relayed the results of its investigation to NCMEC.

Free access — add to your briefcase to read the full text and ask questions with AI

United States v. Richard Brillhart, (11th Cir. 2026).

United States v. Richard Brillhart (United States v. Richard Brillhart) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

United States v. De La Cruz Suarez
601 F.3d 1202 (Eleventh Circuit, 2010)
United States v. Stinson
97 F.3d 466 (Eleventh Circuit, 1996)
United States v. Sherwin Tyrneal Nickels
324 F.3d 1250 (Eleventh Circuit, 2003)
United States v. Dodds
347 F.3d 893 (Eleventh Circuit, 2003)
United States v. Rigoberto Carrasco
381 F.3d 1237 (Eleventh Circuit, 2004)
United States v. Amadou Fall Ndiaye
434 F.3d 1270 (Eleventh Circuit, 2006)
United States v. Valladares
544 F.3d 1257 (Eleventh Circuit, 2008)
United States v. Bobb
577 F.3d 1366 (Eleventh Circuit, 2009)
United States v. Garcia-Bercovich
582 F.3d 1234 (Eleventh Circuit, 2009)
Blockburger v. United States
284 U.S. 299 (Supreme Court, 1931)
Dusky v. United States
362 U.S. 402 (Supreme Court, 1960)
Illinois v. Vitale
447 U.S. 410 (Supreme Court, 1980)
Walter v. United States
447 U.S. 649 (Supreme Court, 1980)
United States v. Jacobsen
466 U.S. 109 (Supreme Court, 1984)
United States v. Alfaro-Moncada
607 F.3d 720 (Eleventh Circuit, 2010)
United States v. Edgar Jamal Gamory
635 F.3d 480 (Eleventh Circuit, 2011)
United States v. Hill
643 F.3d 807 (Eleventh Circuit, 2011)
Larry Bonner v. City of Prichard, Alabama
661 F.2d 1206 (Eleventh Circuit, 1981)