Federal Trade Commission v. Johnson

156 F. Supp. 3d 1202, 2015 U.S. Dist. LEXIS 173522, 2015 WL 9592497
District Court, D. Nevada·Decided December 31, 2015·No. Case No. 2:10-cv-02203-MMD-GWF·Published·Cited by 2 cases

Opinion

ORDER

MIRANDA M. DU, UNITED STATES DISTRICT JUDGE

I. INTRODUCTION

The Court granted summary judgment in favor of the FTC in part with respect to certain grant websites and deferred resolution of several issues, including review of additional sites (“SJ Order”).1 (Dkt. no. 1586). The Court addressed the remaining sites in an earlier Order. (Dkt. no 1794.) This Order addresses the remaining unresolved issues: affiliate liability, common enterprise liability, individual liability and disgorgement. (Dkt. no. 1586 at 60.) The Court grants summary judgment in favor of the FTC on the issue of affiliate liability, common enterprise liability, and individual liability with respect to Jeremy Johnson and Ryan Riddle. The Court denies sum[1206]*1206mary judgment on the issue of disgorgement.

II. BACKGROUND

The relevant factual background is recited in the SJ Order. (Dkt. no. 1586.) The Court permitted supplemental briefings on the issue of consumer redress and relevant new case law. (Dkt. no. 1599.) The parties submitted supplemental briefs on the issues addressed in this Order. (Dkt. nos. 1619,1636,1638.)

III. DISCUSSION

A. Affiliate Liability

The Court has found that, as a matter of law, a number of iWorks’ websites violated Section 5(a) of the FTC Act. (Dkt. nos, 1586, 1794.) Defendants argue that even if the sites are deceptive, they should not be held vicariously liable if the sites were hosted by third party advertisers or marketers.2 (Dkt. no. 1343 at 42.) As a secondary argument, Defendants contend that because they maintained a commercially reasonable monitoring program, they should not be liable for deceptive sites hosted by affiliates. (Id. at 43.) As part of the monitoring program, iWorks sought voluntary compliance from affiliates who violated the terms of their agreements, followed by written warnings, withheld payments, rejected sales, and termination of the relationship. (Id. at 49.)

' The FTC contends that iWorks was contractually responsible for the sites hosted by brokers and marketing partners. In support of its position, the FTC points to networking agreements iWorks entered into with these third parties. (Dkt. no. 1280 at 30; dkt. no. 1387 at 48-49.) The agreements gave iWorks final say over the content and display of information about its offers on its partners’ websites. (See, e.g., dkt. nos. 1338-3; 22-1 at 25, 33; 22-2 at 17; 22-3 at 1.) The FTC argues that the same monitoring program that iWorks believes absolves it of liability should be considered further evidence of its control over its marketing partners’ sites'. According to the FTC, iWorks’ ability to monitor sites through its pixel tracking system and its ability to communicate with and discipline brokers and marketing partners simply show that iWorks understood that it was ultimately responsible for the content on those sites. The Court agrees with the FTC.

Defendants are liable for violations of Section 5(a) of the FTC Act committed by third parties if those parties are acting within the scope of their actual or apparent authority. See Southwest Sunsites, Inc. v. FTC, 785 F.2d 1431, 1438-39 (9th Cir.1986). The agreements between iWorks and its partners clearly indicate that iWorks was responsible for approving representations and disclosures regarding its products. For example, iWorks’ agreement with Virgin indicates that iWorks requires proofs and tracking information for each website and “shall be responsible and .liable” for all of the content it approves. (Dkt. no. 1389-9 ¶¶ 4.2, 4.4, 4.5.) Similarly, iWorks’ agreement with Skunk Werks Media3 gives iWorks authority to “approve any and all of [Skunk Werks Media’s] marketing material related to [its product], including, but not limited to graphic and text creatives,” and requires Skunk Werks to provide iWorks with “snap shots of its marketing material for iWorks’ written ap[1207]*1207proval.” (Dkt. no. 1338-3 at 3, 8.) iWorks’ agreements with other third party affiliates, such as PVI and Cathexis, contain identical or similar language. (See, e.g., dkt. nos. 22 at 24; dkt. no. 1339-30.) These agreements clearly indicate that iWorks retained final editorial control over the advertisements for its products.

Defendants’ secondary argument is without merit. Defendants have not identified any authority holding that establishing a commercially reasonable monitoring program is some sort of safe haven or affirmative defense to a violation of the FTC Act. In fact, courts have clearly held otherwise. See Goodman v. FTC, 244 F.2d 584, 592 (9th Cir.957) (“[T]he courts take the view that the principal is bound by the acts of the salesperson he chooses to employ, if within the actual or apparent scope of his authority, even when unauthorized.”); see also FTC v. Stefanchik, No. C04-1852RSM, 2007 WL 1058579, at *6 (WD.Wash. Apr. 3, 2007) (“Under the FTC Act, a principal is liable for misrepresentations made by its agents regardless of any efforts of the principal to prevent such misrepresentations.”) aff'd, 559 F.3d 924 (9th Cir.2009). A monitoring program would help iWorks ensure compliance by third party brokers, but iWorks would still be bound by its brokers’ conduct so long as they acted within the scope of their authority.

The FTC has offered undisputed evidence that iWorks’ marketing partners— namely PVI, Virgin, Cathexis and Skunk Werks Media — were acting with actual authority pursuant to their agreements with iWorks. Therefore, Defendants are liable for violations of the FTC Act even if the representations were made on websites hosted by these third parties.

B. Common Enterprise

The FTC asks this court to recognize all of the Corporate Defendants in this case as part of a common enterprise. Under the theory of common enterprise, each entity in a group of interrelated companies can be held jointly and severally liable for the actions of other entities in that group. FTC v. Network Servs. Depot, Inc., 617 F.3d 1127, 1142-43 (9th Cir.2010). “Entities constitute a common enterprise when they exhibit either vertical or horizontal commonality — qualities that may be demonstrated by a showing of strongly interdependent economic interests or the pooling of assets and revenues.” Id. “To determine whether a common enterprise exists, the Court considers factors such as: common control; the sharing of office space and officers; whether business is transacted through a maze of interrelated companies; the commingling of corporate funds and failure to maintain separation' of companies; unified advertising; and evidence that reveals that no real distinction exists between the corporate defendants.” FTC v. Grant Connect, LLC, 827 F.Supp.2d 1199, 1216 (D.Nev.2011) aff'd in part, vacated in part, 763 F.3d 1094 (9th Cir.2014).

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

Federal Trade Commission v. Johnson, 156 F. Supp. 3d 1202, 2015 U.S. Dist. LEXIS 173522, 2015 WL 9592497 (D. Nev. 2015).

156 F. Supp. 3d 1202 (Federal Trade Commission v. Johnson) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related