LabMD – FTC Face-Off Continues Over FTC’s Data Privacy Authority

by | Jul 11, 2017

By Linda Henry

See all of Our JDSupra Posts by Clicking the Badge Below

View Patrick Law Group, LLC

The U.S. Court of Appeals for the Eleventh Circuit recently heard oral arguments in LabMD, Inc. v. Federal Trade Commission, the long-running dispute over the FTC’s authority to impose liability for data security breaches even in the absence of actual consumer injury. The Court’s decision, which is expected in the coming months, will have widespread implications on companies’ potential liability for lax security practices.

The LabMD dispute dates back to 2013 when the FTC filed an administrative complaint against LabMD, alleging that it failed to reasonably protect the security of consumers’ personal data, including protected health information. The FTC maintained that LabMD’s data security practices caused or were likely to cause substantial consumer injury, and thus constituted an unfair business practice under Section 5 of the FTC Act (the “Act”). Rather than settling the complaint with the FTC, LabMD became the second company to challenge the FTC’s authority over companies’ data security practices.

In 2015, an Administrative Law Judge (“ALJ”) dismissed the case after finding that the FTC had not met its burden of proof for demonstrating that LabMD had engaged in unfair practices in violation of the Act. Section 5 of the Act provides that a business practice is unfair if it “causes or is likely to cause substantial injury to consumers which is not reasonably avoidable by consumers themselves and not outweighed by countervailing benefits to consumers or to competition.” The ALJ found that the FTC failed to prove that LabMD’s data security practices were likely to cause” substantial consumer injury” as required by the Act, and cited the lack of evidence that anyone actually misused consumers’ data. The ALJ stated “[t]o impose liability for unfair conduct under Section 5(a) of the FTC Act, where there is no proof of actual injury to any consumer, based only on an unspecified and theoretical ‘risk’ of a future data breach and identity theft, would require unacceptable speculation and would vitiate the statutory requirements of ‘likely’ substantial consumer injury.”

The FTC later reversed the ALJ’s decision and maintained that the ALJ did not apply the correct legal standard in making its determination. The FTC stated: “contrary to the ALJ’s holding that ‘likely to cause’ necessarily means that the injury was ‘probable,’ a practice may be unfair if the magnitude of the potential injury is large, even if the likelihood of the injury occurring is low.” According to the FTC, it need not wait for consumers to suffer actual harm before exercising its enforcement authority under Section 5 of the Act.

In November 2016, the Eleventh Circuit Court of Appeals granted a stay of enforcement of the FTC’s Final Order until the pending appeal is resolved, stating that “there are compelling reasons why the FTC’s interpretation may not be reasonable.” The Court questioned whether the Act covers intangible harms such as those at issue in the LabMD case, and also whether the FTC was correct that the phrase “likely to cause” substantial injury to consumers should be interpreted to mean “significant risk” rather than “probable” risk. The Court noted that it did not interpret “the word ‘likely’ to include something that has a low likelihood,” thus finding that the FTC’s interpretation was not reasonable.

In the oral arguments before the Eleventh Circuit on June 21, 2017, LabMD argued that the Court should reject the FTC’s argument that “purely conceptual privacy harm that the FTC found to exist, whenever there is any unauthorized access to any personal medical information, constitutes substantial injury within the meaning of Section 5 under the FTC Act.” In addition, LabMD urged the Court to consider the legislative history of the Act, and pointed to a policy statement on which Congress relied when enacting the Act. According to LabMD, Congressional intent was to expressly exclude subjective injuries and as a result, the Court should not accept the FTC’s position that “likely injury” under Section 5 of the Act includes low-likelihood harm.

In the oral arguments, the FTC maintained that there is nothing in the Act or the Act’s legislative history that limits substantial injury to tangible injury, and that companies have an obligation to act reasonably under the circumstances. The Court questioned whether there is an outer limit to the FTC’s enforcement approach or anything would be beyond the power of the Commission to reach, however the FTC did not provide a direct answer to this question. When asked by the Court why the FTC did not use rulemaking to enact regulations that would address data privacy and security issues, the FTC replied that rule-making is not an effective way to proceed in the cybersecurity context due to the ever-evolving nature of technology and cybersecurity threats. The FTC went on to argue that it is much more sensible to say that a company must act reasonably than rely on rulemaking. The Court pressed for an explanation as to how a company could ever know with certainty what it means to act reasonably, however, the FTC maintained that failure to act reasonably under the circumstance is not a nebulous standard, and stressed that it does not act by using hindsight but rather, considers what is reasonable at the time the security breach occurs.

As the oral arguments made clear, the Court’s decision is likely to significantly impact the FTC’s data security enforcement authority. If the Eleventh Circuit agrees with LabMD’s position that the FTC must demonstrate concrete consumer harm or injury in order to bring an enforcement action under Section 5 of the Act, speculative injury may no longer be a sufficient basis for liability. If, however, the Court finds in favor of the FTC, companies may face liability for data security breaches if the FTC is able to show a “significant” risk of consumer injury, even if such injury is not probable and has not actually occurred.



Good, Bad or Ugly? Implementation of Ethical Standards In the Age of AI

By Dawn Ingley See all of Our JDSupra Posts by Clicking the Badge Below With the explosion of artificial intelligence (AI) implementations, several technology organizations have established AI ethics teams to ensure that their respective and myriad uses across...

IoT Device Companies: The FTC is Monitoring Your COPPA Data Deletion Duties and More

By Jennifer Thompson See all of Our JDSupra Posts by Clicking the Badge Below Recent Federal Trade Commission (FTC) activities with respect to the Children’s Online Privacy Protection Act (COPPA) demonstrate a continued interest in, and increased scrutiny of,...

Predictive Algorithms in Sentencing: Are We Automating Bias?

By Linda Henry See all of Our JDSupra Posts by Clicking the Badge Below Although algorithms are often presumed to be objective and unbiased, recent investigations into algorithms used in the criminal justice system to predict recidivism have produced compelling...

My Car Made Me Do It: Tales from a Telematics Trial

By Dawn Ingley See all of Our JDSupra Posts by Clicking the Badge Below Recently, my automobile insurance company gauged my interest in saving up to 20% on insurance premiums.  The catch?  For three months, I would be required to install a plug-in monitor that...

When Data Scraping and the Computer Fraud and Abuse Act Collide

By Linda Henry See all of Our JDSupra Posts by Clicking the Badge Below As the volume of data available on the internet continues to increase at an extraordinary pace, it is no surprise that many companies are eager to harvest publicly available data for their own use...

Is Your Bug Bounty Program Uber Risky?

By Jennifer Thompson See all of Our JDSupra Posts by Clicking the Badge Below In October 2016, Uber discovered that the personal contact information of some 57 million Uber customers and drivers, as well as the driver’s license numbers of over 600,000 United States...

IoT Device Companies: COPPA Lessons Learned from VTech’s FTC Settlement

By Jennifer Thompson See all of Our JDSupra Posts by Clicking the Badge Below In “IoT Device Companies:  Add COPPA to Your "To Do" Lists,” I summarized the Federal Trade Commission (FTC)’s June, 2017 guidance that IoT companies selling devices used by children will be...

Beware of the Man-in-the-Middle: Lessons from the FTC’s Lenovo Settlement

By Linda Henry See all of Our JDSupra Posts by Clicking the Badge Below The Federal Trade Commission’s recent approval of a final settlement with Lenovo (United States) Inc., one of the world’s largest computer manufacturers, offers a reminder that when it comes to...

#TheFTCisWatchingYou: Influencers, Hashtags and Disclosures 2017 Year End Review

Influencer marketing, hashtags and proper disclosures were the hot button topic for the Federal Trade Commission (the “FTC”) in 2017, so let’s take a look at just how the FTC has influenced Social Media Influencer Marketing in 2017. First, following up on the more...

Part III of III | FTC Provides Guidance on Reasonable Data Security Practices

By Linda Henry See all of Our JDSupra Posts by Clicking the Badge Below This is the third in a series of three articles on the FTC’s Stick with Security blog. Part I and Part II of this series can be found here and here. Over the past 15 years, the Federal Trade...