Mora v. Zeta Interactive Corp. et al

Filing 58

ORDER GRANTING IN PART PLAINTIFFS MOTION TO COMPEL (ECF Nos. #46 , #49 , #51 , #53 ) signed by Magistrate Judge Stanley A. Boone on 2/10/2017. It is hereby ordered that: Plaintiff's motion to compel production of documents responsive to request for production nos. 18, 19, and 21 is GRANTED IN PART; Defendants shall produce the call logs for calls made by Education Bridge, during the putative class period, from February 16, 2012, through present, in order to promote its products or services, in an electronic format within twenty-one (21) days of the date of entry of this order; and The parties shall file a stipulated protective order based upon the Northern District of California's Model Protective Order for Litigation Involving Patents, Highly Sensitive Confidential Information and/or Trade Secrets, but excising portions that are inconsistent with this order, within ten (10) days of the date of entry of this order. (Valdez, E)

1
2
3
4
5
6

UNITED STATES DISTRICT COURT

7

EASTERN DISTRICT OF CALIFORNIA

8
SERGIO MORA, on behalf of himself and all
others similarly situated,

9

Case No. 1:16-cv-00198-DAD-SAB
ORDER GRANTING IN PART
PLAINTIFF’S MOTION TO COMPEL

10
Plaintiff,
11
v.

(ECF Nos. 46, 49, 51, 53)

12
ZETA INTERACTIVE CORP., et al.,
13
Defendants.
14
Currently before the Court is Plaintiff Sergio Mora’s (“Plaintiff’s”) motion to compel

15

16 production of documents. Oral argument on Plaintiff’s motion was held on February 8, 2017.
17 Counsel Joshua Arisohn appeared telephonically for Plaintiff and counsel John Du Wors
18 appeared telephonically for Defendants Zeta Interactive Corp. (“Defendant Zeta”) and David
19 Steinberg (“Defendant Steinberg”). Having considered the notice of motion, the parties’ joint
20 statement re discovery disagreement, Defendants’ supplemental statement re discovery
21 disagreement, Plaintiff’s supplemental statement re discovery disagreement, arguments presented
22 at the February 8, 2017 hearing, as well as the Court’s file, the Court issues the following order.
23

I.

24

RELEVANT HISTORY
Plaintiff proceeds on his first amended complaint (“FAC”) against Defendant Zeta and

25

1
26 Defendant Steinberg, the CEO and founder of Defendant Zeta. (FAC, ECF No. 13.) Plaintiff

27
1

The Court notes that Plaintiff filed a motion to amend his complaint on February 3, 2017, which is set for hearing

28 on March 7, 2017. (ECF No. 55.)

1

1 brings this action on behalf of a putative class of individuals who received allegedly unsolicited
2 telephone calls from Ward Media, Inc. (“Ward Media”), a now defunct subsidiary of Defendant
3 Zeta. (Id. at ¶¶ 1-4, 18-21.) Specifically, Plaintiff alleges that on November 13, 2015, he
4 personally received two telephone calls from an entity known as Education Bridge, which is
5 related to Ward Media. (Id. at ¶¶ 14-16.) Plaintiff also alleges that prior to these telephone calls,
6 he : (1) never had any contact with Defendants; (2) never provided Defendants with his
7 telephone number; and (3) never consented, in writing or otherwise, to receive such calls from
8 Defendants. (Id. at ¶ 13.) Plaintiff’s claims are based on alleged violations of the Telephone
9 Consumer Protection Act (“TCPA”). (Id. at ¶ 2.)
10

On January 17, 2017, Plaintiff filed a motion to compel discovery with a hearing on the

11 motion set for February 8, 2017. (ECF No. 46.) The parties filed a joint statement re discovery
12 disagreement on January 23, 2017. (ECF No. 49.)
13

On January 25, 2017, an order issued requiring the parties to conduct a meaningful meet

14 and confer in person or by telephone regarding the issues in the motion to compel on or before
15 January 31, 2017. (ECF No. 50.) The parties were also ordered to file a supplemental joint
16 statement detailing their renewed meet and confer efforts and any additional information for the
17 motion, or a notice of withdrawal of the motion to compel, on or before January 31, 2017. If
18 Plaintiff did not withdraw the motion to compel and Defendants requested a protective order that
19 was different from Plaintiff’s proposed protective order, Defendants were ordered to file a copy
20 of their proposed protective order.
21

On January 30, 2017, the parties met and conferred. On January 31, 2017, Defendants

22 filed their updated statement re discovery disagreement discussing their position and their
23 proposed protective order. (ECF No. 51.) Defendants indicate in their updated statement re
24 discovery disagreement that after the parties met and conferred on January 30, 2017, Plaintiff
25 provided Defendants with an updated joint statement reflecting Plaintiff’s changes. Defendants
26 then provided Plaintiff with Defendants’ changes. Defendants state that they then inquired
27 multiple times regarding Plaintiff’s intent to file the updated joint statement, but they did not
28 receive any response from Plaintiff and Plaintiff had not filed the joint statement at the time

2

1 Defendants filed their updated portion of the joint statement.

Plaintiff also did not file a

2 supplemental statement re discovery disagreement, file a notice of withdrawal of the motion to
3 compel, or otherwise respond to the Court’s January 25, 2017 order.
4

On February 1, 2017, the Court ordered Plaintiff to show cause in writing why sanctions

5 should not be imposed for failure to comply with the January 25, 2017 order. (ECF No. 52.) On
6 February 1, 2017, Plaintiff filed his response to the order to show cause and his updated
7 statement re discovery disagreement. (ECF No. 53.) Plaintiff’s counsel indicates that he thought
8 that Defendants would be making the required joint filing after adding their portion and that he
9 was on a flight and did not receive Defendants’ email asking which party would be filing the
10 joint statement. Based on Plaintiff’s response, the Court discharged the February 1, 2017 order
11 to show cause. (ECF No. 54.)
12

II.

13

LEGAL STANDARD

14

Motions to compel are governed by Federal Rule of Civil Procedure 37, which states, in

15 pertinent part:
16

(a) Motion for an Order Compelling Disclosure or Discovery.
(1) In General. On notice to other parties and all affected persons,
a party may move for an order compelling disclosure or discovery.
The motion must include a certification that the movant has in
good faith conferred or attempted to confer with the person or
party failing to make disclosure or discovery in an effort to obtain
it without court action.

17
18
19

20 Fed. R. Civ. P. 37.
21

Rule 34 of the Federal Rule of Civil Procedure provides that a party may serve upon any

22 other party a request for production of any designated documents or electronically stored
23 information within the party’s possession, custody, and control that is within the scope of Rule
24 26. Fed. R. Civ. P. 34(a)(1)(A). The party receiving the request has thirty days in which to
25 respond. Fed. R. Civ. P. 34(b)(2). A party may move for an order compelling production where
26 the opposing party fails to produce documents as requested under Rule 34. Fed. R. Civ. P.
27 37(a)(3(B)(iv).
28

Discovery is not limited to the issues raised in the pleadings but encompasses any matter

3

1 that bears on or reasonably could lead to other matter that bears on any issues that is or may be in
2 the case. Oppenheimer Fund, Inc. v. Sanders, 437 U.S. 340, 351 (1978). However, discovery
3 does have ultimate and necessary boundaries. Oppenheimer Fund, Inc., 437 U.S. at 351. Rule 1
4 of the Federal Rules of Civil Procedure provides that the Federal Rules should be administered to
5 “secure the just, speedy, and inexpensive determination of every action and proceeding.”
6

III.

7

DISPUTED DISCOVERY REQUESTS
Plaintiff brings this motion to compel production of documents in response to requests

8

9 no. 18, 19, and 21, which are essentially requests for Defendants’ outbound call logs.
Plaintiff’s Requests for Production

10

A.

11

Plaintiff’s Request for Production No. 18 seeks “DOCUMENTS sufficient to IDENTIFY

12 ALL CALL RECIPIENTS who received PHONE CALLS in which YOU used TELEPHONE
13 DIALING EQUIPMENT.” (ECF No. 49 at 2.)2
Plaintiff’s Request for Production No. 19 seeks “DOCUMENTS sufficient to IDENTIFY

14

15 the total number of PHONE CALLS made to CALL RECIPIENTS in which YOU used
16 TELEPHONE DIALING EQUIPMENT.” (Id.)
Plaintiff’s request for production no. 21 seeks “DOCUMENTS sufficient to IDENTIFY

17

18 the total number of CALL RECIPIENTS.” (Id.)
Defendants’ Response

19

B.

20

Defendants responded to all three document requests at issue in this motion by

21 incorporating their general objections, and also specifically objected insofar as the requests
22 “seek[] discovery unrelated to class certification, which is outside the scope of discovery at this
23 time pursuant to the November 15, 2016 Phase II Scheduling Order.” (Id. at 2-4.) Defendants
24 also objected based on the attorney-client, work-product privileges, and because the requests,
25 and specifically, the terms “call recipients” and “phone calls,” are overbroad, unduly
26
27
28

2

All references to pagination of specific documents pertain to those as indicated on the upper right corners via the
CM/ECF electronic court docketing system.

4

1 burdensome, and not reasonably calculated to lead to the discovery of admissible evidence.3
2 (Id.) Defendants further objected because a protective order has not been entered in this case and
3 the requests seek confidential and/or trade secret information. (Id.)
4

C.

Definitions

5

The definition of “CALL RECIPIENTS” is “all persons to whom YOU, your agents or

6 anyone else acting on your behalf, placed PHONE CALLS.” (ECF No. 51 at 4.)
The definition of “PHONE CALLS” is “any calls made by YOU, your agents or anyone

7

8 else acting on your behalf.” (Id.)
The definition of “YOU” is “Defendants Zeta Interactive Corp., David A. Steinberg,

9

10 Ward Media, Inc., Education Bridge and any relevant predecessors, successors, subsidiaries,
11 departments, divisions, committees, and/or affiliates, and including, without limitation, any
12 organization or entity which it manages or controls, together with all present and former
13 directors, officers, employees, agents, representatives, attorneys, or any persons acting, or
14 purporting to act, on its behalf, including any call center or consulting firms retained, employed,
15 or consulted by DEFENDANTS in connection with PHONE CALLS.” (Id.)
16

IV.

17

DISCUSSION
Plaintiff requests that the Court issue an order compelling Defendants to produce a log of

18

19 all calls that it made during the relevant time period (February 16, 2012 through the present).
20 (ECF No. 49 at 4.) Defendants argue that these requests are overbroad, unduly burdensome, and
21 not reasonably calculated to lead to the discovery of admissible evidence. Plaintiff argues that
22 the call logs are highly relevant because the call logs are relevant to class considerations of
23 numerosity and commonality.

Plaintiff asserts that Defendants’ boilerplate objections are

24 unavailing because a protective order can address Defendants’ concerns and Defendants have not
25 provided any evidence to support their undue burden claims.
26
3

While Defendants objected to the requests for production because the information contained in the documents that

27 Plaintiff seeks is protected by attorney-client privilege and work-product privilege, Defendants do not raise these
arguments in the joint statement re discovery disagreement or in their updated statement re discovery disagreement.

28 Therefore, the Court does further discuss attorney-client privilege or work-product privilege in this order.
5

1

A.

Relevance and Proportionality of the Requested Call Logs

2

Rule 26, as recently amended, provides that a party “may obtain discovery regarding any

3 nonprivileged matter that is relevant to any party’s claim or defense and proportional to the
4 needs of the case, considering the importance of the issues at stake in the action, the amount in
5 controversy, the parties’ relative access to relevant information, the parties’ resources, the
6 importance of the discovery in resolving the issues, and whether the burden or expense of the
7 proposed discovery outweighs its likely benefit.” Fed. R. Civ. P. 26(b)(1). Information need not
8 be admissible in evidence to be discoverable. Fed. R. Civ. P. 26(b)(1). The December 2015
9 amendment to Rule 26 was to restore the proportionality factors in defining the scope of
10 discovery. See Advisory Committee Notes to Rule 26(b)(1) 2015 Amendment. Under the
11 amended Rule 26, relevancy alone is no longer sufficient to obtain discovery, the discovery
12 requested must also be proportional to the needs of the case. In re Bard IVC Filters Prod. Liab.
13 Litig., 317 F.R.D. 562, 564 (D. Ariz. 2016).
14

“Evidence is relevant if: (a) it has any tendency to make a fact more or less probable than

15 it would be without the evidence; and (b) the fact is of consequence in determining the action.”
16 Fed. R. Evid. 401. Relevancy to the subject matter of the litigation “has been construed broadly
17 to encompass any matter that bears on, or that reasonably could lead to other matter that could
18 bear on, any issue that is or may be in the case.” Oppenheimer Fund, Inc., 437 U.S. at 351.
19 Discovery is designed to help define and clarify the issues. Id. Although relevancy is broadly
20 defined for the purposes of discovery, it does have “ultimate and necessary boundaries.”
21 Gonzales v. Google, Inc., 234 F.R.D. 674, 680 (N.D. Cal. 2006) (citations omitted). “The party
22 who resists discovery has the burden to show discovery should not be allowed, and has the
23 burden of clarifying, explaining, and supporting its objections.” Blankenship v. Hearst Corp.,
24 519 F.2d 418, 429 (9th Cir. 1975).
25

“Prior to certification of a class action, discovery is generally limited and in the discretion

26 of the court.” Del Campo v. Kennedy, 236 F.R.D. 454, 459 (N.D. Cal. 2006) (citing Tracy v.
27 Dean Witter Reynolds, 185 F.R.D. 303, 304 (D. Co. 1998)). Generally, it is the plaintiff’s
28 burden to make a “prima facie showing that the class actions requirements of Federal Rule of

6

1 Civil Procedure 23 are satisfied or that discovery is likely to produce substantiation of the class
2 allegations.” Del Campo, 236 F.R.D. at 459 (quoting Tracy, 185 F.R.D. at 304).

Especially

3 when the material is in the possession of the defendant, the court should allow the plaintiff
4 enough discovery to obtain evidence as to whether a class action is maintainable. Doninger v.
5 Pac. Nw. Bell, Inc., 564 F.2d 1304, 1313 (9th Cir. 1977). The court should consider “the need
6 for discovery, the time required, and the probability of discovery providing necessary factual
7 information” in exercising its discretion to allow or prohibit discovery. Doninger, 564 F.2d at
8 1313.

“Yet where the plaintiffs fail to make even a prima facie showing of Rule 23’s

9 prerequisites, as we find here, the burden is on the plaintiff to demonstrate that discovery
10 measures are likely to produce persuasive information substantiating the class action
11 allegations.” Id. (citing Hatfield v. Williams, 64 F.R.D. 71, 75 (N.D. Iowa 1974)).
12

To make a prima facie showing under Rule 23(a) of the Federal Rules of Civil Procedure

13 a plaintiff must meet the prerequisites of numerosity, commonality, typicality, and adequacy of
14 representation. Plaintiff must show “(1) that the class is so numerous that joinder of all members
15 is impracticable; (2) that there are questions of law or fact common to the class; (3) that the
16 claims or defenses of the representative parties are typical of the claims or defenses of the class;
17 and (4) that the representative parties will fairly and adequately protect the interests of the class.”
18 Ogden v. Bumble Bee Foods, LLC, 292 F.R.D. 620, 622 (N.D. Cal. 2013) (internal punctuation
19 and citation omitted).
20

Plaintiff asserts that defendants in other TCPA cases regularly produce call logs. See

21 Thrasher v. CMRE Fin. Servs., Inc., 142 F. Supp. 3d 1083, 1086 (S.D. Cal. Mar. 30, 2015);
22 Gossett v. CMRE Fin. Servs., 142 F. Supp. 3d 1083, 1087 (S.D. Cal. Oct. 30, 2015); Gaines v.
23 Law Office of Patenaude & Felix, A.P.C., No. 13CV1556-JLS DHB, 2014 WL 3894348, at *3
24 (S.D. Cal. June 12, 2014); O’Shea v. Am. Solar Sol., Inc., No. 14CV894-L (RBB), 2016 WL
25 701215, at *3 (S.D. Cal. Feb. 18, 2016). The Court finds that at least some of Defendants’ call
26 logs are relevant to the Rule 23 requirements for Plaintiff’s claim. However, the Court now must
27 determine the scope of Defendants’ call logs that should be produced.
28 / / /

7

1

a.

Who the Calls were Made By

2

First, the Court addresses whether the calls logs should be limited based on who the calls

3 were made by. Defendants argue that Plaintiff’s request should be limited to only call logs for
4 calls made by Education Bridge. Defendants assert that telephone calls by other subsidiaries of
5 Defendant Zeta have nothing to do with Plaintiff’s claims in this action. Plaintiff contends that
6 he should receive all of Defendants’ call logs because he seeks to represent a class that includes
7 all calls made by Defendants. (ECF No. 53-1 at 6.)
Based upon the information before the Court, Defendant Zeta is a company with multiple

8

9 subsidiaries. (ECF No. 51 at 3-4.) The calls that were made to Plaintiff that are at issue in this
10 case were by Education Bridge, a subsidiary of Defendant Zeta. (FAC at ¶¶ 14-16, ECF No. 51
11 at 3.) Plaintiff argues that Education Bridge is just one of dozens of call campaigns that
12 Defendants have engaged in and that the class is not limited to Education Bridge. (ECF No. 53-1
13 at 6.)
Here, the November 15, 2016 phase two scheduling order provides that the motion to

14

15 certify the class must be filed on or before August 11, 2017. Currently, no such motion has been
16 filed. The definitions for the two proposed classes in Plaintiff’s first amended complaint are for
17 calls “made by or on behalf of Defendant in order to promote its products or services.” (FAC at
4
18 ¶¶ 19, 20.)

Plaintiff is seeking to determine how many people and the names of the people who were

19

20 contacted by any of the companies and call campaigns of Defendant Zeta. While the Court
21 considers Plaintiff’s class definitions in the first amended complaint, the other facts in the first
22 amended complaint and in the record do not justify imposing a significant burden on Defendant
23 Zeta to produce all of Defendant Zeta’s calls when it appears this case involves only one of
24 Defendant Zeta’s subsidiaries, Education Bridge. See Gusman v. Comcast Corp, 298 F.R.D.
25 592, 597 (S.D. Cal. April 2, 2014) (finding that the facts in the record do not justify imposing a
26 significant burden on defendant to produce an outbound dial list of marketing calls when it
27
28

4

The Court notes that Plaintiff filed a motion to amend his complaint on February 3, 2017, and the proposed second
amended complaint does not change the proposed classes. (ECF No. 55-1 at ¶¶ 23, 24.)

8

1 appears the case involves collection calls even though there are class allegations for marketing
2 calls). There presently is no representative plaintiff who fits the bill for any of the other
3 subsidiaries besides Education Bridge or any evidence in the record that the dialing system used
4 by Education Bridge is also used by the other subsidiaries.5
While the Court is to allow Plaintiff to conduct discovery to obtain evidence on whether a

5

6 class action is maintainable, based on the current record in this matter, Plaintiff’s requested
7 discovery for all of the call logs of Defendant Zeta is a fishing expedition. Courts do not have to
8 allow discovery whose purpose is a “fishing expedition.” Rivera v. NIBCO, Inc., 364 F.3d 1057,
9 1072 (9th Cir. 2004).
Therefore, the Court finds that the only call logs that Defendants have to produce at this

10

11 time are for calls made by Education Bridge.
12

b.

13

Second, the Court addresses the timeframe for the call logs that should be produced. The

Timeframe

14 parties agree that the timeframe should be the putative class period, which is February 16, 2012,
15 through present. Defendants indicate that Education Bridge uses a Noble System Dialer, which
16 contains data that can be queried to pull all the data Education Bridge keeps in association with
17 marketing calls. (ECF No. 51 at 6 n.3). However, Defendants indicate that it appears that call
18 records go back approximately three years per Education Bridge’s ordinary retention capabilities.
19 (Id.) Defendants cannot be required to produce information that is not in its possession.
Therefore, the Court finds that Defendants should produce the call logs for the putative

20

21 class period, February 16, 2012, through present, to the extent the call logs exist.
22

c.

The Purpose of the Phone Calls

23

Third, the Court addresses whether the call logs produced should be limited by the

24 purpose of the phone calls. Defendants argue that they should only have to produce marketing
25 telephone calls by Education Bridge, and not phone calls made by Defendant Zeta business
26
27
28

5

Further, the Court notes that while Plaintiff is seeking to amend his complaint, the proposed second amended
complaint only adds one plaintiff and there are no allegations that this new plaintiff, Plaintiff Rivas, was called by a
subsidiary other than Education Bridge. The second amended complaint actually does not specify which subsidiary
called Plaintiff Rivas. The allegations are that “Defendants called Plaintiff Rivas.” (ECF No. 55-1 at ¶¶ 18-19.)
The Court notes that Defendants contended during the hearing that Plaintiff Rivas was called by Education Bridge.

9

1 people for business purposes. Plaintiff counters that Defendants refuse to explain how they will
2 determine which calls fit into this category and which calls will be excluded.
3

Here, the allegations are that Plaintiff was called by Education Bridge and Ward Media.

4 (FAC at ¶¶ 1, 4, 15.) Based on the allegations in the first amended complaint, the calls were
5 made regarding “education leads.” (FAC at ¶¶ 16-17.) The definitions for the two proposed
6 classes in the first amended complaint are for calls “made by or on behalf of Defendant in order
7 to promote its products or services.” (FAC at ¶¶ 19, 20.) Calls that were made by Education
8 Bridge employees for business reasons, such as calls between two employees of Defendants, are
9 not relevant to this action. Based upon the first amended complaint, including the definitions of
10 the proposed classes, the only relevant calls are ones made to promote products or services.
11

Therefore, the Court finds that Defendants should produce calls made by Education

12 Bridge in order to promote its products or services.
Defendants’ Other Proposed Limitations for the Call Logs

13

d.

14

Fourth, the Court addresses Defendants’ arguments regarding other limitations to the call

15 logs. Defendants argue that the document requests should be limited to calls using an automatic
16 telephone dialing system (“ATDS”) where there is no prior express consent. Plaintiff counters
17 that Defendants refuse to disclose which systems are at issue, how they are determining whether
18 a system is ATDS, and which dialing systems are being excluded. Plaintiff contends that it is not
19 appropriate for Defendants to determine behind closed doors whether a dialing system
20 constitutes an ATDS and that is usually a contested issue in this type of case.
21

The Court agrees with Plaintiff and finds that whether calls were made using an ATDS or

22 occurred without prior express consent are contested issues in a TCPA case, and Defendants are
23 not allowed to only produce the call lists for calls that they believe meet the definition of using
24 an ATDS or that they believe were made without prior express consent.
25

Accordingly, considering the relevance to Plaintiff’s claim and the proportionality to the

26 needs of the case, the Court finds that Plaintiff’s request for Defendants’ call logs should be
27 granted, but limited to only calls made by Education Bridge, during the putative class period,
28 February 16, 2012, through present, in order to promote its products or services.

10

1

B.

The Format of the Discovery of the Call Logs

2

Next, the parties dispute the proper format of the discovery of the call logs. Specifically,

3 the parties dispute whether the call logs should be produced or inspected and the manner for
4 doing so. Defendants assert that Education Bridge does not maintain a list of calls or call
5 recipients, but the information is stored in Defendant Zeta’s proprietary source code. Defendants
6 contend that in order to produce a call list like that which Plaintiff seeks, one must access
7 Defendant Zeta’s source code and run various commands or scripts to create it. Based on this,
8 Defendants assert that Plaintiff’s counsel may view the source code and data, with an expert of
9 Plaintiff’s choice, who has been vetted by Defendants’ counsel, in a secure location on a secure
6
10 laptop. Defendants also contend that for Plaintiff to prove his allegations, he will need to

11 examine the source code.
Plaintiff argues that a comprehensive protective order should obviate the need for an in-

12

13 person inspection of the documents. Plaintiff asserts that Defendants have not provided Plaintiff
14 with a single example of a document request that would require Defendants to produce their
15 source code and how producing the call logs would entail producing Defendants’ source code.
On the subject of ESI, the Federal Rules state:

16

(E)
Producing the Documents or Electronically Stored
Information. Unless otherwise stipulated or ordered by the court,
these procedures apply to producing documents or electronically
stored information:
(i) A party must produce documents as they are kept in the usual
course of business or must organize and label them to correspond
to the categories in the request;
(ii) If a request does not specify a form for producing
electronically stored information, a party must produce it in a form
or forms in which it is ordinarily maintained or in a reasonably
usable form or forms; and
(iii) A party need not produce the same electronically stored
information in more than one form.

17
18
19
20
21
22
23

24 Fed. R. Civ. P. 34(b)(2)(E). The 2006 Advisory Committee Notes for Rule 34 further state:
25
6

Defendants indicated in their statement re discovery dispute that they have offered to provide to counsel for

26 Plaintiff the call record data for all education lead call recipients retained by Education Bridge on a secure laptop in

Florida pursuant to the parameters specified in Defendants’ proposed protective order. At the hearing, Defendants

27 discussed the possibility of putting the data on servers and the servers being viewed by Plaintiff’s counsel and
28

Plaintiff’s expert at a secure location in New York City or in Michigan, which is the location of Plaintiff’s expert.

11

1
2
3
4
5
6
7
8
9
10
11
12
13
14

If the requesting party is not satisfied with the form stated by the
responding party, or if the responding party has objected to the
form specified by the requesting party, the parties must meet and
confer under Rule 37(a)(2)(B) in an effort to resolve the matter
before the requesting party can file a motion to compel. If they
cannot agree and the court resolves the dispute, the court is not
limited to the forms initially chosen by the requesting party, stated
by the responding party, or specified in this rule for situations in
which there is no court order or party agreement.
...
Rule 34(a) requires that, if necessary, a responding party
“translate” information it produces into a “reasonably usable”
form. Under some circumstances, the responding party may need
to provide some reasonable amount of technical support,
information on application software, or other reasonable assistance
to enable the requesting party to use the information. The rule does
not require a party to produce electronically stored information in
the form it which it is ordinarily maintained, as long as it is
produced in a reasonably usable form. But the option to produce in
a reasonably usable form does not mean that a responding party is
free to convert electronically stored information from the form in
which it is ordinarily maintained to a different form that makes it
more difficult or burdensome for the requesting party to use the
information efficiently in the litigation. If the responding party
ordinarily maintains the information it is producing in a way that
makes it searchable by electronic means, the information should
not be produced in a form that removes or significantly degrades
this feature.

15
16 Fed. R. Civ. P. 34 advisory committee’s note.
17

While a responding party is not required to create documents responsive to a request for

18 production, it must produce or permit for inspection reasonably accessible electronically stored
19 information. See Fed. R. Civ. P. 34(a)(1)(A).
20

Here, Defendants have not shown that Plaintiff would actually be required to view the

21 source code in order to see the call logs.

While Defendants assert that one must access

22 Defendant Zeta’s source code and run various scripts or commands to create the call logs,
23 Defendants have not explained why they cannot just run the scripts or commands and create the
24 call logs and then turn over the call logs to Plaintiff. Defendants stated at the hearing that
25 Plaintiff’s expert could go to the secure location and run the queries on the data to produce the
26 information that she needs and then could request production of the call logs in accordance with
27 Defendants’ proposed protective order. However, it appears to the Court that Defendants are
28 capable of running the scripts and commands on the data and producing the call logs as specified

12

1 in this order. Plaintiff’s expert can then evaluate the data that has been produced and run the
2 data through programs, which according to Plaintiff’s statement at the hearing, may take weeks.7
3 While Defendants argued at the hearing that the distribution list of names is as important as or
4 even more important than the source code, the call logs will be covered by a protective order,
5 which will restrict who has access to the call logs and for what purpose the call logs may be
6 used. Although Defendants contend that Plaintiff will need to view the source code to prove his
7 allegations, Plaintiff is not requesting to view the source code.
Therefore, the Court, in its discretion and considering the circumstances of this case,

8

9 finds that the call logs should be produced in an electronic format. Plaintiff should not be
10 required to have to personally inspect the data on a computer at a certain location during a set
11 time. If Defendants are incapable of producing the call logs in an electronic format, they may
12 request an evidentiary hearing before the Court.
13

C.

Protective Order

14

Last, the Court addresses the parties’ arguments regarding which protective order should

15 be entered in this action based on the call logs beings produced. Both parties have submitted
16 proposed protective orders in this matter. Plaintiff requests that the Court adopt the Northern
17 District of California Model Protective Order.8 Defendants assert that their proposed protective
18 order, which they filed on January 31, 2017, is necessary to protect Defendant Zeta’s proprietary
19 source code and highly sensitive data. Defendants’ proposed protective order is based upon the
20 Northern District of California’s Model Protective Order for Litigation Involving Patents, Highly
21 Sensitive Confidential Information and/or Trade Secrets, but also includes additions and changes
22 to the source code and highly sensitive data section.
Here, Defendants will not be producing their actual source code to Plaintiff, but the data

23
24
25
26
27
28

7

The Court notes that Defendants’ proposed protective order says that “t]he Receiving Party may request production
of limited portions of ESI that are reasonably necessary for the preparation of court filings, pleadings, expert reports,
or other papers, or for disposition or trial.” (ECF No. 51-1 at 15.) Defendants’ proposed protective order would
only permit Plaintiff and Plaintiff’s expert to have a limited amount of the call logs produced, instead of all of the
call logs which the Court finds should be produced.
8

The model protective order can be found at http://www.cand.uscourts.gov/filelibrary/407/CAND_Standard
ProtOrd.pdf.

13

1 from the source code. As discussed above, the Court finds that Defendants should produce the
2 call logs rather than requiring Plaintiff to inspect the data at a secure location at a set time.
3 Therefore, the sections of Defendants’ proposed protective order regarding the procedure for
4 inspecting the data at a set location are not applicable. The parties shall file a stipulated
5 protective order based upon the Northern District of California’s Model Protective Order for
6 Litigation Involving Patents, Highly Sensitive Confidential Information and/or Trade Secrets, but
7 excising portions that are inconsistent with this order, within ten (10) days of the date of entry of
8 this order.9
9

V.

10

ORDER

11

Based on the foregoing, IT IS HEREBY ORDERED that:

12

1. Plaintiff’s motion to compel production of documents responsive to request for
production nos. 18, 19, and 21 is GRANTED IN PART;

13
14

2. Defendants shall produce the call logs for calls made by Education Bridge, during the

15

putative class period, from February 16, 2012, through present, in order to promote its

16

products or services, in an electronic format within twenty-one (21) days of the date

17

of entry of this order; and

18

3. The parties shall file a stipulated protective order based upon the Northern District of

19

California’s Model Protective Order for Litigation Involving Patents, Highly

20

Sensitive Confidential Information and/or Trade Secrets, but excising portions that

21

are inconsistent with this order, within ten (10) days of the date of entry of this order.

22
23

IT IS SO ORDERED.

24 Dated:

February 10, 2017
UNITED STATES MAGISTRATE JUDGE

25
26
27
9

The model protective order can be found at http://www.cand.uscourts.gov/filelibrary/776/ND_Cal_Patent_Highly_

28 Sensitive_Model_Prot_Ord_Revised.docx.

14