HAYWOOD S. GILLIAM, JR., District Judge.
Pending before the Court is the parties' joint renewed administrative motion to file under seal. The Court previously granted in part and denied in part the parties' administrative motions to file under seal. Dkt. No. 789. Having carefully considered the pending motion and supporting declarations, the Court
Courts generally apply a "compelling reasons" standard when considering motions to seal documents. Pintos v. Pac. Creditors Ass'n, 605 F.3d 665, 678 (9th Cir. 2010) (quoting Kamakana v. City & Cty. of Honolulu, 447 F.3d 1172, 1178 (9th Cir. 2006)). "This standard derives from the common law right `to inspect and copy public records and documents, including judicial records and documents.'" Id. (quoting Kamakana, 447 F.3d at 1178). "[A] strong presumption in favor of access is the starting point." Kamakana, 447 F.3d at 1178 (quotations omitted). To overcome this strong presumption, the party seeking to seal a judicial record attached to a dispositive motion must "articulate compelling reasons supported by specific factual findings that outweigh the general history of access and the public policies favoring disclosure, such as the public interest in understanding the judicial process" and "significant public events." Id. at 1178-79 (quotations omitted). "In general, `compelling reasons' sufficient to outweigh the public's interest in disclosure and justify sealing court records exist when such `court files might have become a vehicle for improper purposes,' such as the use of records to gratify private spite, promote public scandal, circulate libelous statements, or release trade secrets." Id. at 1179 (quoting Nixon v. Warner Commc'ns, Inc., 435 U.S. 589, 598 (1978)). "The mere fact that the production of records may lead to a litigant's embarrassment, incrimination, or exposure to further litigation will not, without more, compel the court to seal its records." Id.
Records attached to nondispositive motions must meet the lower "good cause" standard of Rule 26(c) of the Federal Rules of Civil Procedure, as such records "are often unrelated, or only tangentially related, to the underlying cause of action." Id. at 1179-80 (quotations omitted). This requires a "particularized showing" that "specific prejudice or harm will result" if the information is disclosed. Phillips ex rel. Estates of Byrd v. Gen. Motors Corp., 307 F.3d 1206, 1210-11 (9th Cir. 2002); see also Fed. R. Civ. P. 26(c). "Broad allegations of harm, unsubstantiated by specific examples of articulated reasoning" will not suffice. Beckman Indus., Inc. v. Int'l Ins. Co., 966 F.2d 470, 476 (9th Cir. 1992) (quotation omitted).
The Court previously denied in part numerous administrative motions to file under seal, primarily because the parties did not narrowly tailor their sealing requests to redact only confidential or proprietary business information, and the requests sought to redact substantial volumes of information otherwise unredacted elsewhere. Dkt. No. 789 at 3. The Court directed the parties to file any renewed motions to seal within fourteen days. Id. at 6.
The parties have publicly refiled documents which they no longer seek to seal. Dkt. No. 858. However, the parties have not publicly refiled Exhibits 3, 6, 18, 19, and 28 to the Declaration of Daniel A. Apgar ("Apgar Declaration"), nor have the parties submitted renewed requests to seal those exhibits. Given the substantial volume of documents, the Court will afford the parties one more opportunity to file a renewed motion to seal those exhibits, should the parties still seek to do so. Otherwise, the parties should file unredacted versions of those exhibits.
Turning to the renewed sealing requests, the parties have narrowly tailored the redactions to confidential and proprietary business information. The Court finds good cause to grant the motion to file the redacted portions under seal. See Apple Inc. v. Samsung Elecs. Co., Ltd., No. 11-CV-01846-LHK, 2012 WL 6115623 (N.D. Cal. Dec. 10, 2012); see also Agency Solutions.Com, LLC v. TriZetto Group, Inc., 819 F.Supp.2d 1001, 1017 (E.D. Cal. 2011); Linex Techs., Inc. v. Hewlett-Packard Co., No. C 13-159 CW, 2014 WL 6901744 (N.D. Cal. Dec. 8, 2014).
However, the parties still fail to narrowly tailor the sealing request for the Declaration of Jonathan M. Sharret ("Sharret Declaration"). Dkt. No. 860-11. With respect to third-party Google's proposed redactions in paragraphs 52 and 53, the Court finds Google has established good cause to seal those narrowly tailored redacted portions. However, the public version contains redactions pertaining to both HTC and Microsoft, Dkt. No. 860-11 ¶¶ 6-44 (HTC), 61-95 (Microsoft), yet neither party's supporting declaration explains why the information should be redacted. See Dkt. Nos. 860-2, 860-3. Further, the redactions pertaining to HTC and Microsoft are substantially overbroad. For example, the parties seek to redact procedural history, including information publicly available on the docket. The Court does not find that procedural history in this case constitutes confidential and proprietary business information so as to warrant sealing, especially in the absence of a particularized showing of how disclosure would lead to specific harm or prejudice.
Accordingly, the Court
For the foregoing reasons, the Court
The Court will grant the parties one more opportunity to file a renewed motion to seal for the Sharret Declaration and Exhibits 3, 6, 18, 19, and 28 to the Apgar Declaration. The Court will allow seven days (7) from the date of this order for the parties to file the renewed motion to seal according to the requirements discussed above. If the parties no longer seek to seal those documents, then the parties are directed to file public, unredacted versions of the documents within seven days (7) from the date of this order (the exception being Google's proposed redactions in paragraphs 52 and 53 of the Sharret Declaration). The Court expects the parties will use their best objective judgment to file a motion that is narrowly tailored, properly supported by declarations, and satisfies the requisite standards. Google need not file another supporting declaration.