Infogroup, Inc. v. Databasellc
Decision Date | 30 March 2015 |
Docket Number | No. 8:14–CV–49.,8:14–CV–49. |
Citation | 95 F.Supp.3d 1170 |
Parties | INFOGROUP, INC., et al., Plaintiffs, v. DATABASELLC, et al., Defendants. |
Court | U.S. District Court — District of Nebraska |
Alan D. Sege, Alan Sege Law Firm, Los Angeles, CA, Ari N. Rothman, Venable Law Firm, Washington, DC, Brooke H. McCarthy, Douglas W. Peters, John P. Passarelli, Kutak, Rock Law Firm, Omaha, NE, for Plaintiffs.
Mark C. Laughlin, Patrick S. Cooper, Fraser, Stryker Law Firm, Omaha, NE, for Defendants.
This matter is before the Court on the plaintiffs' motion for preliminary injunction (filing 12), motion to strike affirmative defenses (filing 61), and motion to dismiss counterclaims (filing 63). The Court will deny each of the plaintiffs' motions.
The plaintiffs and the defendants are all, generally speaking, in the information business: they compile databases about consumers and businesses and they sell access to that information through various Web sites. The plaintiffs are Infogroup, Inc., infoUSA, Inc., and infoUSA Marketing, Inc. (collectively, Infogroup). Filing 23 at 1. The defendants are DatabaseUSA.com and several individual employees of DatabaseUSA.com (collectively, DatabaseUSA).1 Filing 23 at 1–2 The individual defendants are all former employees of Infogroup—most pertinently, Vinod Gupta, the founder of Infogroup, and a former officer and shareholder. Filing 23 at 2; filing 13 at 2. Gupta founded DatabaseUSA after leaving Infogroup, and there is no love lost between them.
Infogroup has pled several claims for relief, but as relevant to the current motions, Infogroup's claims generally fall into three categories: (1) DatabaseUSA's alleged acquisition of information from Infogroup's proprietary database, (2) alleged false advertising regarding the extent to which DatabaseUSA's information is “verified,” and (3) alleged false representations suggesting to potential customers that there is a corporate relationship between DatabaseUSA's products and Infogroup.
As mentioned above, the basis of Infogroup's business is its proprietary database. To check the security of its database, Infogroup inserts “seed data” into its listings, containing fictitious combinations of name, address, and telephone number. Filing 14–1 at 3. Seed data is disbursed through the database geographically, and per industry, on a monthly basis. Filing 32–2 at 19–20; filing 33–1 at 2. So, if Infogroup's seed data appears in the wild, in a competitor's list, Infogroup knows that the competitor has somehow gained access to Infogroup's information.2 Filing 14–1 at 3. But the word “somehow” is important, because how the competition got information from Infogroup's database makes all the difference when it comes to establishing liability—and, as a precursor to liability, obtaining a preliminary injunction.
In June 2013, Infogroup found its November 2011 seed data in DatabaseUSA's products.3 Filing 33–1 at 5; filing 40–1 at 2. Specifically, Infogroup found all of the expected seeds for its November 2011 data set. Filing 33–1 at 3. According to Infogroup's Vice President of Business Optimization, the presence of November 2011 seed files—but no other seed files—and the high match rate between Infogroup's data and DatabaseUSA's data suggests that DatabaseUSA acquired Infogroup's full business database at one point in time.4 Filing 40–1 at 2–3. Infogroup sued, theorizing that the individual defendants—each of whom had left Infogroup and been hired by DatabaseUSA—had provided DatabaseUSA with misappropriated data or access to Infogroup's systems. Filing 23 at 7, 11, 13–14, 16–17.
But DatabaseUSA's evidence pokes some holes in that theory. The information in Infogroup's database is not wholly unavailable to the world at large—to begin with, while some data may come from private sources or Infogroup's own information-gathering, a substantial amount of the data is compiled from publicly-available sources. Filing 32–2 at 5–6; filing 33–1 at 2. And, of course, because Infogroup makes money by selling information, some data is made publicly available after it is compiled. Some of Infogroup's data is available to the public on search services such as Google, Yahoo!, Bing, and Ask.com. Filing 32–2 at 8–10. The business database is available through a reference service provided to libraries. Filing 32–2 at 10. Obviously, data sets have been sold to customers, sometimes through resellers, although Infogroup's licensed customers are prohibited by licensing agreements from providing that data to DatabaseUSA. Filing 32–2 at 10–11; filing 33–1 at 12, 18–19. And DatabaseUSA points out that third parties have been able to “scrape” database information from publicly-accessible sources and bundle it for resale. Filing 33–2 at 4. Information from at least some of Infogroup's seed files has been found in other competitors' data and on public search engines. Filing 33–1 at 9–10; filing 33–3 at 69–225.
DatabaseUSA's evidence also casts substantial doubt on whether any of the individual employee defendants could have obtained the data at issue. Three of the five individual defendants were terminated by Infogroup before the November 2011 seed data was inserted into the Infogroup database. Another was not hired by DatabaseUSA until after the June 2013 audit that discovered the seed data. And none of the former Infogroup employees (with the presumable exception of Gupta, who was out the door by 2008) had the necessary access to Infogroup's database to have perpetrated a heist.
None of that conclusively proves that the individual defendants were uninvolved—for instance, someone might have been secretly working for DatabaseUSA, exceeded his authorized access to Infogroup's database, or been working with someone else at Infogroup. But there is no evidence of any of that. Infogroup speculates that perhaps DatabaseUSA bought the information from someone else who “scraped” it. Filing 39 at 4. But in the end, it suffices to say this: it is certain that information from Infogroup's proprietary database ended up in DatabaseUSA's hands, and it is wholly uncertain how that happened.5
Infogroup claims that DatabaseUSA is falsely representing its database entries as “verified” when they are not. Filing 23 at 9–11, 32–33. This claim, factually, is mostly derived from the presence of Infogroup's seed files in DatabaseUSA's database. DatabaseUSA promotes its database as “Triple–Verified.” Filing 14–2 at 36. When Infogroup marks a listing in its database as “verified,” that apparently means an Infogroup employee has confirmed that the information is accurate and current. Filing 14–1 at 2. It is far less apparent what a “verified” record means to DatabaseUSA. E.g., filing 48–1 at 2; filing 51 at 8. But there is evidence that DatabaseUSA promotes its “verification process” as involving “original sources,” telephone verification, and Internet research. Filing 82–1 at 8; Ex. A.
DatabaseUSA displayed some of Infogroup's seed files as “verified” records, stating that “Verified Records have been through our verification process that includes phone verification, search engine research and business website review.”
Filing 14–2 at 23. Infogroup's argument is simple: how could DatabaseUSA have “verified” a fictitious entry? Filing 13 at 9. And Infogroup points to other inaccuracies in supposedly-“verified” entries in DatabaseUSA's data. Filing 82–3. But DatabaseUSA points out that even Infogroup's seed files contain some real information. For instance, one of the seed files at issue is a fictional business, but the address is a real place, and the telephone number is a working number belonging to an Infogroup employee. Filing 31 at 19. So, there is still some information that could be “verified” by certain methods. DatabaseUSA also points to similar inaccuracies among Infogroup's “verified” listings, filing 86–3, and argues that even “verified” listings will sometimes be incorrect because information changes and not every listing can be verified every day. Filing 85 at 12–13. And DatabaseUSA presented evidence of the process that it uses, internally, to verify the accuracy of its listings. Filing 33–2 at 2–3; filing 48–1 at 1–2.
Infogroup claims that DatabaseUSA is making misleading statements, in press releases and advertisements, that falsely imply an ongoing relationship between Gupta and Infogroup, or DatabaseUSA and Infogroup. Infogroup has presented evidence of these instances:
To continue reading
Request your trial-
Copperhead Agric. Prods. v. KB AG Corp.
... ... 1, 14. Beginning in as early as February 7, 2011, Don Estes began working for CM Welding, Inc. ("CM Welding"), a company in Frankfurt, Indiana, owned by Carolyn Mitchell Estes. Doc. 63-5. A ... (a)(1)(B) and likelihood of confusion test to false endorsement claim under (a)(1)(A)); Infogroup , Inc ... v ... Database LLC , 95 F.Supp.3d 1170, 1188-92 (D. Neb. 2015) (same). As noted by the ... ...
-
Poole v. City of Lincoln
... ... no possible relation or logical connection to the subject matter of the controversy." Infogroup, Inc., v. DatabaseLLC , 95 F.Supp. 3d 1170, 1194 (D. Neb. 2015); Lane v. Page , 272 F.R.D. 581, ... ...
-
W. Plains, L. L.C. v. Retzlaff Grain Co., 16-2650.
... ... " Wilson v. Brinker Int'l, Inc. , 382 F.3d 765, 769 (8th Cir. 2004) (quoting City of Omaha Emps. Betterment Ass'n v. City of ... proof that there was a reasonable likelihood or probability of a business relationship." Infogroup Inc. v. Database LLC , 95 F.Supp.3d 1170, 1196 (D. Neb. 2015). 6 Bradley sent all of his contacts ... ...
-
Benson v. City of Lincoln
... ... Yellow Book USA , Inc ., 445 F.3d 1074, 1079 (8th Cir. 2006) ("Title VII addresses the conduct of employers only and does ... no possible relation or logical connection to the subject matter of the controversy." Infogroup , Inc ... v ... DatabaseLLC , 95 F. Supp. 3d 1170, 1194 (D. Neb. 2015) (citations omitted). "[E]ven ... ...