1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA
9 SiteLock LLC, No. CV-19-02746-PHX-DWL
10 Plaintiff, ORDER
11 v.
12 GoDaddy.com LLC,
13 Defendant. 14 15 Pending before the Court is the parties’ stipulation to redact information from 16 certain documents and to file certain other documents under seal. (Doc. 97.) For the 17 following reasons, the stipulation will be denied without prejudice. 18 As background, SiteLock and GoDaddy entered into a Reseller Agreement in 19 November 2013 under which GoDaddy agreed to market and sell SiteLock’s website 20 security services to GoDaddy’s customers as part of the larger suite of web services offered 21 by GoDaddy. (See generally Doc. 20 at 4-7.) The parties also entered into several 22 subsequent addenda to the Reseller Agreement. (Id.) 23 In April 2019, SiteLock initiated this action. SiteLock’s primary claim is that 24 GoDaddy breached the Reseller Agreement and addenda by failing to remit payment for 25 each SiteLock subscription that customers ordered through the GoDaddy website—instead, 26 GoDaddy only remitted payment when the customer went further and activated the 27 subscription. (Id.) GoDaddy denies that it breached the Reseller Agreement and addenda. 28 (Id.) Additionally, GoDaddy has now come to believe—after reviewing certain documents 1 produced by SiteLock as part of the discovery process—that SiteLock breached the 2 Reseller Agreement and addenda. (Docs. 93, 94.) Thus, GoDaddy has filed a motion for 3 leave to amend its answer and assert new counterclaims. (Id.) 4 The memorandum filed in support of GoDaddy’s motion (Doc. 94) contains an array 5 of proposed redactions, as does GoDaddy’s proposed amended answer (Doc. 93-1 at 19- 6 49). In addition, GoDaddy seeks permission to file the First Addendum and Second 7 Addendum to the Reseller Agreement under seal in their entirety. In the stipulation, the 8 parties contend the proposed redactions and sealing requests are permissible because the 9 items in question “contain pricing terms and structures constituting ‘sensitive information 10 akin to trade secrets.’” (Doc. 97.) 11 The first document containing redactions is GoDaddy’s memorandum in support of 12 its motion to amend. (Compare Doc. 94 [redacted version] with Doc. 101 [lodged version 13 with proposed redactions highlighted].) The Court has carefully reviewed the proposed 14 redactions and is struggling to understand why the material in question should be shielded 15 from public view. In some instances, GoDaddy merely specifies which addendum it 16 contends has been breached, without identifying any of that addendum’s terms. (See, e.g., 17 Doc. 101 at 2:14, 3:9, 6:14-15.) The existence of the addenda has already been disclosed 18 in other filings, so it is unclear why these references must be redacted. As for the next 19 category of proposed redactions (see, e.g., Doc. 101 at 2:20, 12:8-9, 15:4), the Court is 20 again struggling to understand how these references could be considered trade secrets, 21 given their utterly generic nature. Finally, the last batch of proposed redactions (Doc. 101 22 at 15:1-2, 15:15-16) appear to parrot allegations that already appear in other unsealed 23 filings (see, e.g., Doc. 93-1 at 26 ¶¶ 7-8). Given this backdrop, the Court is disinclined to 24 authorize any of the proposed redactions in Doc. 94. 25 The next document containing redactions is the proposed amended answer. 26 (Compare Doc. 93-1 at 19-49 [redacted version] with Doc. 102 [lodged version with 27 proposed redactions highlighted].) The Court is satisfied that the redactions in paragraphs 28 19, 21, 27, 29, 30, 38, 42, 43, 44, 45, 46, 48, 49, and 75 are likely permissible because they 1 refer to specific pricing terms and/or customer identification information that may 2 constitute, or is akin to, a trade secret. However, the redactions in paragraphs 20, 34, 35, 3 36, 37, 40, 47, 50, 51, 54, 55, 57, 60, 63, 68, 74, 76, and 78 seem too generic to trigger 4 competitive concerns and/or seem to encompass information that is already referenced in 5 other unsealed filings. The redactions in paragraph 39 may be permissible in part but some 6 redactions (e.g., Doc. 102 at 35, lines 15, 16, and 19) appear overbroad because they seek 7 to exclude information that is already referenced in other unsealed filings. The redactions 8 in paragraphs 52 and 53 are overbroad for similar reasons. It is unclear why the redactions 9 in paragraph 58 are necessary to avoid competitive harm, as they are generic in nature and 10 constitute the core allegations of fraud that GoDaddy wishes to pursue. And the redactions 11 in paragraphs 59 and 73 seem overbroad because it is unclear why anything apart from the 12 other companies’ names should be redacted. 13 Finally, as for the First Addendum and Second Addendum, although the Court 14 accepts that specific pricing terms within these documents may be subject to redaction, the 15 parties have not attempted to explain why the documents should instead be sealed in their 16 entirety. This approach is particularly difficult to understand given the centrality of these 17 contracts to the parties’ claims and the many references to these documents, and their 18 general contours, in other unsealed filings in this case. 19 For these reasons, the parties’ stipulation will be denied without prejudice. The 20 Court notes that the process of reviewing the proposed stipulations was tedious, time- 21 consuming, and complicated by the parties’ seeming failure to carefully consider whether 22 each proposed redaction was, in fact, necessary. This is a common problem in commercial 23 litigation, as many courts have recognized:
24 The issue that [the motion to seal] presents is illustrative of a much broader problem: the practice of counsel in complex civil cases using the sealing 25 privilege excessively, without careful consideration of whether it is appropriate in particular instances. The problem for judges is that such 26 requests are seldom opposed—the would-be opposing party has access to the materials and doesn’t particularly care whether the public has access as well. 27 Worse, the would-be opposing party frequently hopes to be able to use the sealing mechanism itself and therefore understands that consenting to a 28 motion to seal is the best way to maximize the chance that it will be able to use the sealing mechanism without resistance when its turn comes up. That 1 leaves the judge in the position of having to decide a sometimes complex issue of sealing or redaction with no adversarial briefing and often, as in this 2 case, with only a perfunctory submission from the party seeking relief. . . . Because the policing process is so time-consuming, and because judges have 3 limited access to information that is often important in evaluating claims of confidentiality, the responsibility ultimately falls on counsel to police 4 themselves and to instruct their clients that judges often do not respond well to unreasonable efforts to keep as much out of the public record as possible. 5 Lipocine Inc. v. Clarus Therapeutics, Inc., 2020 WL 4569473, *7 (D. Del. 2020). 6 Should the parties wish to wish to make another attempt to seal or redact any of the 7 materials in question, they must file a motion that identifies, with specificity, each sentence 8 or phrase that is the subject of the sealing or redaction request and explains, with 9 specificity, why the disclosure of that particular sentence or phrase would cause 10 competitive harm.! 11 Accordingly, 12 IT IS ORDERED that the parties’ stipulation to redact information from certain 13 documents and to file certain other documents under seal (Doc. 97) is denied without 14 prejudice. 15 IT IS FURTHER ORDERED that, pursuant to LRCiv 5.6(e), the lodged 16 documents will not be filed, but will remain under seal.
Free access — add to your briefcase to read the full text and ask questions with AI
1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA
9 SiteLock LLC, No. CV-19-02746-PHX-DWL
10 Plaintiff, ORDER
11 v.
12 GoDaddy.com LLC,
13 Defendant. 14 15 Pending before the Court is the parties’ stipulation to redact information from 16 certain documents and to file certain other documents under seal. (Doc. 97.) For the 17 following reasons, the stipulation will be denied without prejudice. 18 As background, SiteLock and GoDaddy entered into a Reseller Agreement in 19 November 2013 under which GoDaddy agreed to market and sell SiteLock’s website 20 security services to GoDaddy’s customers as part of the larger suite of web services offered 21 by GoDaddy. (See generally Doc. 20 at 4-7.) The parties also entered into several 22 subsequent addenda to the Reseller Agreement. (Id.) 23 In April 2019, SiteLock initiated this action. SiteLock’s primary claim is that 24 GoDaddy breached the Reseller Agreement and addenda by failing to remit payment for 25 each SiteLock subscription that customers ordered through the GoDaddy website—instead, 26 GoDaddy only remitted payment when the customer went further and activated the 27 subscription. (Id.) GoDaddy denies that it breached the Reseller Agreement and addenda. 28 (Id.) Additionally, GoDaddy has now come to believe—after reviewing certain documents 1 produced by SiteLock as part of the discovery process—that SiteLock breached the 2 Reseller Agreement and addenda. (Docs. 93, 94.) Thus, GoDaddy has filed a motion for 3 leave to amend its answer and assert new counterclaims. (Id.) 4 The memorandum filed in support of GoDaddy’s motion (Doc. 94) contains an array 5 of proposed redactions, as does GoDaddy’s proposed amended answer (Doc. 93-1 at 19- 6 49). In addition, GoDaddy seeks permission to file the First Addendum and Second 7 Addendum to the Reseller Agreement under seal in their entirety. In the stipulation, the 8 parties contend the proposed redactions and sealing requests are permissible because the 9 items in question “contain pricing terms and structures constituting ‘sensitive information 10 akin to trade secrets.’” (Doc. 97.) 11 The first document containing redactions is GoDaddy’s memorandum in support of 12 its motion to amend. (Compare Doc. 94 [redacted version] with Doc. 101 [lodged version 13 with proposed redactions highlighted].) The Court has carefully reviewed the proposed 14 redactions and is struggling to understand why the material in question should be shielded 15 from public view. In some instances, GoDaddy merely specifies which addendum it 16 contends has been breached, without identifying any of that addendum’s terms. (See, e.g., 17 Doc. 101 at 2:14, 3:9, 6:14-15.) The existence of the addenda has already been disclosed 18 in other filings, so it is unclear why these references must be redacted. As for the next 19 category of proposed redactions (see, e.g., Doc. 101 at 2:20, 12:8-9, 15:4), the Court is 20 again struggling to understand how these references could be considered trade secrets, 21 given their utterly generic nature. Finally, the last batch of proposed redactions (Doc. 101 22 at 15:1-2, 15:15-16) appear to parrot allegations that already appear in other unsealed 23 filings (see, e.g., Doc. 93-1 at 26 ¶¶ 7-8). Given this backdrop, the Court is disinclined to 24 authorize any of the proposed redactions in Doc. 94. 25 The next document containing redactions is the proposed amended answer. 26 (Compare Doc. 93-1 at 19-49 [redacted version] with Doc. 102 [lodged version with 27 proposed redactions highlighted].) The Court is satisfied that the redactions in paragraphs 28 19, 21, 27, 29, 30, 38, 42, 43, 44, 45, 46, 48, 49, and 75 are likely permissible because they 1 refer to specific pricing terms and/or customer identification information that may 2 constitute, or is akin to, a trade secret. However, the redactions in paragraphs 20, 34, 35, 3 36, 37, 40, 47, 50, 51, 54, 55, 57, 60, 63, 68, 74, 76, and 78 seem too generic to trigger 4 competitive concerns and/or seem to encompass information that is already referenced in 5 other unsealed filings. The redactions in paragraph 39 may be permissible in part but some 6 redactions (e.g., Doc. 102 at 35, lines 15, 16, and 19) appear overbroad because they seek 7 to exclude information that is already referenced in other unsealed filings. The redactions 8 in paragraphs 52 and 53 are overbroad for similar reasons. It is unclear why the redactions 9 in paragraph 58 are necessary to avoid competitive harm, as they are generic in nature and 10 constitute the core allegations of fraud that GoDaddy wishes to pursue. And the redactions 11 in paragraphs 59 and 73 seem overbroad because it is unclear why anything apart from the 12 other companies’ names should be redacted. 13 Finally, as for the First Addendum and Second Addendum, although the Court 14 accepts that specific pricing terms within these documents may be subject to redaction, the 15 parties have not attempted to explain why the documents should instead be sealed in their 16 entirety. This approach is particularly difficult to understand given the centrality of these 17 contracts to the parties’ claims and the many references to these documents, and their 18 general contours, in other unsealed filings in this case. 19 For these reasons, the parties’ stipulation will be denied without prejudice. The 20 Court notes that the process of reviewing the proposed stipulations was tedious, time- 21 consuming, and complicated by the parties’ seeming failure to carefully consider whether 22 each proposed redaction was, in fact, necessary. This is a common problem in commercial 23 litigation, as many courts have recognized:
24 The issue that [the motion to seal] presents is illustrative of a much broader problem: the practice of counsel in complex civil cases using the sealing 25 privilege excessively, without careful consideration of whether it is appropriate in particular instances. The problem for judges is that such 26 requests are seldom opposed—the would-be opposing party has access to the materials and doesn’t particularly care whether the public has access as well. 27 Worse, the would-be opposing party frequently hopes to be able to use the sealing mechanism itself and therefore understands that consenting to a 28 motion to seal is the best way to maximize the chance that it will be able to use the sealing mechanism without resistance when its turn comes up. That 1 leaves the judge in the position of having to decide a sometimes complex issue of sealing or redaction with no adversarial briefing and often, as in this 2 case, with only a perfunctory submission from the party seeking relief. . . . Because the policing process is so time-consuming, and because judges have 3 limited access to information that is often important in evaluating claims of confidentiality, the responsibility ultimately falls on counsel to police 4 themselves and to instruct their clients that judges often do not respond well to unreasonable efforts to keep as much out of the public record as possible. 5 Lipocine Inc. v. Clarus Therapeutics, Inc., 2020 WL 4569473, *7 (D. Del. 2020). 6 Should the parties wish to wish to make another attempt to seal or redact any of the 7 materials in question, they must file a motion that identifies, with specificity, each sentence 8 or phrase that is the subject of the sealing or redaction request and explains, with 9 specificity, why the disclosure of that particular sentence or phrase would cause 10 competitive harm.! 11 Accordingly, 12 IT IS ORDERED that the parties’ stipulation to redact information from certain 13 documents and to file certain other documents under seal (Doc. 97) is denied without 14 prejudice. 15 IT IS FURTHER ORDERED that, pursuant to LRCiv 5.6(e), the lodged 16 documents will not be filed, but will remain under seal. The Court will extend the time 17 provided by LRCiv 5.6(e) for GoDaddy to act. GoDaddy may, within 15 days of the entry 18 of this Order, (1) file unredacted versions of the documents in the public record or (2) file 19 a new motion to seal that conforms with the requirements delineated in this order. 20 Dated this 14th day of August, 2020. 21 22 23 Lom ee” } i ~ — 24 Dominic W. Lanza 25 United States District Judge 26 27 □ I The Court recognizes that it granted an earlier sealing request without requiring the sort of detailed showing now being required. (Doc. 80 at 10 n.6.) This may explain why the parties believed the current stipulation would suffice.
-4-