Perry Street Software, Inc. v. Jedi Technologies, Inc.

District Court, S.D. New York·Decided October 22, 2020·No. 1:20-cv-04539·Unknown

Opinion

Case 1:20-cv-04539-CM Document □□ Filed 10/22/20 Page 1 of 4

Sehaeoae LLAHAN ROBSON & GARZA, PLLC _ || USDC SDNY ATTORNEYS AND COUNSELORS AT LAW DOCUMENT 3333 Lee Parkway Suite 460 Direct Dial: (469) 587-7240 LED Dallas, Texas 75219 Facsimile: (214) 764-8392 ~ □□ yw of pare FiLeb:_a Bofors |e od : October 22, 2020 ) , b □ “ { By ECF and By Hand Delivery ltr (Dt The Honorable Colleen McMahon [we A ope United States District Court p> U 4 □ Southern District of New York sk Hts fe □□□□ 500 Pearl Street New York, New York 10007-1312 Ym oe RE: Perry Street Software, Inc. v. Jedi Technologies, Inc., ub 4 Case 1:20-cv-04539-CM (S.D.N.Y.) Lie [wv Dear Chief Judge McMahon: Perry Street Software, Inc. (“Perry”) seeks clarification regarding whether the Court’s October 14, 2020 Memorandum Decision and Order (ECF No. 49) (the “Order”) allows discovery concerning the arbitrability issue and whether the Order contemplates any further briefing. mr = □□ i ahh NAPS I. Arbitrability Discovery Is Appropriate = (,,) ) ; The Order concludes (at 15) by stating that the arbitration is stayed “pending full litigation of the request for a permanent injunction” which “requires the presentation of evidence—specifically, evidence about what Jedi’s lawyer did and why he did it[.]” The Order found that, because evidence was necessary, “the parties have 30 days to develop and submit evidence in support of the motion for a permanent injunction (stay) and the cross-motion to compel.”! (emphases added). Perry interpreted the Order—including the Order providing 30 days for the parties to “develop” and “submit” evidence—as allowing Perry to conduct discovery on issues of arbitrability. To that end, Perry wrote Jedi requesting certain discovery. See Ex. A (Per- ry’s letter). Jedi, however, refuses to provide any discovery. See Ex. B (Jedi’s response). The parties met and conferred by telephone on October 21, 2020, but could not reach any agreement. Perry respectfully submits that discovery is appropriate. In several places, the Or- der recognizes that the arbitrability issue is fact intensive. For example, the Order states, Jedi] fails to accompany [its] authority with the evidence that is needed to resolve what is ultimately a question of fact: what, exactly, was Jedi’s lawyer doing when he accessed 1 See also Order at 15 (“[F]Jor the next 30 days proceedings are limited to those nec- essary to flesh out the record on the pending motions.”); id. at 2 (“the parties [have] 30 days to complete the record”); id. at 3 (“for the next 30 days the parties are limited to fleshing out the record so that the court can finally decide the motion to compel”).

Case 1:20-cv-04539-CM Document 53 Filed 10/22/20 Page 2 of 4 The Honorable Colleen McMahon October 22, 2020 Page 2

SCRUFF and agreed to the TOS, and why was he doing it?” Id. at 2 (emphases added); id. at 12 (“This lack of evidence to support Jedi’s argument is in stark contrast to the facts in the cases it cites.”) (emphasis added); id. at 13 (“[T]he resolution of such factual ques- tions depends on the submission of evidence. That evidence is missing here.”) (emphases added). The Court’s Order specifically contemplates the parties developing and submit- ting evidence, and allows 30 days to obtain and submit such evidence. Contrary to Jedi’s reading of the Order, the Order does not provide that only Jedi would have the opportuni- ty to submit a declaration from its attorney (as Jedi has now done, see ECF No. 52) with- out subjecting itself to any discovery. Here, the evidence that the Court found necessary to resolve the arbitrability issue is uniquely in Jedi and its attorney’s possession—e.g., evidence concerning what Jedi au- thorized its attorney to do and why Jedi’s attorney signed up for Perry’s app and agreed to Perry’s Terms of Service. Order at, e.g., 10, 15. Courts recognize that discovery on the arbitrability issue is typically allowable or necessary. See, e.g., Lismore v. Societe Generale Energy Corp., 11-CV-6705, 2012 WL 3577833, at *1 (S.D.N.Y. Aug. 17, 2012) (“[ijn a typical motion to compel arbitration . .. some discovery may be allowable or necessary”); Accardo v. Equifax, Inc., 18-CV-5030, 2019 WL 5695947, at *6 (E.D.N.Y. Aug. 9, 2019) (same); Alvarez v. T-Mobile USA, Inc., 822 F. Supp. 2d 1081, 1085 (E.D. Cal. 2011) (“With respect to the first threshold issue, formation of an agreement, Alvarez is entitled to discovery.”); see also 9 U.S.C. § 4 (contemplating summary trial by court or jury where “the making of the arbitration agreement [is] in issue”). Accordingly, Perry seeks the deposition of Brian Haan (Jedi’s attorney who signed up for Perry’s app) and Jedi’s principal (Benjamin Baker). Perry also seeks limited catego- ries of documents relating to the key issues implicated by the Court’s Order. See Ex. A at 1-2 (requesting six categories of documents). The requested deposition of Mr. Haan will allow Perry to explore the statements in Mr. Haan’s recently filed declaration, including statements regarding Jedi’s retention of Mr. Haan’s law firm (ECF No. 52-1 7 4), whether Mr. Haan was conducting a Rule 11 in- vestigation to file a lawsuit (as opposed to an investigation to attempt to license Jedi’s patent on Jedi’s behalf) (id. J 11), what Jedi authorized Mr. Haan to do (id. J 11), wheth- er Mr. Haan created a “personal profile and account” as opposed to an account for Jedi (id.),2 and whether Mr. Haan had authority to agree to Perry’s Terms of Service on Jedi’s behalf (id. 14). The requested deposition of Mr. Baker (Jedi’s principal) will similarly develop evidence concerning Jedi’s actions—including what Jedi authorized Mr. Haan to do, what Jedi knew about Mr. Haan’s investigation, the purpose of Jedi’s pre-suit letter to Perry, and whether Jedi itself signed up for Perry’s app—and the Court will benefit from hearing from Jedi directly as presently no record evidence exists from Jedi. The documents Perry seeks will also shed light on the key factual questions impli- cated by the pending arbitrability motion. Jedi’s attorney-client retention agreement will 2 Mr. Haan did not use his own name when creating the account, but rather “jedis- cruff” —suggesting an investigation conducted on Jedi’s behalf. See ECF No. 38-1, Sil- verberg Decl. 7 12-13.

Case 1:20-cv-04539-CM Document 53 Filed 10/22/20 Page 3 of 4 The Honorable Colleen McMahon October 22, 2020 Page 3

show what Jedi authorized its attorneys to do on Jedi’s behalf; drafts of and communica- tions concerning Jedi’s pre-suit letter will shed light on whether Jedi contemplated litiga- tion as opposed to only licensing (the same is true regarding whether any pre-suit draft complaints exist); time sheets or invoices will presumably address the “litigation” v. “li- censing” issue; documentation regarding Perry’s apps would also bear on this issue; and other pre-suit communications sent by Jedi’s attorney to third parties will similarly show whether Jedi intended solely to license its patent (as it represented to Perry pre-suit)* or intended to bring a patent-infringement lawsuit. Jedi may argue that the requested discovery is privileged. But the requested dis- covery is either not privileged or Jedi waived any otherwise applicable privilege by sub- mitting Mr. Haan’s declaration. See, e.g., In re EchoStar Commce’ns Corp., 448 F.3d 1294, 1301 (Fed. Cir. 2006) (“[W]hen a party defends its actions by disclosing an attorney- client communication, it waives the attorney-client privilege as to all such communica- tions regarding the same subject matter.”); United States v. Bilzerian,

Perry Street Software, Inc. v. Jedi Technologies, Inc., (S.D.N.Y. 2020).

Perry Street Software, Inc. v. Jedi Technologies, Inc. (Perry Street Software, Inc. v. Jedi Technologies, Inc.) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

In Re Echostar Communications Corporation
448 F.3d 1294 (Federal Circuit, 2006)
United States v. Paul A. Bilzerian
926 F.2d 1285 (Second Circuit, 1991)
Alvarez v. T-MOBILE USA, INC.
822 F. Supp. 2d 1081 (E.D. California, 2011)