Quick Answer
Sometimes, and the reason is narrower than the headlines suggest. After a fatal crash in Wisconsin in which a passenger used Snapchat’s speed filter while the car reached 123 miles per hour, the United States Court of Appeals for the Ninth Circuit held in Lemmon v. Snap, Inc., No. 20-55295, filed May 4, 2021, that Section 230 of the Communications Decency Act did not immunize Snap from the parents’ negligent design claim. The court did not decide that Snap was liable. It reversed a dismissal and sent the case back for further proceedings. Two things follow for a Kentucky reader. Section 230 is federal immunity for a platform sued over content provided by someone else, not a general shield against every claim, and it decides nothing about whether a Kentucky negligence or product design claim can be proved. The driver who hit you is still the first defendant, and Kentucky’s own statutes govern the claim.
Snapchat is a widely used social media app, and one of its features has been blamed for encouraging drivers to travel at dangerous speeds so they could record and share the result. A federal appeals court held that its owner, Snap, Inc., was not protected from suit by Section 230 in a case brought by the parents of two of three young men killed in a single crash in Walworth County, Wisconsin.
The cases involving Snapchat come down to a single question. Is the app a defective product because its design encouraged dangerous driving, so that its maker owes the same duty as any other manufacturer, or is the company being sued as a publisher of content that someone else created, in which case federal law bars the claim? The Ninth Circuit answered that the claim in front of it was the first kind, not the second.
Speeding Car Shared on Snapchat Encouraged Reckless Driving That Caused Crash
Users post messages, photos and videos on Snapchat. According to the court’s account of the amended complaint, on May 28, 2017, at around 7:00 p.m., three young men were driving on Cranberry Road in Walworth County, Wisconsin. Jason Davis, age 17, was driving. Landen Brown, age 20, was in the front passenger seat, and Hunter Morby, age 17, was in the back. At some point the car began to speed as fast as 123 miles per hour, and they traveled at those speeds for several minutes before running off the road at roughly 113 miles per hour and striking a tree. The car caught fire and all three died.
Shortly before the crash, it was Landen Brown, the front seat passenger, who opened Snapchat to document how fast they were going, and who used the feature known as the speed filter, which lets a user record their real world speed and overlay it on a photo or video. The lawsuit was brought by Carly Lemmon and Michael Morby, Hunter’s parents, together with Samantha Brown and Marlo Brown, Landen’s parents. Their theory was not that the snap itself hurt anyone. It was that Snapchat’s reward system, which gives users trophies, streaks and social recognition without telling them how those rewards are earned, worked together with the speed filter to encourage young drivers to reach high speeds. The complaint alleged that Snap knew or should have known about the problem before this crash, pointing to news coverage, an online petition, at least three other crashes linked to users chasing high speed snaps, and at least one earlier lawsuit, and that a warning against snapping and driving had proved ineffective.
The trial court dismissed the case, and the parents appealed. On May 4, 2021 the Ninth Circuit reversed that dismissal and remanded the case. It is worth stating clearly what that did and did not decide, because the original version of this article overstated it. The appeals court did not find that Snap was liable, and it did not find that the app caused these deaths. It held only that Section 230(c)(1) did not bar the claim at the pleading stage, and it expressly declined to decide whether the parents had adequately pleaded causation, leaving that for the trial court.
Appeals Court Finds Snapchat Owner Not a Publisher
At issue is Section 230 of the federal Communications Decency Act, codified at 47 U.S.C. 230. The operative sentence is narrower than its reputation. Section 230(c)(1) provides that no provider or user of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider. Section 230(f)(2) defines an interactive computer service broadly, and Section 230(f)(3) defines an information content provider as any person or entity responsible, in whole or in part, for the creation or development of information provided through the internet. Section 230(e)(3) then preempts state or local law that is inconsistent with the section while expressly leaving states free to enforce consistent law.
Read those pieces together and the shape of the protection becomes clear. It shields a platform from being held responsible for what its users say and post. It is not a blanket immunity from every civil claim, and it does nothing at all where the claim does not depend on third party content. The article’s earlier description of Section 230 as protecting tech companies from libel and other civil suits over online posts no matter how harmful has the first half right and the second half wrong.
The Ninth Circuit applied a three part test. Snap enjoys immunity only if it is a provider or user of an interactive computer service, whom the plaintiff seeks to treat under a state law cause of action as a publisher or speaker, of information provided by another information content provider. Nobody disputed the first element. The court held the second was not met, because the claim turned on Snap’s own design of the app and treated Snap as a product manufacturer rather than as a publisher, and it noted that Snap could have met the alleged obligation to design a reasonably safe product without altering any content its users generate. The court held the third element was not met either, because Snap indisputably designed the reward system and the speed filter itself, and the parents disclaimed any complaint about the snap that was actually sent.
The opinion describes the legal premise of a negligent design claim as the rule that manufacturers have a duty to exercise due care in supplying products that do not present an unreasonable risk of injury or harm to the public, and frames the question as whether a reasonable person would conclude that the reasonably foreseeable harm of a product built to its design outweighs the product’s utility. The court also relied on an earlier Georgia Court of Appeals decision in the same line, Maynard v. Snapchat, Inc., 816 S.E.2d 77 (Ga. Ct. App. 2018), which it quoted for the proposition that a claim seeking to hold Snapchat liable for its own conduct, principally for the creation of the speed filter, is not a publisher claim.
Where Do Snapchat Cases Go From Here?
Honesty is better than prediction here. A reversal at the pleading stage means the case goes back to the trial court, where the plaintiffs still have to prove duty, breach, causation and damages, and where Snap is free to press the causation defense the appeals court declined to reach. We could not verify from an official court source what ultimately happened after remand in the Ninth Circuit case, or the final disposition of the parallel Georgia litigation, so we are not going to tell you how either one ended. What the published decision does establish is a legal boundary that matters well beyond Snapchat: a claim aimed at how a platform was designed is analyzed as a product claim, while a claim aimed at what users posted runs into Section 230.
That boundary is also where these cases are won and lost. The same Ninth Circuit opinion notes in a footnote that the parents could use the snap sent minutes before the crash as circumstantial evidence of causation, but could not fault Snap for publishing other users’ content, such as snaps of friends speeding, that may have encouraged the young men. Design in, content out. Any future case against a platform over a crash has to be built entirely on the first side of that line.
None of this changes the fact that a company is entitled to argue that its product was misused, that it warned against the very conduct at issue, and that the driver’s own choices caused the crash. Those are ordinary defenses in a design case, and Kentucky’s product liability statutes give them real teeth, as the next section explains.
What Would a Claim Like This Look Like Under Kentucky Law?
Lemmon v. Snap is a federal appellate decision applying California or Wisconsin tort law, and it is persuasive rather than binding here. If an app were part of the story in a Kentucky crash, the claim would be built on Kentucky law, and the honest starting point is that the driver is the defendant with the clearest duty. Kentucky requires every operator to drive at a speed that is reasonable and prudent for the traffic and for the condition and use of the highway under KRS 189.390(2), and to operate the vehicle in a careful manner with regard for the safety of pedestrians and other vehicles under KRS 189.290(1), with KRS 189.290(4) separately prohibiting reckless or negligent operation that endangers persons or property. Phone use has its own rule, and it is narrower than most people assume. KRS 189.292(2) prohibits a person operating a motor vehicle in motion on the traveled portion of a roadway from writing, sending or reading text based communication on a personal communication device, with exceptions in subsection (3) for navigation features, for dialing a phone number, and for reporting an emergency. Whether opening a camera filter falls inside a prohibition written around text based communication is not something the statute answers, so the broader careless and reckless driving duties usually carry more weight in a crash claim than the texting statute does. Under KRS 446.070, a person injured by the violation of any statute may recover the damages sustained by reason of that violation.
A design claim against the app maker would run through Kentucky’s Product Liability Act, and that Act is broad enough to reach it on its face. KRS 411.300(1) defines a product liability action to include any action brought for personal injury or death caused by or resulting from the design, development of standards, testing, warning, instructing, marketing or advertising of any product. The defenses are where Kentucky gets hard. KRS 411.320(1) limits a manufacturer’s liability to the harm that would have occurred had the product been used in its original, unaltered and unmodified condition. KRS 411.320(2) bars recovery where the plaintiff’s own unauthorized alteration was a substantial cause of the occurrence, and KRS 411.320(3) bars recovery where the plaintiff failed to exercise ordinary care in using the product and that failure was a substantial cause, whether or not the product was defective. KRS 411.310(2) adds a rebuttable presumption that a product was not defective if its design, methods of manufacture and testing conformed to the generally recognized and prevailing standards or the state of the art when the design was prepared. In a case about an app that a passenger opened while a driver chose to accelerate, the ordinary care defense in KRS 411.320(3) is the argument a manufacturer will make first.
Fault would then be divided rather than assigned to one party. Under KRS 411.182(1) and (2) the fact finder assigns a percentage of the total fault to each claimant, defendant and third party defendant, weighing both the nature of the conduct and how closely it is connected to the damages. Kentucky’s comparative fault doctrine itself comes from decisions of the Kentucky courts rather than from that statute. Under KRS 411.182(3) the judgment states each party’s equitable share, which makes liability several rather than joint and several, so you cannot collect the entire award from whichever defendant has the deepest pocket. If someone died, the action belongs to the estate rather than to a relative individually: KRS 411.130(1) allows damages to be recovered where a death results from an injury inflicted by the negligence or wrongful act of another, permits punitive damages where the act was willful or the negligence gross, and requires the action to be prosecuted by the personal representative of the deceased, with KRS 411.130(2) setting the order of distribution.
The deadlines are the part that quietly decides whether any of this is available. A Kentucky motor vehicle tort action must be commenced no later than two years after the injury or the death, or after the issuance of the last basic or added reparation payment, whichever occurs later, under KRS 304.39-230(6). The general Kentucky personal injury limitation is only one year under KRS 413.140(1)(a), and a product design claim against a company that does not own or operate a vehicle is not obviously a motor vehicle tort. Because that question is not free from doubt, the safe course in a case with both a driver and a manufacturer in it is to treat the shorter clock as the one that governs and to move accordingly. Waiting to see how a novel theory develops is the one thing that cannot be undone.
Was an App or a Phone Part of the Crash That Hurt You?
Most crashes come down to a driver who was going too fast, looking at a screen, or both, and that is the claim that pays for the surgery and the missed work. Now and then the story is bigger than the driver, and it is worth having someone look. The Fleck Firm, PLLC was founded by attorney Tyler M. Fleck, a U.S. Army veteran who built his practice to serve people throughout Kentucky. If a distracted or speeding driver injured you or took someone in your family, we will get the phone and vehicle data preserved before it is overwritten, tell you honestly whether anyone besides the driver can be held responsible, and keep the deadlines from closing on you while you recover. Our car accident and wrongful death work begins with a free consultation and we handle these cases on a contingency fee, so there is no fee unless we win for you. Call (270) 446-7000, and if you cannot come to us we will come to you, including at the hospital or your home.








