Rabin, CPA v. Google LLC

Opinion

1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 STEVE RABIN, et al., Case No. 22-cv-04547-PCP

8 Plaintiffs, ORDER RE: DISCOVERY LETTER v. 9 Re: Dkt. No. 73 10 GOOGLE LLC, Defendant. 11

12 13 The parties are unable to agree on the type of protective order that should be entered in this 14 case and have asked the Court to resolve their dispute. For the reasons that follow, the Court will 15 enter the Plaintiffs’ proposed protective order, which is based on the model for standard cases. 16 The Northern District offers several model protective orders, and this Court’s Standing 17 Order encourages parties requesting a protective order to base their proposals on these models. For 18 “patent cases,” the Northern District provides a “Model Protective Order for Litigation Involving 19 Patents, Highly Sensitive Confidential Information and/or Trade Secrets.” For “standard cases,” it 20 provides a model “Stipulated Protective Order for Standard Litigation.” Except for patent cases 21 (which this case is not), “the Local Rules do not require the parties to use any of the model 22 protective orders and counsel may stipulate to or move for another form of protective order.” 23 Model Protective Orders, cand.uscourts.gov/forms/model-protective-orders. 24 Here, Plaintiffs propose to use a modified version of the model order for standard cases; 25 Google proposes to use a modified version of the model order for patent cases. See Dkt. No. 73. 26 The key difference is that the latter order imposes a two-tiered classification system that would 27 allow Google to designate information as either “confidential” or “highly confidential – attorneys’ 1 Under Federal Rule of Civil Procedure 26(c), the Court “may, for good cause, issue an 2 order to protect a party or person from annoyance, embarrassment, oppression, or undue burden or 3 expense” in discovery, including by “requiring that a trade secret or other confidential research, 4 development, or commercial information not be revealed or be revealed only in a specified way.” 5 “The burden is upon the party seeking the order to ‘show good cause’ by demonstrating harm or 6 prejudice that will result from the discovery.” Rivera v. NIBCO, Inc., 364 F.3d 1057, 1063 (9th 7 Cir. 2004). “For good cause to exist, the party seeking protection bears the burden of showing 8 specific prejudice or harm will result if no protective order is granted.” Phillips ex rel. Estates of 9 Byrd v. Gen. Motors Corp., 307 F.3d 1206, 1210–11 (9th Cir. 2002). Here, because Google seeks 10 to impose greater restrictions, it bears the burden of showing prejudice or harm that will result if 11 the less restrictive standard order, as modified by Plaintiffs, is imposed. See MasterObjects Inc. v. 12 Google Inc., No. C 11-01054 LB, 2012 WL 2958227, at *2 (N.D. Cal. July 19, 2012). 13 Google has not met its burden. Its statement in support of its request for the more 14 restrictive protective order is couched in speculation. Google writes in the joint discovery letter 15 that “discovery may require Google to produce competitively sensitive information”; that it seeks 16 “to adequately protect itself in the litigation, should the need arise”; and that requested categories 17 of information “present, at least the possibility, that Google will need ‘highly confidential’ 18 protection for responsive documents and information.” This is not the kind of showing of specific 19 harm or prejudice that is required to warrant imposing additional restrictions on discovery. 20 Google also argues its proposed more restrictive order would not prejudice the Plaintiffs. 21 But this gets the burden backwards. It is not enough that proposed restrictions will not prejudice 22 Plaintiffs. And it is not enough that proposed restrictions are not “unreasonable or unusual,” or 23 that they may have been imposed in other cases. It is Google that must specifically show that it 24 will be prejudiced or harmed in this particular case if its proposed restrictions are not adopted. 25 This Google has not done. 26 The Court is also keenly aware of the tendency for parties to litigation to over-designate 27 material as “confidential” or “highly confidential” pursuant to the terms of such protective orders. 1 internal mechanisms for managing materials produced in discovery, sharing documents (including 2 || draft pleadings) with clients, and filing documents with the Court. The practice also burdens the 3 Court, which must resolve disputes between the parties about the proper designation of particular 4 || discovery responses and address motions to seal that are premised upon such over-designations. In 5 the absence of a strong showing of necessity, the Court is reluctant to impose any protective order 6 || that increases the risk of such over-designation. 7 Plaintiffs have proposed to use (with some modifications) the Northern District’s model 8 || “Stipulated Protective Order for Standard Litigation”—an order that, as its name suggests, is 9 deemed to be presumptively reasonable in most cases. Because Google has not met its burden of 10 || demonstrating that it will be harmed or prejudiced if the standard and presumptively reasonable 11 protective order is adopted in this case, the Court accepts Plaintiffs’ proposal. Plaintiffs are 12 || directed to update their proposed order to resolve the tracked changes and remove the “stipulation” 5 13 designation and to then file a revised copy on ECF within seven days of this order. The order will 14 || then be entered as the protective order for this case. 3 15 As Google’s statement recognizes, it is possible this case might proceed without Google 16 || ever being asked to produce any information it deems to be highly confidential. Should the need 3 17 arise, however, Google remains free to move under Rule 26 for a specific protective order 18 || protecting particular information for which good cause can be demonstrated. 19 20 IT IS SO ORDERED. 21 Dated: November 20, 2023 22 Ce Ze 23 P. Casey Pitts United States District Judge 25 26 27 28