Bartech Systems International, Inc. v. Mobile Simple Solutions, Inc. et al

Filing 290

ORDER granting Plaintiff's ECF No. 247 Amended Motion to Strike "Attorneys' Eyes Only" Designation From Source Code. Signed by Magistrate Judge Nancy J. Koppe on 4/19/2017. (Copies have been distributed pursuant to the NEF - KR)

Download PDF
1 2 3 4 5 6 7 UNITED STATES DISTRICT COURT 8 DISTRICT OF NEVADA 9 10 11 12 13 14 BARTECH SYSTEMS INTERNATIONAL, INC., ) ) Plaintiff(s), ) ) vs. ) ) MOBILE SIMPLE SOLUTIONS, INC., et al., ) ) Defendant(s). ) ) Case No. 2:15-cv-02422-MMD-NJK ORDER (Docket No. 247) 15 Pending before the Court is Plaintiff’s amended motion to strike “attorneys’ eyes only” 16 designation from source code in favor of the designation “confidential” pursuant to the amended 17 stipulated protective order. Docket No. 247. Defendant Vincent Tessier filed a response, and 18 Plaintiff filed a reply. Docket Nos. 259, 270. The Court finds his motion properly resolved without 19 oral argument. See Local Rule 78-1. For the reasons discussed below, Plaintiff’s motion, Docket 20 No. 247, is hereby GRANTED. 21 I. BACKGROUND 22 This action was initially removed from state court on December 18, 2015. Docket No. 1. 23 Before removal, the parties filed a stipulated protective order in the state court action. Docket No. 24 247-5. Defendants Tessier and Christelle Pigeat subsequently moved for a protective order that, 25 inter alia, would include an attorneys’ eyes only (“AEO”) provision that would apply to the source 26 code for ABreez, a product sold by their company, Mobile Simple Solutions (IAS), Inc. (“Mobile 27 Simple”). Docket No. 247-3. Plaintiff opposed that motion. Docket No. 247-6. The state court 28 ultimately held a hearing, granted Defendants’ motion in part, and ordered that all source code must 1 be provided enhanced protection. Docket No. 247-7. The parties then negotiated a blanket 2 protective order, including an AEO provision to be applied to the source code, which the state court 3 entered on August 19, 2015. Docket No. 247-8 at 5-22. The parties subsequently exchanged source 4 code subject to the AEO provision of the stipulated protective order. Docket Nos. 247-9, 247-10. 5 On September 28, 2016, unbeknownst to Bartech, Defendant Mobile Simple sold the ABreez 6 source code. See, e.g., Docket No. 247 at 7. On February 3, 2017, after discovering the sale, 7 Plaintiff filed a motion to strike the AEO designation from the source code in favor of the 8 designation “confidential” pursuant to the parties’ amended stipulated protective order. Docket No. 9 218. On February 14, 2017, the Court stayed this action as to Defendant Pigeat. Docket No. 232. 10 On March 10, 2017, the Court denied without prejudice Plaintiff’s motion to strike because it was 11 filed before the Court stayed the case as to Defendant Pigeat. Docket No. 241. The Court allowed 12 Plaintiff to file a renewed motion to strike that addresses how the stay as to Defendant Pigeat affects 13 the relevant issues. Id. 14 On March 17, 2017, Plaintiff filed the instant motion. Docket No. 247. Plaintiff submits that 15 the stay as to Defendant Pigeat does not impact its motion to strike because, inter alia, Defendant 16 Pigeat no longer has an interest in the ABreez source code since her company sold it. Id. at 3-4. 17 Defendant Tessier does not appear to contest this assertion, though he apparently purports to speak 18 on behalf of both himself and Defendant Pigeat. See, e.g., Docket No. 259 at 2 (“Although Tessier 19 and Miss Pigeat are no longer administrators and co-owners of Mobile Canada . . . they nevertheless 20 want to protect the logic on how ABreez Software was developed”). Having independently reviewed 21 Plaintiff’s analysis on this issue, the Court finds that, as Plaintiff submits, the stay as to Defendant 22 Pigeat does not affect the instant motion. The Court therefore addresses the substance of the motion 23 below. 24 25 26 27 28 2 1 II. ANALYSIS 2 As a preliminary matter, the Court may properly adopt and apply the parties’ stipulated 3 protective order, though it was issued by a state court. After removal, “[t]he federal court treats 4 everything that occurred in the state court as if it had taken place in federal court.” Carvalho v. 5 Equifax Info. Servs., LLC, 629 F.3d 876, 887 (9th Cir. 2010) (internal quotation marks and 6 alterations omitted) (quoting Butner v. Neustadter, 324 F.2d 783, 785 (9th Cir. 1963)). Therefore, 7 “an order entered by a state court should be treated as though it had been validly rendered in the 8 federal proceeding.” Carvalho, 629 F.3d at 887 (internal quotation marks omitted) (quoting Butner, 9 324 F.2d at 785). Additionally, this Court retains the “authority to dissolve or modify a state court 10 order that was entered prior to removal.” Kogok v. T-Mobile USA, Inc., 2013 WL 1942211, at *1 11 (S.D. Cal. May 9, 2013) (citing 28 U.S.C. § 1450). The Court therefore adopts the protective order 12 entered in the state court case and treats it as though it had been rendered in this Court. 13 Plaintiff submits that this Court should designate the ABreez source code “confidential” 14 rather than applying the AEO provision to it in order to facilitate better preparation for trial. Docket 15 No. 247 at 11-12. In particular, Plaintiff submits that “Defendant Tessier has an unfair advantage 16 at trial due to his extensive personal knowledge of Bartech’s source code, whereas neither Bartech 17 nor its employees have any familiarity with the ABreez code.” Id. at 11. Plaintiff contends that 18 removing the AEO designation in favor of a “confidential” designation would improve its ability to 19 trace Defendants’ alleged misappropriation of its own source code. Id. at 11-12. Plaintiff further 20 asserts that this Court may properly change the designation because the initial rationale underlying 21 the application of the AEO provision to the ABreez source code no longer applies. Id. at 5-7, 9, 12. 22 Specifically, Plaintiff submits, in the state court litigation, Defendants submitted that revealing the 23 ABreez source code to Plaintiff’s employees “would destroy Defendants’ competitive advantage” 24 absent “a prima facie showing that this information was misappropriated or otherwise belongs to 25 [Plaintiff].” Docket No. 247-3 at 5 (italics not in original). At this point in the litigation, however, 26 Plaintiff submits that Defendants have sold the source code, and that the Court has found that 27 28 3 1 “[Plaintiff] is . . . likely to succeed on the merits of its misappropriation claim.” See, e.g., Docket 2 No. 247 at 5; Docket No. 96 at 15. Plaintiff also submits that the ABreez source code would still 3 enjoy sufficient protection if designated “confidential,” and that Plaintiff would agree to also have 4 its own source code designated “confidential.” Docket No. 247 at 5, 7-8. 5 Defendant Tessier responds that, though he no longer owns ABreez, he “still want[s] to 6 protect the logic on how ABreez Software was developed.” Docket No. 259 at 2. Defendant Tessier 7 also submits that Plaintiff has improper motives in seeking to remove the AEO protection from the 8 ABreez source code. Id. at 3-6. Defendant Tessier further contends that Plaintiff’s counsel have 9 already had the source code in their possession for quite some time and that Plaintiff should be able 10 to continue its investigation through experts. Id. at 6. Plaintiff replies that the Abreez source code 11 will remain amply protected as “confidential” under the stipulated protective order, that one of this 12 Court’s prior orders supports granting the relief Plaintiff requests, and that known facts disprove 13 Defendant Tessier’s contention about Plaintiff’s motives. Docket No. 270 at 3-6. 14 The Court agrees with Plaintiff. Defendant Tessier no longer possesses any interest in the 15 ABreez source code because his company sold it. See, e.g., Docket No. 247 at 5. Moreover, aside 16 from conclusory assertions about Plaintiff’s motives, Defendant Tessier has not explained how 17 designating the source code as “confidential” rather than applying the AEO provision to it would 18 harm him. See, e.g., Beckman Indus., Inc. v. Int’l Ins. Co., 966 F.2d 470, 476 (9th Cir. 1992) 19 (internal citation omitted) (“‘Broad allegations of harm, unsubstantiated by specific examples or 20 articulated reasoning,’” are insufficient to show good cause for protection under Rule 26(c)); see also 21 Wells Fargo Bank, N.A. v. Iny, 2014 U.S. Dist. Lexis 78875, at *8 (D. Nev. June 9, 2014) (internal 22 citation omitted) (“When a confidentiality designation is challenged, the burden of persuasion to 23 show good cause for such a designation rests upon the designating party”). Additionally, Defendant 24 Tessier provides no authority that would require the Court to apply the AEO designation to the 25 source code. See Local Rule 7-2(d) (“The failure of an opposing party to file points and authorities 26 in response to any motion,” absent an exception not applicable here, “constitutes a consent to the 27 28 4 1 granting of the motion”). Thus, the Court is not persuaded that it is necessary to apply the AEO 2 provision of the stipulated protective order to the Abreez source code. 3 III. CONCLUSION 4 For the reasons discussed above, Plaintiff’s amended motion to strike “Attorneys’ Eyes Only” 5 designation, Docket No. 247, is hereby GRANTED. The source code at issue in this case no longer 6 falls under the AEO provision of the parties’ stipulated protective order, and is instead designated 7 “confidential.” 8 IT IS SO ORDERED. 9 DATED: April 19, 2017. 10 ___________________________________ NANCY J. KOPPE United States Magistrate Judge 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 5

Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.

Why Is My Information Online?