Reynolds and Reynolds Company v. Brnovich

CourtDistrict Court, D. Arizona
DecidedApril 2, 2020
Docket2:19-cv-04849
StatusUnknown

This text of Reynolds and Reynolds Company v. Brnovich (Reynolds and Reynolds Company v. Brnovich) 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
Reynolds and Reynolds Company v. Brnovich, (D. Ariz. 2020).

Opinion

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

9 CDK Global LLC, et al., No. CV-19-04849-PHX-GMS

10 Plaintiffs, ORDER

11 v.

12 Mark Brnovich, et al.,

13 Defendants,

14 and

15 Arizona Automobile Dealers Association,

16 Intervenor Defendant. 17 18 Pending before the Court is Defendant Arizona Department of Transportation 19 (“ADOT”) Director John S. Halikowski’s Motion to Dismiss for Lack of Subject Matter 20 Jurisdiction. (Doc. 38.) The Motion is granted.1 21 BACKGROUND 22 Plaintiffs CDK Global LLC, et al. (“Plaintiffs”) develop, own, and operate 23 proprietary computer systems known as dealer management systems (“DMSs”) that 24 process vast amounts of data2 sourced from various parties. Automotive dealerships hold 25 licenses to DMSs to help manage their business operations, including handling confidential

26 1 The parties have requested oral argument. Those requests are denied because the parties have had an adequate opportunity to discuss the law and evidence and oral argument will 27 not aid the Court’s decision. See Lake at Las Vegas Investors Group, Inc. v. Pac. Malibu Dev., 933 F.2d 724, 729 (9th Cir. 1991). 28 2 E.g., social security numbers, driver’s license numbers, and proprietary pricing data. 1 consumer and proprietary data, processing transactions, and managing data 2 communications between dealers, customers, car manufacturers, credit bureaus, and other 3 third parties. Plaintiffs employ multiple technological measures—such as secure login 4 credentials, CAPTCHA prompts, and comprehensive cybersecurity infrastructure, 5 hardware, and software—to safeguard their DMS systems from unauthorized access or 6 breach. Plaintiffs also contractually prohibit dealers from granting third parties access to 7 their DMSs without Plaintiffs’ authorization. 8 In March 2019, the Arizona Legislature passed the Dealer Data Security Law (“the 9 Law”). A.R.S. §§ 28-4651–28-4655. The Law went into effect on August 27, 2019.3 The 10 Law regulates the relationship between DMS licensers like Plaintiffs and the dealerships 11 they serve. Under the Law, DMS providers may no longer “[p]rohibit[] a third party that 12 has satisfied or is compliant with . . . current, applicable security standards published by 13 the standards for technology in automotive retail [(STAR standards)] . . . from integrating 14 into the dealer’s [DMS] or plac[e] an unreasonable restriction on integration . . . .” A.R.S. 15 §§ 28-4653(A)(3)(b), 28-4651(9). The Law also requires DMS providers to “[a]dopt and 16 make available a standardized framework for the exchange, integration and sharing of data 17 from [a DMS]” that is compatible with STAR standards and to “[p]rovide access to open 18 application programming interfaces to authorized integrators.” A.R.S. § 28-4654(A). 19 Finally, a DMS provider may only use data to the extent permitted in the DMS provider’s 20 agreement with the dealer, must permit dealer termination of such agreement, and “must 21 work to ensure a secure transition of all protected dealer data to a successor dealer data 22 vendor or authorized integrator” upon termination. A.R.S. §§ 28-4654(B)(1)-(3). 23 Plaintiffs filed the underlying complaint seeking declaratory and injunctive relief 24 from the Law on July 29, 2019. This Motion to Dismiss for Lack of Subject Matter 25 Jurisdiction followed on September 18, 2019. 26 27 3 However, Defendants stipulated on September 4, 2019 that they would “take no action to 28 enforce Arizona House Bill 2418 (2019) for the pendency of Plaintiffs’ Motion for Preliminary Injunction in this Court.” (Doc. 28 at 2.) 1 DISCUSSION 2 I. Legal Standard 3 “For a case or controversy to exist under Article III, a plaintiff must have standing 4 to assert his legal claims, those claims must be ripe for review, and the harm must be 5 redressable against the defendants.” Ariz. Contractors Ass’n, Inc. v. Napolitano, 526 F. 6 Supp. 2d 968, 977 (D. Ariz. 2007) (citing Renne v. Geary, 501 U.S. 312, 320 (1991), as 7 amended (Dec. 10, 2007), corrected, No. CV07-1355-PHX-NVW, 2007 WL 9723967 (D. 8 Ariz. Dec. 10, 2007), and aff’d sub nom. Chicanos Por La Causa, Inc. v. Napolitano, 544 9 F.3d 976 (9th Cir. 2008). Redressability in this context means that “it must be likely, as 10 opposed to merely speculative, that the injury will be redressed by a favorable decision.” 11 Planned Parenthood Ariz., Inc. v. Brnovich, 172 F. Supp. 3d 1075, 1086 (D. Ariz. 2016) 12 (quoting Lujan v. Defs. of Wildlife, 504 U.S. 555, 561 (1992)). “It is well-established that 13 when a plaintiff brings a pre-enforcement challenge to the constitutionality of a particular 14 statutory provision, the causation element of standing requires the named defendants to 15 possess authority to enforce the complained-of provision,” Ariz. Contractors, 526 F. Supp. 16 2d at 983 (quoting Bronson v. Swensen, 500 F.3d 1099, 1110 (10th Cir. 2007)); “a 17 generalized duty to enforce state law or general supervisory power over the persons 18 responsible for enforcing the challenged provision will not subject an official to 19 suit,” Planned Parenthood, 172 F. Supp. 3d at 1086 (quoting Coalition to Defend 20 Affirmative Action v. Brown, 674 F.3d 1128, 1134 (9th Cir. 2012)). 21 II. Analysis 22 The Plaintiffs have failed to demonstrate any harm that could be redressable against 23 Defendant Halikowski. Although the Director is generally “responsible for the 24 administration of the department,” A.R.S. § 28-331(B), nothing authorizes him to 25 prosecute or enforce all of the laws contained within the thirty chapters of Title 28, see, 26 e.g., A.R.S. §§ 28-363(A), 28-364, 28-367. Instead, in areas where the legislature intended 27 the director to have enforcement authority, it expressly provided for such authority. See, 28 e.g., A.R.S. §§ 28-3411 (“The director shall administer and enforce this article,” regarding 1 traffic survival school); 28-4002 (“The director shall . . . [a]dminister and enforce this 2 chapter,” regarding vehicle insurance); 28-5602 (“The following persons have authority to 3 enforce this article: 1. The director of the department of transportation,” regarding fuel 4 taxes). Those provisions would be superfluous if the Director had comprehensive authority 5 to enforce all aspects of Title 28. See Boise Cascade Corp. v. U.S. EPA, 942 F.2d 1427, 6 1432 (9th Cir. 1991) (“Under accepted canons of statutory interpretation, we must interpret 7 statutes as a whole, giving effect to each word and making every effort not to interpret a 8 provision in a manner that renders other provisions of the same statute inconsistent, 9 meaningless or superfluous.”).

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

Related

Renne v. Geary
501 U.S. 312 (Supreme Court, 1991)
Lujan v. Defenders of Wildlife
504 U.S. 555 (Supreme Court, 1992)
Nova Health Systems v. Fogarty
416 F.3d 1149 (Tenth Circuit, 2005)
Bronson v. Swensen
500 F.3d 1099 (Tenth Circuit, 2007)
Coalition to Defend Affirmative Action v. Brown
674 F.3d 1128 (Ninth Circuit, 2012)
Jean Patou, Inc. v. Theon, Inc.
9 F.3d 971 (Federal Circuit, 1993)
Planned Parenthood Arizona, Inc. v. Brnovich
172 F. Supp. 3d 1075 (D. Arizona, 2016)

Cite This Page — Counsel Stack

Bluebook (online)
Reynolds and Reynolds Company v. Brnovich, Counsel Stack Legal Research, https://law.counselstack.com/opinion/reynolds-and-reynolds-company-v-brnovich-azd-2020.