Facebook, Inc. v. OnLineNic Inc

District Court, N.D. California·Decided November 8, 2023·No. 3:19-cv-07071·Unknown

Opinion

1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 FACEBOOK, INC., et al., Case No. 19-cv-07071-SI

8 Plaintiffs, ORDER RE: ADMINISTRATIVE 9 v. MOTIONS TO FILE UNDER SEAL

10 ONLINENIC INC, et al., Re: Dkt. Nos. 300, 302, 319, 321, 325, 336, 11 Defendants. 340, 342

12 13 The Court has before it multiple motions to seal, including supplemental motions and several 14 errata, filed in conjunction with plaintiffs’ motion to strike defendant’s answer and for entry of 15 default against defendant Xiamen 35.com Internet Technology Co., Ltd. (“35.CN”). See Dkt. Nos. 16 300, 302, 319, 321, 325, 336, 340, 342. 17 18 LEGAL STANDARD 19 The parties agree that because the underlying motion is a dispositive one,1 the “compelling 20 reasons” standard applies. In the Ninth Circuit, with the exception of a narrow range of documents 21 that are “traditionally kept secret,” courts begin their sealing analysis with “a strong presumption in 22 favor of access.” Foltz v. State Farm Mut. Auto. Ins., 331 F.3d 1122, 1135 (9th Cir. 2003). When 23 applying to file documents under seal in connection with a dispositive motion, the submitting party 24 bears the burden of “articulating compelling reasons supported by specific factual findings that 25 outweigh the general history of access and the public policies favoring disclosure, such as the public 26 1 Plaintiffs originally filed the underlying motion as a motion to strike 35.CN’s answer and 27 for default, in other words, a motion for terminating sanctions under Federal Rule of Civil Procedure 1 interest in understanding the judicial process.” Kamakana v. City & Cnty. of Honolulu, 447 F.3d 2 1172, 1178-79 (9th Cir. 2006) (internal quotations and citations omitted). The Ninth Circuit has 3 explained: 4 Under this stringent standard, a court may seal records only when it finds a compelling reason and articulates the factual basis for its ruling, without relying on 5 hypothesis or conjecture. The court must then conscientiously balance the competing interests of the public and the party who seeks to keep certain judicial records secret. 6 What constitutes a “compelling reason” is best left to the sound discretion of the trial court. Examples include when a court record might be used to gratify private spite 7 or promote public scandal, to circulate libelous statements, or as sources of business information that might harm a litigant’s competitive standing. 8 Ctr. for Auto Safety v. Chrysler Grp., LLC, 809 F.3d 1092, 1096-97 (9th Cir. 2016) (citations, 9 internal quotation marks, and alterations omitted). In addition, all requests to file under seal must 10 be “narrowly tailored,” such that only sealable information is sought to be redacted from public 11 access. Civ. L.R. 79-5(c)(3). 12

13 DISCUSSION 14 The parties (plaintiffs, 35.CN, and the OnlineNIC defendants),2 as well as third-party 15 Internet Corporation of Assigned Names and Numbers (“ICANN”), have filed statements regarding 16 the various sealing motions. To summarize, plaintiffs did not file a statement in support of sealing 17 any material, explaining that 35.CN’s “Opposition and supporting declarations contain only 18 conclusions abstracted from documents produced and designated by Plaintiffs in the course of 19 discovery” and that “Plaintiffs do not believe that sealing those portions of the Opposition and 20 supporting declarations purportedly containing Plaintiffs’ confidential information is necessary.” 21 Dkt. No. 323 at 2. ICANN seeks to seal material that “reflect[s] personal identifiable information 22 provided to ICANN.” Dkt. No. 309 at 1; Dkt. No. 326. ICANN, however, did not file a declaration 23 in support of sealing material filed in connection with 35.CN’s opposition brief or plaintiffs’ 24 objection to sur-reply evidence.3 The OnlineNIC defendants have filed several declarations in 25

26 2 The OnlineNIC defendants are comprised of defendants OnlineNIC Inc. (“OnlineNIC”) and Domain ID Shield Service Co. (“ID Shield”). 27 1 support of sealing material, see Dkt. Nos. 312, 313, 334. OnlineNIC’s declarations go through line- 2 by-line analysis of which portions of the materials the OnlineNIC defendants still wish to have 3 sealed. They largely seek to seal information they say “is competitively sensitive, internal corporate 4 financial information disclosing profitability.” See Dkt. No. 334 at 2-9. 5 35.CN has filed declarations in support of sealing essentially all of the material that 35.CN 6 has designated as confidential. See Dkt. Nos. 310, 319-1, 328, 336-1, 344. 7 The Court has reviewed the declarations and the material sought to be sealed. The Court 8 will grant the motions requesting sealing of the materials for which ICANN filed a declaration in 9 support of sealing. For the remainder of the material, the Court will seal only those portions of the 10 filings that are financial figures or that disclose the names and contact information of rank-and-file 11 employees. A party may move to seal confidential business and financial information that includes, 12 among other items, financial terms of agreements, business strategies, and confidential negotiations. 13 See Exeltis USA Inc. v. First Databank, Inc., 2020 WL 2838812 at *1-2 (N.D. Cal. June 1, 2020); 14 In re Qualcomm Litig., 2017 WL 5176922, at *2 (S.D. Cal. Nov. 8, 2017). As to the remaining 15 sealing requests, those are denied for failure to meet the legal standard and because the requests are 16 not narrowly tailored. 17 The Court finds that 35.CN’s sealing motions in particular are overbroad and unsupported 18 by compelling reasons. The Local Rules of this District caution that “overly broad requests to seal 19 may result in the denial of a motion.” Civ. L.R. 79-5(f)(6). Looking at what 35.CN seeks to seal, 20 almost none of the information could be construed as confidential. Rather, most of it involves the 21 relationships among the parties that go to the very heart of the Court’s recent order on the question 22 of alter ego. See Dkt. No. 351. For instance, 35.CN seeks to seal the portions of plaintiffs’ motion 23 stating that Carrie Yu signed the Service Outsource Contracts on behalf of OnlineNIC at the same 24 time that she was an employee of 35.CN, paid solely by 35.CN. See Dkt. No. 299, Pls.’ Mot. at 25 5:14-15. As another example, 35.CN—which is a publicly owned company—seeks to seal the 26 identities of its wholly owned subsidiaries and its largest shareholders, officers, and directors. See 27 Kroll Decl., Ex. A, App’x A at 5-6. 1 but rather states, as to everything, that the documents “contain information concerning private 2 financial transactions of Defendant, personal information about employees of Defendant and 3 Defendant’s Chinese business partners, and the identities of employees of Defendant.” See, e.g., 4 Dkt. No 310 ¶ 5. Relying “upon the analysis of Chinese outside counsel for Defendant,” 35.CN 5 asserts that “Chinese law prohibits Chinese companies from disclosing a wide variety of data and 6 personal information about Chinese residents to entities outside of China.” See id. ¶¶ 6, 9. 35.CN 7 cites to outside counsel’s analysis, attached to a discovery dispute letter form June 2022. See id. ¶ 9 8 (citing Dkt. No. 247-11). The Court is not persuaded that this letter, written by a law firm that 9 represents 35.CN in response to a discovery dispute, creates a compelling reason to seal from public 10 view basic information such as who signed OnlineNIC and 35.CN’s outsourcing contracts. 11 Moreover, the letter describes certain processes that Chinese companies may go through in order to 12 validly disclose certain data.

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

Facebook, Inc. v. OnLineNic Inc, (N.D. Cal. 2023).

Facebook, Inc. v. OnLineNic Inc (Facebook, Inc. v. OnLineNic Inc) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Boakai v. Gonzales
447 F.3d 1 (First Circuit, 2006)
Center for Auto Safety v. Chrysler Group, LLC
809 F.3d 1092 (Ninth Circuit, 2016)