From Casetext: Smarter Legal Research

Swarmify, Inc. v. Cloudflare, Inc.

UNITED STATES DISTRICT COURT FOR THE NORTHERN DISTRICT OF CALIFORNIA
May 31, 2018
No. C 17-06957 WHA (N.D. Cal. May. 31, 2018)

Opinion

No. C 17-06957 WHA

05-31-2018

SWARMIFY, INC., Plaintiff, v. CLOUDFLARE, INC., Defendant.


ORDER ON MOTION TO STRIKE

INTRODUCTION

In this action for trade secret misappropriation, defendant moves to strike the latest list of asserted trade secrets that plaintiff disclosed pursuant to Section 2019.210 of the California Code of Civil Procedure. The motion is GRANTED IN PART and DENIED IN PART.

STATEMENT

The issue is a recurring one, the question of the extent to which a trade secrets plaintiff in a federal action may be permitted to adjust its list of asserted trade secrets after having obtained access to the files of the accused.

This is an action by plaintiff Swarmify, Inc., against defendant Cloudflare, Inc., for trade secret misappropriation and related state law claims. Swarmify fired the opening salvo in this action with a motion for a preliminary injunction. During briefing on that motion, Swarmify filed its original disclosure of six alleged trade secrets pursuant to Section 2019.210 of the California Code of Civil Procedure. The disclosure's contents and the complaint's allegations have been described in detail in a prior order dated February 27, which denied Swarmify's motion for a preliminary injunction based on failure to show likelihood of irreparable harm. Although it did not actually reach the merits, the February 27 order also discussed at length the "overbreadth of Swarmify's various and ever-shifting descriptions of its supposed trade secrets" and noted that "Swarmify's attempts to set up its purported trade secrets as elusive moving targets do not bode well for the merits of its claims" (see Dkt. No. 88 at 4-6).

After the dust settled on its motion for a preliminary injunction, Swarmify filed a new disclosure of five alleged trade secrets under Section 2019.210. Despite the fact that Swarmify had already made quicksand of its asserted trade secrets — a problem explicitly called out in the February 27 order — the new disclosure once again drastically overhauled its descriptions of the technology Cloudflare allegedly misappropriated. Cloudflare now moves to strike both the new disclosure and the deficient portions of Swarmify's original disclosure, protesting that Swarmify cannot "take a second bite at the apple" after losing at the preliminary injunction stage but obtaining valuable information about Cloudflare's litigation strategy and defenses (Dkt. No. 101). Swarmify responds that the new disclosure should be allowed because the February 27 order amounted to "an instruction to provide clarification on [Swarmify's] claimed trade secrets." If that was not the message of the February 27 order, Swarmify says, it would be "content to stand on its Original Disclosure" (Dkt. No. 107 at 2). Swarmify also insists it has not improperly used discovery to overhaul its Section 2019.210 disclosure and, in the alternative, seeks leave to amend its disclosure yet again (see id. at 13).

This order follows full briefing and oral argument.

ANALYSIS

Section 2019.210 provides:

In any action alleging the misappropriation of a trade secret under the Uniform Trade Secrets Act . . . before commencing discovery relating to the trade secret, the party alleging the misappropriation shall identify the trade secret with reasonable particularity.
The parties have offered no analysis or authority to explain whether or how this provision should apply where, as here, discovery has already commenced in a federal action, but it is a point worth clarifying. The plain text of Section 2019.210 does not contemplate this scenario. Our court of appeals has not spoken directly on the issue, but has cited with approval Universal Analytics v. MacNeal-Schwendler Corp., 707 F. Supp. 1170, 1177 (C.D. Cal. 1989) (Judge Stephen Victor Wilson), for the proposition that the plaintiff "should describe the subject matter of the trade secret with sufficient particularity to separate it from matters of general knowledge in the trade or of special knowledge of those persons skilled in the trade." Imax Corp. v. Cinema Techs., Inc., 152 F.3d 1161, 1164-65 (9th Cir. 1998). Universal Analytics, in turn, took that proposition from Diodes, Inc. v. Franzen, 260 Cal. App. 2d 244, 253 (1968), the "seminal decision" that became "the genesis of [S]ection 2019.210." Brescia v. Angelin, 172 Cal. App. 4th 133, 147 (2009). In other words, while Imax did not explicitly discuss Section 2019.210, it applied the core principle codified therein.

In doing so, Imax affirmed a district court's decision — after commencement of discovery — to grant summary judgment for the defendant on a trade secret misappropriation claim where the plaintiff had failed to identify its alleged trade secrets with sufficient particularity. See 152 F.3d at 1164-68. Consistent with this approach, judges in our district — including the undersigned judge — faced with deficient disclosures under Section 2019.210 have routinely entertained defense motions to defeat trade secret misappropriation claims after commencement of discovery, whether styled as a "motion to strike," "motion for summary judgment," or something else. See, e.g., Openwave Messaging, Inc. v. Open-Xchange, Inc., 2018 WL 692022, at *4 (N.D. Cal. Feb. 2, 2018) (Judge William Orrick) (examining adequacy of Section 2019.210 disclosure on motion for summary judgment); BladeRoom Grp. Ltd. v. Facebook, Inc., 2018 WL 514923, at *3-5 (N.D. Cal. Jan. 23, 2018) (Judge Edward Davila) (same); Waymo LLC v. Uber Techs., Inc., 2017 WL 5000352, at *7-9 (N.D. Cal. Nov. 2, 2017) (Judge William Alsup) (granting overlapping motions to strike and for summary judgment on trade secret misappropriation claim); Jobscience, Inc. v. CVPartners, Inc., 2014 WL 1724763, at *2-4 (N.D. Cal. May 1, 2014) (Judge William Alsup) (granting motion to strike and dismissing trade secret misappropriation claim) (Jobscience I); Art of Living Found. v. Does 1-10, 2012 WL 1565281, at *23 (N.D. Cal. May 1, 2012) (Judge Lucy Koh) (inviting motion for summary judgment on trade secret misappropriation claim).

Insofar as controlling law on this subject remains ambiguous, district courts may also exercise discretion in case management to enforce Section 2019.210, and the undersigned judge has in fact done so. See, e.g., Jobscience, Inc. v. CVPartners, Inc., 2014 WL 852477, at *4-5 (N.D. Cal. Feb. 28, 2014) (Jobscience II). Approaching the issue as one of case management also works well because, technicalities aside, Section 2019.210 ultimately aims to address practical problems that tend to arise in trade secret litigation. See Advanced Modular Sputtering, Inc. v. Superior Court, 132 Cal. App. 4th 826, 835 (2005) ("[T]he law is flexible enough for the referee or the trial court to achieve a just result depending on the facts, law, and equities of the situation."). Among other things, it "promotes well-investigated claims and dissuades the filing of meritless trade secret complaints," "prevents plaintiffs from using the discovery process as a means to obtain the defendant's trade secrets," and "enables defendants to form complete and well-reasoned defenses." Id. at 833-34. "Experience has shown that it is easy to allege theft of trade secrets with vagueness, then take discovery into the defendants' files, and then cleverly specify what ever happens to be there as having been trade secrets stolen from plaintiff." Jobscience I, 2014 WL 1724763, at *2.

The foregoing practical concerns bear on the instant motion. First, Swarmify should not be allowed to drag Cloudflare into court based on meritless arguments, only to reboot its alleged trade secrets lineup and try again when the opening skirmish illuminates glaring flaws in Swarmify's case. Second, Swarmify represents that it has not used information gained in discovery to redefine its alleged trade secrets, and Section 2019.210 draws the line at "discovery." But even if that representation could be relied upon, redefining alleged trade secrets based on information gained by moving for a preliminary injunction, thereby forcing the accused to disclose the details of its technology and defenses, raises a similar concern of abuse. Third, Swarmify's bait-and-switch tactic prejudices Cloudflare, which invested significant time, effort, and legal strategy in opposing Swarmify's motion for a preliminary injunction but must now rebuild its defenses to react to Swarmify's new disclosure, having already shown much of its hand to the opposing side. These concerns all indicate that Swarmify's new disclosure should not be permitted — at least, not without consequence.

On the other hand, the new disclosure as a whole has not become so unmoored from the core technology described in the original disclosure that this action, which remains in its early stages, would become unsalvageable if allowed to proceed. Moreover, another practical advantage unique to post-discovery enforcement of Section 2019.210 has also become particularly germane to our case.

Gamesmanship, even if well-disguised at the outset, tends to come into clearer focus as litigation progresses. For example, it becomes easier to pinpoint how vaguely-alleged trade secrets may have functioned as moving targets, and how the plaintiff may have taken advantage of the shifting sands of litigation to evade counterarguments. These developments may cast the unreasonableness of the initial disclosure into sharp relief in light of how the alleged trade secrets evolved over time. In such cases, a plaintiff that merely postpones reckoning with Section 2019.210 early on may eventually find that the consequences of their evasions come home to roost in the form of an adverse ruling on the entire trade secret misappropriation claim. See, e.g., Waymo, 2017 WL 5000352, at *7-9. As the February 27 order foreshadowed, Swarmify has already gone quite a ways down this path.

After weighing the foregoing factors, this order holds that Swarmify may proceed on its new disclosure if it so chooses. To proceed on the new disclosure, however, Swarmify must follow three conditions. First, the new disclosure would be the final definition of Swarmify's alleged trade secrets for this case. No further amendments would be permitted. Cloudflare, however, would still be able to reference the original disclosure in its arguments — for example, to show the jury the shifting-sands nature of Swarmify's case. Second, Swarmify would pay Cloudflare its reasonable attorney's fees for defending the motion for a preliminary injunction premised on a defunct list of alleged trade secrets. Third, Cloudflare would be entitled to additional expedited discovery, including repeat depositions if necessary, to rebuild its defenses with the new disclosure in mind.

By JUNE 7 AT NOON, Swarmify shall file and serve a statement electing to either proceed on its new disclosure on the conditions set forth above or instead stand on its earlier trade secret disclosure. There must be no equivocations or caveats. All appellate rights, of course, shall be reserved as to both sides.

CONCLUSION

For the foregoing reasons, defendant's motion to strike is GRANTED IN PART and DENIED IN PART.

IT IS SO ORDERED. Dated: May 31, 2018.

/s/_________

WILLIAM ALSUP

UNITED STATES DISTRICT JUDGE


Summaries of

Swarmify, Inc. v. Cloudflare, Inc.

UNITED STATES DISTRICT COURT FOR THE NORTHERN DISTRICT OF CALIFORNIA
May 31, 2018
No. C 17-06957 WHA (N.D. Cal. May. 31, 2018)
Case details for

Swarmify, Inc. v. Cloudflare, Inc.

Case Details

Full title:SWARMIFY, INC., Plaintiff, v. CLOUDFLARE, INC., Defendant.

Court:UNITED STATES DISTRICT COURT FOR THE NORTHERN DISTRICT OF CALIFORNIA

Date published: May 31, 2018

Citations

No. C 17-06957 WHA (N.D. Cal. May. 31, 2018)

Citing Cases

Wisk Aero LLC v. Archer Aviation Inc.

See id.; see also Swarmify, Inc. v. Cloudflare, Inc., No. C 17-06957 WHA, 2018 WL 2445515, at *2…

Coast Hematology-Oncology Assocs. Med. Grp. v. Long Beach Mem'l Med. Ctr.

(Cf. Swarmify, Inc. v. Cloudflare, Inc. (N.D.Cal. May 31, 2018, No. C 17-06957 WHA) 2018 WL 2445515 at *2,…