Quest Solution v. Redlpr LLC

CourtDistrict Court, D. Utah
DecidedApril 28, 2021
Docket2:19-cv-00437
StatusUnknown

This text of Quest Solution v. Redlpr LLC (Quest Solution v. Redlpr LLC) is published on Counsel Stack Legal Research, covering District Court, D. Utah primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Quest Solution v. Redlpr LLC, (D. Utah 2021).

Opinion

IN THE UNITED STATES DISTRICT COURT DISTRICT OF UTAH

QUEST SOLUTION, INC.; HTS IMAGE Case No. 2:19-cv-437-CW-DBP PROCESSING, INC.; HTS (USA) INC.,

Plaintiffs, MEMORANDUM DECISION AND ORDER v.

REDLPR, LLC; SAGY AMIT; JEREMY Judge Clark Waddoups BARKER; RIVERLAND TECHNOLOGIES LLC,

Defendants

HTS (USA) Inc. (“HTS”)1 develops and deploys license plate recognition technology (“LPR”) at international airports, shopping centers, and so forth—both in the United States and in other nations. Defendants Sagy Amit and Jeremy Barker are former employees of HTS who resigned their employment and established RedLPR, LLC as a competing business. HTS contends the defendants2 misappropriated trade secrets when they left and have harmed HTS due to the defendants use of such trade secrets. HTS also asserts claims for breach of fiduciary duty, tortious interference with economic relations, unjust enrichment, unfair competition, and breach of implied covenant of good faith and fair dealing (collectively “Non-Trade Secret Claims”).

1 A dispute exists between the parties about whether Quest Solution, Inc. and HTS Image Processing, Inc. are proper plaintiffs. Until the issue is resolved, the court’s reference to HTS refers only to HTS (USA) Inc.

2 Riverland Technologies LLC is not part of the present motions before the court. Accordingly, in this decision, the term “the defendants” refers only Sagy Amit, Jeremy Barker, and RedLPR, Defendants move for summary judgment on HTS’ claims. HTS asserts summary judgment is premature because the parties are still engaged in fact discovery. It moves under Rule 56(d) of the Federal Rules of Civil Procedure for summary judgment to be denied on the ground that further discovery is needed. Multiple motions also have been filed about whether certain documents, contentions, and legal arguments should be sealed. Such motions have gone through various iterations due to arguments raised by the parties. Based on the present record before the court, it denies without prejudice Defendants’ motion for summary judgment. Nevertheless, it orders HTS to identify with more particularity the trade secrets that are at issue. It grants the Rule 56(d) motion and directs that certain documents

shall remain under seal until otherwise directed by the court. ANALYSIS I. TRADE SECRETS A. Particularity Requirements HTS asserts claims under the federal Defend Trade Secrets Act and the Utah Uniform Trade Secrets Act. “Most forms of intellectual property have boundaries that are defined before the commencement of litigation.” TLS Mgmt. & Mktg. Srvs., LLC v. Rodriguez-Toledo, 966 F.3d 46, 51 (1st Cir. 2020). This is so even if there is a dispute about the scope of those boundaries. Id. “Trade secrets are different. There is no requirement of registration and, by definition, there

is no public knowledge of the trade secret in advance of litigation.” Id. at 51–52. Because of the unique aspects of trade secrets, it “raises the possibility that the trade secret owner will tailor the scope of the trade secret in litigation to conform to the litigation strategy.” Id. at 52. A defendant may face an ever-changing field where goal posts are moved, positions are altered, and defenses cannot be developed because a trade secret claim remains amorphous. See Next Commc’ns, Inc. v. Viber Media, Inc., 758 F. App’x 46, 49 (2d Cir. 2018) (stating plaintiff had “described its trade secret differently at each stage of the litigation”). To address these challenges, Federal courts typically require identification of a trade secret with reasonable particularity or sufficient definiteness, so the defendant and the court know what issues are before them. See e.g., InteliClear, LLC v. ETC Global Holdings, Inc., 978 F.3d 653, 658 (9th Cir. 2020) (requiring trade secret to be identified with sufficient particularity “because defendants need concrete identification to prepare a rebuttal” and “[c]ourts and juries also require precision” because they lack the “requisite expertise to define what the plaintiff leaves abstract”) (quotations and citation omitted)); Next Commc’ns, Inc., 758 F. App’x at 48 (stating “a party must

describe the trade secret with specific and concrete information”) (quotations and citations omitted)); Storagecraft Tech. Corp. v. Symantec Corp., No. 2:07-cv-856, 2009 U.S. Dist. LEXIS 10608, at *7 (D. Utah Feb. 11, 2009) (stating “the reasonable particularity standard requires that the alleged trade secret be described ‘with adequate specificity to inform the defendants what it is alleged to have misappropriated”) (quotations, citations, and alteration omitted)). Utah applies a different approach. The Utah Supreme Court has held that Utah’s trade secret statute does not have a “particularity” requirement. USA Power, LLC v. PacifiCorp., 2016 UT 20, ¶ 48, 372 P.3d 629, 649. Thus, a plaintiff is “not required to identify its trade secret with particularity,” id. ¶ 47, before discovery may be had on the issue. Nevertheless, the statute does

require a “fact-finder to know what it is that the plaintiff claims is not generally known or readily ascertainable.” Id. ¶ 48. The plaintiff “bear[s] the burden of defining its purported trade secret in a manner that would allow the fact-finder to determine if it met the statutory requirements.” Id. ¶ 49 (citing Utah Med. Prods., Inc. v. Clinical Innovations Assocs., Inc., 79 F. Supp. 2d 1290, 1313 (D. Utah 1999) (requiring plaintiff to “define its claimed trade secret with the precision and particularity necessary to separate it from the general skill and knowledge possessed” by one skilled in the art)). Whether one applies a reasonable-particularity requirement for identification purposes, or so one may distinguish a claimed trade secret from the general skills and knowledge possessed by others in the art, a plaintiff bears the burden to define the claimed trade secret sufficiently for discovery to be meaningful, for boundaries to be known, and for the fact-finder to understand what is to be decided. B. Guidelines for Identifying a Trade Secret Because the standard is reasonable particularity versus absolute definiteness, the question

become what is enough? Although trade secret identification is not susceptible to a “talismanic procedure,” Storagecraft Tech. Corp., 2009 U.S. Dist. LEXIS 10608, at *6 (quotations and citation omitted), the court sets forth some guidelines here. “It is inadequate for plaintiffs to cite and incorporate by reference hundreds of documents that purportedly reference or reflect the trade secret information.” InteliClear, LLC, 978 F.3d at 658 (quotations and citation omitted). It also is inadequate to describe a trade secret in broad, general terms. The length of a document does not determine its adequacy. In IDX Systems Corp. v. Epic Systems Corp., 285 F.3d 581, 583 (7th Cir. 2002), the Court addressed whether the plaintiff had adequately identified the claimed trade secrets. The plaintiff

asserted “a 43-page description of the methods and processes underlying and the inter- relationships among various features making up IDX’s software package” sufficiently identified the trade secret. Id. The Court disagreed because the information was “too vague” on the one hand and “too inclusive” on the other. Id. IDX effectively asserted “that all information in or about its software [was] a trade secret.” Id.

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
Quest Solution v. Redlpr LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/quest-solution-v-redlpr-llc-utd-2021.