Hacker v. American Family Mutual Insurance Company SI

CourtDistrict Court, D. Arizona
DecidedJune 24, 2025
Docket2:22-cv-01936
StatusUnknown

This text of Hacker v. American Family Mutual Insurance Company SI (Hacker v. American Family Mutual Insurance Company SI) is published on Counsel Stack Legal Research, covering District Court, D. Arizona primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Hacker v. American Family Mutual Insurance Company SI, (D. Ariz. 2025).

Opinion

1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA

9 Craig Hacker, No. CV-22-01936-PHX-DLR

10 Plaintiff, ORDER

11 v.

12 American Family Mutual Insurance Company SI, et al., 13 Defendants. 14 15 16 Before the Court is Plaintiff’s Unopposed Motion to File Under Seal Plaintiff’s 17 Motion for Class Certification and Supporting Documents. (Doc. 62.) For reasons 18 explained below, the motion is denied. 19 I. Standards governing motions to seal 20 The public has a right to access judicial records. San Jose Mercury News, Inc. v. 21 U.S. Dist. Court—N. Dist. (San Jose), 187 F.3d 1096, 1101 (9th Cir. 1999). The Court 22 therefore begins “with a strong presumption in favor of access to court records,” Foltz v. 23 State Farm Mut. Auto Ins. Co., 331 F.3d 1122, 1135 (9th Cir. 2003), and a party seeking 24 to overcome this presumption and file a document under seal generally must provide a 25 compelling reason for doing so, Ctr. for Auto Safety v. Chrysler Grp., LLC, 809 F.3d 1092, 26 1096 (9th Cir. 2016). The Ninth Circuit has carved out an exception to this general rule 27 “for sealed materials attached to a discovery motion unrelated to the merits of the case.” 28 Id. at 1097. A party seeking to seal such materials “need only satisfy the less exacting ‘good 1 cause’ standard.” Id. 2 Although earlier decisions from the Ninth Circuit sometimes used the words 3 “dispositive” and “non-dispositive” to describe the dividing line between those documents 4 governed by the compelling reasons standard and those governed by the good cause 5 standard, the Ninth Circuit has since clarified that “[t]he focus ... is on whether the motion 6 at issue is more than tangentially related to the underlying cause of action.” Id. at 1099. 7 The exception to the ordinary compelling reasons standard applies only to documents that 8 are unrelated or merely tangentially related to the merits of a case. Sealing documents 9 appended to a motion that is more than tangentially related to the merits of a case requires 10 a compelling justification. 11 As this Court has explained on numerous prior occasions, the fact that a document 12 is treated as confidential pursuant to a protective order is not, without more, a compelling 13 reason or good cause for sealing that document once it is used to support a motion. Instead, 14 once a party decides to use a document to support a filing with the Court, the party asserting 15 confidentiality must show either good cause or compelling reasons (depending on the 16 nature of the filing) for sealing it from public view. See, e.g., Calyxt Inc. v. Morris Ag Air 17 & Sons Inc., No. CV-20-01221-PHX-DLR, 2022 WL 17689166, at *2 (D. Ariz. Dec. 15, 18 2022); Blum v. Banner Health, No. CV-20-00409-PHX-DLR, 2021 WL 5446460, at *1 19 (D. Ariz. Nov. 22, 2021); Marsteller v. MD Helicopter Inc., No. CV-14-01788-PHX-DLR, 20 2017 WL 5479927, at *2 (D. Ariz. Nov. 15, 2017). This remains so even if the parties agree 21 that a document should be sealed. Parties cannot stipulate away the public’s right to view 22 judicial records and, instead, must articulate a factual and legal basis sufficient to overcome 23 the presumption favoring public access. 24 II. Procedure for requesting that documents be sealed 25 Local Rule of Civil Procedure 5.6 details the procedures that must be followed when 26 parties seek to file documents under seal. 27 Ordinarily, the Court will not seal a document absent a motion or stipulation that 28 “set[s] forth a clear statement of the facts and legal authority justifying the filing of the 1 document under seal[.]” LRCiv 5.6(b). When such a motion or stipulation is filed, the 2 submitting party must also separately lodge the relevant documents under seal. LRCiv 3 5.6(b)-(c) If the Court agrees that the documents should be sealed, then it will grant the 4 motion or stipulation and direct the Clerk of the Court to file under seal the documents that 5 the submitting party previously lodged under seal. If the Court disagrees and denies the 6 motion or stipulation in full, then those lodged documents do not become part of the record, 7 public or otherwise. Instead, the submitting party can choose to either not file those 8 documents, or to file them on the public docket within 5 days of the date of the Court’s 9 order. LRCiv 5.6(e). Similarly, if the Court grants the motion or stipulation to seal in part 10 and denies it in part, then the submitting party may resubmit the documents in a way that 11 conforms to the Court’s order (for example, by redacting only the discrete material the 12 Court found could be sealed). 13 This procedure gets more complicated, however, when the party who wishes to file 14 the documents is not the same party who believes the documents should be sealed. This 15 situation most often arises when one party wishes to support a motion with documents 16 designated by another party as confidential pursuant to a protective order. This scenario is 17 governed by a different procedure, detailed in LRCiv 5.6(d), which is designed to ensure 18 that the party moving to seal documents is the same party who believes the documents 19 should be filed under seal. 20 Under LRCiv 5.6(d), the parties are first to confer. This conferral could yield several 21 different outcomes. First, the designating party could withdraw all or some of its 22 confidentiality designations, thereby paving the way for the submitting party to file those 23 documents publicly. Second, the parties could agree that all or some of the confidential- 24 designated documents meet the legal standard for submission under seal, in which case 25 they can file a stipulation stating the facts and legal authority justifying the filing of the 26 documents under seal, per LRCiv 5.6(b). Third, the parties could disagree in whole or in 27 part over the propriety of filing the confidential-designated documents under seal. In this 28 situation, the submitting party does not file a motion to seal because the submitting party 1 is not the party asserting confidentiality. Instead, the submitting party provisionally lodges 2 the relevant documents under seal, along with a notice certifying the parties conferred in 3 good faith but could not agree about whether the documents should be filed under seal and 4 summarizing the disagreement. This notice then triggers a 14-day deadline by which the 5 designating party must either file a notice withdrawing its confidentiality designations or 6 a motion to seal detailing the factual and legal basis for sealing the documents. If the 7 designating party does not file such a motion or notice, the Court may order that the 8 provisionally sealed documents be filed on the public docket. 9 III. Plaintiff’s motion 10 Plaintiff’s motion does not strictly comport with LRCiv 5.6(d). Here’s how the 11 Court understands what the parties were trying to accomplish: 12 The parties met and conferred regarding Defendant’s confidentiality designations, 13 and Defendant agrees to withdraw its confidentiality designation as to Exhibit 81 of the 14 Declaration of John M. DeStefano in Support of Plaintiff’s Motion for Class Certification. 15 The parties did not confer regarding aspects of Plaintiff’s brief in support of class 16 certification, or regarding the expert reports attached thereto at Exhibits 83 and 84, because 17 Plaintiff did not want to give Defendant advance access to these documents prior to 18 Plaintiff’s filing deadline.

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
Hacker v. American Family Mutual Insurance Company SI, Counsel Stack Legal Research, https://law.counselstack.com/opinion/hacker-v-american-family-mutual-insurance-company-si-azd-2025.