Police Misconduct Changes Everything in Reckless Ben Case

Why It Matters

The mishandled release turns a questionable police action into a verifiable record, giving Ben a solid basis for civil‑rights claims and exposing systemic accountability failures within the department.

Key Takeaways

• Police accidentally released unredacted 48 GB of footage online.
• YouTuber claimed a hack, but department itself uploaded files.
• Accidental release validates evidence, avoids chain‑of‑custody doubts entirely.
• Redacted audio gaps reveal officers discussing charges and camera shutdown.
• Potential civil‑rights claims include retaliation, unlawful stop, and Franks warrant issues.

Summary

The Utah police department unintentionally posted a 48 GB folder of body‑camera and dash‑camera recordings from a four‑day March incident involving YouTuber Benjamin Schneider, known as Reckless Ben. The files were labeled as a media kit, left unredacted, and were quickly mirrored on the Internet Archive after the department attempted to remove them. Schneider later told national television that the footage had been hacked, a claim contradicted by the department’s own admission that the upload was its own mistake.

The unredacted footage shows officers debating possible felony charges—stalking, digital bullying, and usury—while also admitting they turned off Ben’s recording device. Redacted segments, originally explained as protecting a victim’s identity, actually conceal these internal discussions, suggesting selective editing rather than a simple privacy safeguard. The incident also includes a traffic stop allegedly extended to “scare” Ben, a search warrant based on a tip from an officer who knew the Airbnb host, and an arrest that resulted in only misdemeanor charges despite the earlier felony talk.

Key moments include an officer’s on‑camera remark, “I was going to scare him a little,” directly violating the Supreme Court’s Rodriguez rule on stop duration, and the officer’s acknowledgment of shutting off the recording, implicating a breach of the First Amendment right to film police. The discrepancy between the felony language in the footage and the misdemeanor charges filed fuels a potential retaliation claim under Nieves, while the undisclosed relationship with the tipster raises a Franks‑type warrant challenge.

Legally, the accidental public release strengthens the evidentiary weight of the video, removing chain‑of‑custody doubts and shielding Ben from computer‑fraud liability. It also opens multiple civil‑rights avenues: retaliation for filming, unlawful stop, and possibly a flawed warrant. For law‑enforcement agencies, the episode underscores the risks of careless data handling and the importance of transparent redaction practices.

Original Description

The American Fork Police Department accidentally uploaded 48GB of unredacted body camera footage to a public link — and what was hidden in the redacted version may be worse than a cover-up.

Here's the qualified immunity problem at the center of the Reckless Ben / Bricks & Minifigs case.

When YouTuber Reckless Ben (Benjamin Schneider) said the footage was "hacked," he got the single most important fact wrong — and in a way that hurt his own case.

In this video I break down what the American Fork PD bodycam footage actually shows, why the police's redaction explanation doesn't hold up, and why qualified immunity may let officers walk even if every constitutional violation is real.

We cover:

— The "hack" that wasn't: why an accidental public release gives the footage clean provenance (and why "hacked" was a self-inflicted wound)

— What the redacted audio was actually hiding, and the Hope v. Pelzer "consciousness of liability" problem it creates

— The four days in March: a prolonged traffic stop under Rodriguez v. United States, a search warrant that returned "No items seized," and a Franks affidavit question

— Felony stalking and usury floated on camera — and the four misdemeanors actually filed

— A clear-eyed Section 1983 analysis: the First Amendment right to record (Irizarry v. Yehia, 10th Cir. 2022), retaliation, and Monell liability

— Qualified immunity explained: the two-step test, the "clearly established" trap, and why the doctrine can perpetuate itself

— Two corrections from earlier videos, including the contested Oregon small-claims judgments

Nothing here has been decided by a court. Allegations are identified as allegations, and footage presented by a party to the dispute is flagged as such.

⚖️ I'm Leonard French — your favorite copyright attorney.

🔗 LINKS

Support the channel: patreon.com/ljfrench

Send a postcard to Congress: PostcardsToCongress.org (coupon code Just5Dollars)

#RecklessBen #BricksAndMinifigs #QualifiedImmunity #BodyCam #CivilRights #FirstAmendment #LegalAnalysis #Section1983 #AmericanFork #LegoLawsuit

📌 CHAPTERS

0:00 - The footage they didn't mean to release

01:39 - Disclaimer

02:07 - I. The hack that wasn't

06:01 - II. What the redactions were hiding

09:46 - III. Four days in March

13:54 - IV. The felony that never came

18:59 - V. The shield

23:45 - Where this leaves us

25:53 - Please Support Lawful Masses