Shared Partnership v. Meta Platforms, Inc.

District Court, N.D. California·Decided March 14, 2023·No. 3:22-cv-02366·Unknown

Opinion

1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 EUREKA DIVISION 7 8 SHARED PARTNERSHIP, Case No. 22-cv-02366-RS (RMI)

9 Plaintiff, ORDER RE: DISCOVERY DISPUTES 10 v. Re: Dkt. Nos. 47, 49 11 META PLATFORMS, INC., 12 Defendant.

13 14 Now pending before the court are a pair of discovery dispute letter briefs (dkts. 47, 49) 15 that, generally speaking, represent Plaintiff’s request to compel the production of certain 16 discovery. It appears that the two letters are substantially the same, with the exception that the first 17 letter appears to have been rushed to court before Defendant could articulate its position as to one 18 of the issues raised by Plaintiff (see dkt. 47 at 3-4; see also dkt. 49 at 1, 4-5). Defendant submits 19 that Plaintiff has involved the court prematurely, that the dispute is not quite ripe for a motion to 20 compel, and that the parties should continue to engage one another in the discovery process. See 21 Ltr. Br. (dkt. 49) at 2. For the reasons stated below, the court wholeheartedly agrees. 22 Plaintiff has presented two issues. In the first, Plaintiff complains of the timing of 23 Defendant’s document production. See id. at 1-2. In this regard, Plaintiff submits that it tendered a 24 set of interrogatories and requests for production in late October of 2022, and that Defendant’s 25 responses – which were served in mid-December of 2022, did not contain substantive information 26 but were rather limited to objections (presumably as to some requests) and statements to the effect 27 that responsive documents and information would be produced on a rolling basis (again, 1 not be forced to agree to an speculative extension of the fact discovery deadline (currently set for 2 September 21, 2023) and risk pushing back an already-scheduled trial date of April 2024, Plaintiff 3 submits that Defendant should now be forced “to complete its entire document production by 4 April 7, 2023” because it “has had more than enough time – and has more than enough resources – 5 to accomplish this.” Id. at 2. 6 Defendant responds to the effect that Plaintiff’s 41 document requests are relatively broad 7 and that they seek, among other things, all documents relating to Plaintiff, all documents regarding 8 Plaintiff’s rejected advertisements on Defendant’s platform, and all documents concerning 9 Defendant’s use of artificial intelligence to reject any and all advertisements in general (that is, not 10 simply information limited to the rejection of Plaintiff’s own advertisements – the subject of this 11 action). Id. at 2. Nevertheless, Defendant submits that through its December responses, it agreed to 12 search for and produce several categories of information including documents relating to 13 Plaintiff’s rejected advertisements, notifications regarding those advertisements, and 14 communications between the Parties. Id. Following discussions regarding the scope, relevance, 15 and proportionality of the requested discovery, Defendant states that it has agreed to produce a 16 narrowed set of documents for the majority of Plaintiff’s requests, and that it is working diligently 17 to gather responsive, non-privileged documents for production. Id. at 2-3. 18 However, Defendant contends that there are three remining hurdles. As to the first, 19 Defendant states that it “cannot produce any documents until a stipulated protective order is 20 entered between the parties and Court, and the parties are currently negotiating the substance of 21 the protective order so that [Defendant] can begin producing documents.” Id. at 3. The court finds 22 that this hurdle is easy to surmount. The Parties are herewith ORDERED to promptly meet and 23 confer in a good faith effort to iron out their differences as to their respective views regarding the 24 substance of the protective order necessary such that Defendant can begin producing documents. 25 The court recommends, but does not require, using this district’s model protective order at least as 26 a starting point. In the event that the Parties cannot arrive at a stipulated resolution, the Parties are 27 FURTHER ORDERED to clearly and concisely present what disputes remain in this regard 1 undersigned’s general standing order.1 2 As to the second hurdle, Defendant submits that it “continues to work diligently to search 3 for documents responsive to the majority of [the] requests it has agreed to produce” and that it 4 “has already identified tens of thousands of potentially responsive documents to [Plaintiff’s] 5 rejected advertisements and notifications regarding those rejected advertisements.” Id. at 3. 6 Defendant explains that the responsive discovery is voluminous and time-consuming to gather and 7 produce due to the fact that Plaintiff’s advertising relationship on Defendant’s platform “goes back 8 over ten years, and the volume of data is substantial,” as well as the fact that “the process to search 9 for, review, and pull those documents, which began months ago, is manual — [and] there are thus 10 multiple, time-consuming steps [Defendant] must undertake before it can produce information 11 regarding [Plaintiff’s] disapproved advertisements, of which there were many.” Id. Defendant then 12 adds that this is why it has focused on only potentially responsive documents – that is, those 13 related to Plaintiff’s rejected advertisements – rather than documents related to Defendant’s more 14 “general purported use of artificial intelligence.” Id. At bottom, Defendant contends that “[t]hese 15 documents are probative of whether [Plaintiff’s] ads were rejected and what notice [Plaintiff] 16 received regarding those ads, which is directly relevant to [the] fraud-based claims.” Id. The court 17 finds that the assertion of this hurdle is closely intertwined with the second issue raised by 18 Plaintiff’s request to compel; accordingly, the court will address it below. 19 As to the third hurdle, Defendant submits that it has not yet provided a specific date by 20 which it will complete production of all responsive, non-privileged documents because it 21 “continues to search for responsive documents, the extent of those documents, and [because it is 22 currently engaged in] the labor-intensive process of pulling those potentially responsive 23 documents.” Id. In short, Defendant submits that it “has been working for months to gather and 24 review documents for production once the protective order is entered,” and that it “intends on 25 producing documents on a rolling basis shortly thereafter.” Id. 26 In essence, this dispute boils down to Plaintiff’s desire to rush Defendant through the 27 1 discovery process based only on a thin justification that Defendant “has had more than enough 2 time – and has more than enough resources – to accomplish this.” Id. at 2. The court finds this 3 notion to be unpersuasive. The alleged magnitude of Defendant’s resources, and the passage of a 4 few months of time does not justify arbitrarily setting a production deadline of April 7, 2023, as 5 Plaintiff suggests. Once the Parties’ dispute about the terms of the forthcoming protective order 6 (either by stipulation or by court order) are resolved, the court sees no reason – and Plaintiff has 7 certainly not suggested one – that Defendant’s production should not proceed on the rolling basis 8 it has suggested and justified. Accordingly, Plaintiff’s request to force Defendant to complete its 9 production by April 7, 2023, is DENIED. 10 As to the second issue, Plaintiff seeks an order “making clear that [Defendant’s] use of 11 artificial intelligence to reject ads—including what it did and did not know about the ability of 12 artificial intelligence to provide explanations for ad rejections—is both relevant and discoverable.” 13 Id. Plaintiff then adds that “[t]his dispute is implicated by the following discovery requests: a) 14 Interrogatories 2-4 and b) RFP Nos. 15-20; 25-34; and 38-41.” Id. at 4.

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

Shared Partnership v. Meta Platforms, Inc., (N.D. Cal. 2023).

Shared Partnership v. Meta Platforms, Inc. (Shared Partnership v. Meta Platforms, Inc.) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.