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

CourtDistrict Court, S.D. New York
DecidedOctober 14, 2020
Docket1:20-cv-04539
StatusUnknown

This text of Perry Street Software, Inc. v. Jedi Technologies, Inc. (Perry Street Software, Inc. v. Jedi Technologies, Inc.) is published on Counsel Stack Legal Research, covering District Court, S.D. New York primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

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

Opinion

UNITED STATES DISTRICT COURT SOUTHERN DISTRICT OF NEW YORK __________________________________________

PERRY STREET SOFTWARE, INC.,

Plaintiff,

-against- No. 20-cv-04539 (CM)

JEDI TECHNOLOGIES, INC.

Defendants. __________________________________________

MEMORANDUM DECISION AND ORDER GRANTING MOTION FOR PRELIMINARY INJUNCTION, DEFERRING ACTION ON THE MOTION TO COMPEL ARBITRATION, DENYING MOTION TO STRIKE CERTAIN PORTIONS OF THE ANSWER, DENYING MOTION TO STAY PROCEEDINGS, AND SETTING A SCHEDULE FOR FURTHR PROCEEDINGS

McMahon, C.J.:

The underlying dispute between the parties to this lawsuit concerns Defendant Jedi’s allegation that a product of Plaintiff’s, known as SCRUFF (an online-dating app), infringes on one of Jedi’s patents. The cross motions presently before this Court concern whether that underlying dispute will be litigated or whether it – or at least some preliminary issues – will be arbitrated. Plaintiff Perry Street contends that Defendant Jedi has agreed to arbitrate any claims it might assert against Perry Street, because Jedi’s lawyer – who downloaded SCRUFF during the run-up to this lawsuit and thereby consented to be bound by SCRUFF’s Terms of Service (TOS) – agreed to a mandatory arbitration clause. It has, therefore, noticed an arbitration against Jedi. Jedi asserts that it never agreed to be bound by any Terms of Service, and that its lawyer’s actions did not and could not manifest Jedi’s assent to those Terms of Service (including the arbitration clause) – this is because the lawyer did what he did in order to satisfy his personal obligation under Fed. R. Civ. P. 11. Jedi has moved for a “preliminary” injunction against the arbitration that Perry Street has noticed. But there is nothing “preliminary” about the relief that Jedi seeks – it wants a permanent

stay of arbitration, so that the patent-infringement suit can be litigated in court. However, while Jedi cites persuasive authority for the proposition that its lawyer’s agreement to the TOS did not manifest Jedi’s assent to arbitration, it fails to accompany that 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 SCRUFF and agreed to the TOS, and why was he doing it? Despite the lack of an affidavit from Jedi’s lawyer, I conclude that Defendant is likely to succeed on the merits of what is, ultimately, an application for a stay of arbitration. And Jedi has unquestionably satisfied the other conditions for the entry of injunctive relief. For that reason, I am granting its motion for a preliminary injunction, deferring action on Perry Street’s motion to compel arbitration, and giving the parties 30 days to complete the record.

Jedi has also raised (albeit in a perfunctory way) the possibility that Perry Street has waived arbitration. Perry Street filed the complaint in this action, seeking a declaration that it did not infringe Jedi’s patent. That action would appear to be at odds with its present position that the matter should be arbitrated. Moreover, the record reveals two highly salient facts that would seem to bear on the waiver issue: (1) unlike many “broad” arbitration clauses, the dispute resolution clause in the TOS specifically permits any party to opt to litigate, rather than arbitrate, intellectual property disputes, at least when seeking some form of equitable relief; and (2) at the time it opted to litigate, Perry Street had available to it all the information from which it would eventually argue that the matter was arbitrable. Unfortunately, the parties failed to brief this issue adequately. If Jedi chooses to pursue the issue of waiver, it can be dealt with when the motion to compel is finally decided. There are two other motions to be decided: Jedi’s motion to strike certain statements from Perry Street’s answer to its counterclaim, and Perry Street’s motion to stay proceedings pending

resolution of its motion to compel. Both motions are denied – although 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. BACKGROUND A. The Parties

The facts pertinent to the various motions are not in dispute. Plaintiff Perry Street Software, Inc. (“Perry Street”) is a company incorporated and headquartered in New York. Perry Street makes mobile applications (“apps”), including SCRUFF, and Jack’d, two online-dating apps that run on the iOS and Android platforms. Defendant Jedi Technologies, Inc. (“Jedi”) is an Arizona-based corporation that holds Patent No. 10,164,918 (the “’918 Patent”) from the United States Patent and Trademark Office (“USPTO”). Jedi accuses the SCRUFF app of infringing the ’918 Patent. B. The SCRUFF App and Its Terms of Service Every user who downloads SCRUFF encounters a series of screens when he or she first signs up for the service. The app’s first default screen prompts the user to either “SIGN IN” or “CREATE” an account, with each option contained in its own large box displayed side by side at the bottom of the screen. (Dkt. No. 38, pg. 3). Below these two options is a statement in small white text that

reads: “Privacy, safety and security are our top priority. Please review the following documents regarding our rules and your rights:” Immediately below that statement are two blue hyperlinks: one to a “Privacy Policy” and the other to “Terms of Service.” When a prospective SCRUFF user clicks on one of these two hyperlinks, s/he is taken to that document. However, a new SCRUFF user does not need to click on either of the hyperlinks to proceed to the next screen; s/he can skip

over reviewing these documents by clicking on the “CREATE” button. (Ibid.). On the next screen, the user is asked, “When is your birthday?” in large white text, and is prompted to enter his or her date of birth by scrolling through options to find the correct month, date, and year. (Id. at 4). The screen also includes a large blue box with the word “NEXT” written inside in white text. Above the box is the following statement in small font: “By tapping Next, you agree to our Privacy Policy and Terms of Service.” The words “Privacy Policy” and “Terms of Service” are once again blue hyperlinks to the respective agreements, while the rest of the statement is printed in white. As was true of the previous screen, a prospective SCRUFF user does not need to click on the hyperlinks to proceed to the next screen or to receive access to the app; s/he can elect not to read the Privacy Policy or the TOS and proceed by clicking the “NEXT” box.

But by doing so, s/he is deemed to have assented to the terms of both agreements. The hyperlinks to SCRUFF’s “Privacy Policy” and “Terms of Service” are known in the industry as “browsewrap” agreements – agreements “which generally post terms and conditions on a website via a hyperlink at the bottom of the screen” and which “do not require the user to expressly assent.” Meyer v. Uber Tech., Inc., 868 F.3d 66, 75 (2d Cir. 2017). These “browsewrap” agreements can be contrasted with “clickwrap” agreements, which “require users to click an ‘I agree’ box after being presented with a list of terms and conditions[.]” Ibid. SCRUFF’s Terms of Service (“TOS”) include the following provisions which are relevant to the current dispute: THESE TERMS OF SERVICE REQUIRE BINDING ARBITRATION TO RESOLVE ANY DISPUTE OR CLAIM ARISING OUT OF OR RELATING IN ANY WAY TO THESE TERMS OR YOUR ACCESS TO OR USE OF THE SERVICE (AS DEFINED BELOW . . . .

17. BINDING ARBITRATION AND CLASS ACTION WAIVER

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

Related

Ameriprise Financial Services, Inc. v. Beland
672 F.3d 113 (Second Circuit, 2011)
Bensadoun v. Jobe-Riat
316 F.3d 171 (Second Circuit, 2003)
Merrill Lynch Investment Managers v. Optibase, Ltd.
337 F.3d 125 (Second Circuit, 2003)
HIGHLAND CAPITAL MANAGEMENT LP v. Schneider
607 F.3d 322 (Second Circuit, 2010)
Conway v. City of Kenosha, Wisconsin
409 F. Supp. 344 (E.D. Wisconsin, 1975)
Rex Medical L.P. v. Angiotech Pharmaceuticals (US), Inc.
754 F. Supp. 2d 616 (S.D. New York, 2010)
Henry Schein, Inc. v. Archer & White Sales, Inc.
586 U.S. 63 (Supreme Court, 2019)
Antonious v. Spalding & Evenflo Companies, Inc.
275 F.3d 1066 (Federal Circuit, 2002)
Meyer v. Uber Technologies, Inc.
868 F.3d 66 (Second Circuit, 2017)

Cite This Page — Counsel Stack

Bluebook (online)
Perry Street Software, Inc. v. Jedi Technologies, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/perry-street-software-inc-v-jedi-technologies-inc-nysd-2020.