Neiferd v. Microsoft Corporation

• Court: District Court, W.D. Washington
• Decided: September 30, 2025
• Docket: 2:25-cv-00327
• Status: Unknown

Opinion

1 2 3 4

5 UNITED STATES DISTRICT COURT 6 WESTERN DISTRICT OF WASHINGTON AT SEATTLE 7 8 JARED MICHAEL NEIFERD, 9 Plaintiff, Case No. C25-327-MLP 10 v. ORDER 11 MICROSOFT CORPORATION, et al., 12 Defendants. 13

14 I. INTRODUCTION 15 Before the Court is Defendants Microsoft Corporation and Richmond Vlong Baker’s 16 (collectively “Defendants”) Motion for a Protective Order. (Mot. (dkt. # 42).) Plaintiff Jared 17 Michael Neiferd, proceeding pro se, has responded (Resp. (dkt. # 45)), and Defendants have 18 replied (Reply (dkt. # 47)). Having reviewed those filings, the supporting materials, and the 19 governing law, the Court GRANTS Defendants’ Motion. The Court’s reasoning follows. 20 II. BACKGROUND 21 This action concerns Mr. Neiferd’s claims that his former employer unlawfully 22 discriminated and retaliated against him by eliminating his position in 2023. (Dkt. # 2 at 1-20.) 23 Defendants have denied these allegations. (Dkt. # 25.) During discovery, Mr. Neiferd produced 1 performance evaluations, referred to as “Connects,” and similar documents. (First Loberstein 2 Decl. (dkt. # 43), ¶ 2.) These documents were also used as exhibits during his deposition. (Id., ¶ 3 4.) 4 Defendants assert that the “Connects” contain confidential and non-public information

5 warranting protection. (Baker Decl. (dkt. # 44), ¶ 4.) As examples, they identify information 6 concerning customer outages and vulnerabilities, specific code, customer relationships, internal 7 revenue and utilization targets, and detailed planning strategies. (Mot. at 4.) Defendants assert 8 that public dissemination of this information would irreparably harm their business and 9 customers. (Id.) 10 On March 12, 2025, Defendants proposed a stipulated protective order referencing the 11 Court’s Model Order. This proposal included provisions designed to protect the confidentiality 12 of the “Connects” and similar documents. (First Loberstein Decl., ¶ 3; id., Ex. A.) Mr. Neiferd 13 objected to Defendants’ definition of “Confidential Material,” advocating for a narrower scope 14 limited to legally protected information, personally identifiable information, trade secrets, and

15 medical records. (Neiferd Decl. (dkt. # 46), ¶ 4; First Loberstein Decl., ¶¶ 4-5; id., Exs. B-C.) 16 Defendants rejected these proposed limitations (id., ¶ 6), and subsequent discussions failed to 17 resolve the dispute, leading to the present motion (id., ¶¶ 7-10). 18 III. DISCUSSION 19 “Rule 26(c) confers broad discretion on the trial court to decide when a protective order 20 is appropriate and what degree of protection is required.” Seattle Times Co. v. Rhinehart, 467 21 U.S. 20, 36 (1984). The party seeking a protective order under Rule 26(c) must establish “good 22 cause,” demonstrating that specific prejudice or harm will result if the order is not granted. In re 23 1 Roman Cath. Archbishop of Portland in Oregon, 661 F.3d 417, 424 (9th Cir. 2011) (citing Foltz 2 v. State Farm Mut. Auto. Ins. Co., 331 F.3d 1122, 1130 (9th Cir. 2003)). 3 This dispute concerns the appropriate scope of the “Confidential Material” definition. 4 Defendants seek a broad definition encompassing internal revenue targets, customer relationship

5 details, and vulnerability information, arguing that public dissemination could cause harm. (See 6 Mot. at 6-8; Reply at 2-6; see also dkt. # 43-1 at 48-49.) Conversely, Mr. Neiferd seeks a 7 narrower definition focused on legally protected information, trade secrets, and personally 8 identifiable data, excluding general business policies, personnel decisions absent trade secrets, 9 and publicly available documents. (See Resp. at 4-8; see also dkt. # 43-1 at 20-21.) 10 Defendants have demonstrated good cause for a protective order. Courts routinely 11 recognize the need to protect trade secrets or other confidential research, development, or 12 commercial information. See, e.g., Phillips ex rel. Estates of Byrd v. Gen. Motors Corp., 307 13 F.3d 1206, 1211 (9th Cir. 2002) (holding that protective orders are appropriate to safeguard trade 14 secrets and other confidential commercial information); WATM LLC v. Payment Alliance Int’l,

15 Inc., 2025 WL 1677558, at *1-2 (W.D. Wash. Apr. 11, 2025) (same); Lauer v. Longevity Med. 16 Clinic PLLC, 2014 WL 5471983, at *7 (W.D. Wash. Oct. 29, 2014) (noting the need to protect 17 sensitive personnel information, “including of persons not party to this lawsuit”). Further, 18 disclosure of reports of protected activity can result in substantial harm or embarrassment to 19 employees. See Delaittre v. Berryhill, 2017 WL 6310483, at *7 (W.D. Wash. Dec. 11, 2017). 20 Moreover, in April 2017, as a condition of his employment, Mr. Neiferd executed an 21 agreement concerning confidential information. (Dkt. # 28, Ex. A.) This agreement defined 22 “Confidential Information” broadly, as data relating to Defendants’ business, technology, or 23 1 finances not generally known to the public. (Id.) That Mr. Neiferd agreed to keep this 2 information confidential further supports a finding of good cause. 3 While Mr. Neiferd argues that Defendants must identify with specificity which 4 documents require protection (Resp. at 3-7), a document-by-document showing is not required.

5 The Court notes that “the use of blanket protective orders conserves judicial resources—and 6 taxpayer money—by eliminating the requirement that a party move for a protective order every 7 time that party produces documents they contend are confidential.” Van v. Wal-Mart Stores, Inc., 8 2011 WL 62499, at *2 (N.D. Cal. Jan. 7, 2011); see also Foltz, 331 F.3d at 1133 (“[A] party 9 seeking the protection of the court via a blanket protective order typically does not make the 10 ‘good cause’ showing required by Rule 26(c) with respect to any particular document.”). As 11 such, “[b]lanket protective orders are entered to facilitate the exchange of discovery documents” 12 and “make no findings that a particular document is confidential or that a document’s disclosure 13 would cause harm.” Small v. Univ. Med. Ctr. of S. Nev., 2015 WL 1281549, at *3 (D. Nev. Mar. 14 20, 2015).

15 A court may issue a blanket protective order if the moving party makes a threshold 16 showing of good cause on a generalized basis, agrees to invoke the designation in good faith, and 17 provides the receiving party the right to challenge confidentiality designations. See Henry v. 18 Ocwen Loan Servicing, LLC, 2018 WL 1638255, at *2 (S.D. Cal. Apr. 5, 2018). Defendants’ 19 proposed protective order, here, satisfies these requirements. (See dkt. # 42-1.) Moreover, 20 Plaintiff’s arguments regarding the public’s general right of access to judicial records are 21 misplaced. See Tefft v. State Farm Mut. Auto. Ins. Co., 2024 WL 2924079, at *1 (D. Nev. June 22 10, 2024) (noting “a party cannot successfully oppose the entry of a blanket protective order by 23 raising concerns about the public’s right of access to judicial records”). 1 IV. CONCLUSION 2 For the foregoing reasons, the Court GRANTS Defendants’ Motion for a Protective 3 Order (dkt. # 42). The parties are ORDERED to confer and propose a protective order consistent 4 with this Order and with the applicable portions of the Local Rules within seven (7) days of the

5 date of this order. If the parties are unable to agree on a proposed protective order by the 6 deadline, the Court will enter a protective order consistent with this Order. 7 Dated this 30th day of September, 2025. 8 9 A 10 MICHELLE L. PETERSON United States Magistrate Judge 11 12 13 14 15 16 17 18 19 20 21 22 23