On June 11, 2026, a California federal court dismissed with prejudice a proposed class action against AutoNation, Inc. alleging that its third-party call-analytics vendor, Invoca, recorded, transcribed and analyzed calls to California dealerships without callers’ consent. See Xavier v. AutoNation, Inc., No. 5:25-cv-00731-AB (DTBx) (C.D. Cal. June 11, 2026). The court did not decide whether the alleged conduct violated the California Invasion of Privacy Act(CIPA); instead, it held that the plaintiff failed to show AutoNation—the out-of-state parent company and defendant—had itself directed the challenged conduct at California. The decision provides a potentially important personal jurisdiction defense for out-of-state companies using nationwide systems without California-specific deployment or direction.
The allegations
The plaintiff alleged that Invoca was the third-party vendor that recorded customer calls, converted them into searchable transcripts and structured data and used artificial intelligence (AI) to analyze caller intent, call outcomes, employee performance and marketing effectiveness. AutoNation was the parent-company defendant, while the California dealerships that received the calls were operated by AutoNation subsidiaries.
According to the complaint, Invoca was not merely functioning as a passive recording tool. The plaintiff alleged that Invoca processed the communications before providing results to AutoNation and could use call data for its own purposes, including research, product improvement and marketing. The plaintiff asserted claims under CIPA Sections 631 and 632 based on the alleged interception and recording of calls without consent.
Those theories, however, were never tested on the merits because the court dismissed the action for lack of personal jurisdiction.
Why the court found no personal jurisdiction
Because AutoNation was not a California resident, the plaintiff was required to show that AutoNation purposefully directed the relevant conduct at California.
The court concluded that the plaintiff had not done so. It emphasized that the jurisdictional analysis must focus on AutoNation’s own contacts with California—not merely the California residence of callers, Invoca’s location or the activities of AutoNation subsidiaries operating dealerships in the state.
The plaintiff alleged that AutoNation contracted with California-based Invoca and that Invoca’s services were used in connection with California dealerships. But the court found no facts showing that AutoNation:
- Deployed or configured the platform differently in California
- Adopted California-specific call-recording policies
- Directed its subsidiaries to use the platform in a California-specific manner
- Otherwise targeted California customers or the California market through the challenged conduct
Instead, the record reflected that the platform was deployed across AutoNation subsidiaries nationwide, without California-specific functionality or instructions. In other words, the plaintiff alleged a chain in which AutoNation hired Invoca, Invoca provided services used by AutoNation subsidiaries and those subsidiaries interacted with California consumers. The court found this to be insufficient and not conduct expressly aimed at California by AutoNation itself.
The plaintiff had already amended the complaint twice, including once after the court identified the jurisdictional deficiencies. The court therefore concluded that another amendment would be futile and dismissed the case with prejudice.
The CIPA claims the court did not reach
Although the court dismissed the case on personal jurisdiction grounds, the complaint reflected several theories that continue to appear in CIPA litigation.
The plaintiff asserted claims under CIPA Sections 631(a) and 632(a). Section 631(a) generally addresses wiretapping and the unauthorized reading, learning or use of communications while they are in transit, as well as aiding, employing or conspiring with another person to engage in that conduct. Section 632(a) generally prohibits the intentional recording or eavesdropping on a confidential communication without the consent of all parties. California is often described as a “two-party consent” state, but “all-party consent” is more precise: each participant generally must consent before a confidential telephone call is recorded or eavesdropped on.
Here, the plaintiff alleged that Invoca was not merely acting as a passive “tape recorder.” Compl., Reyes v. AutoNation, Inc., No. 5:25-CV-731-AB-DTB, C.D. Cal., Feb. 4, 2026. Instead, the complaint alleged that Invoca recorded calls, created transcripts, analyzed call content using AI, generated insights, stored call data and had the ability to use the information for its own internal purposes, including platform improvement, research and marketing. The plaintiff also alleged that AutoNation aided or employed Invoca’s alleged interception by contracting for, paying for and implementing the technology on customer service phone lines.
Why the decision matters
The decision is useful for out-of-state companies that operate nationwide systems but do not specifically direct the challenged activities at California.
The court’s focus was on AutoNation’s own conduct. The mere presence of California callers, California subsidiaries and a California-based vendor did not establish jurisdiction without facts tying AutoNation itself to the challenged California activity.
However, the ruling is not a shield from CIPA claims. Personal jurisdiction is fact-specific, and the outcome may differ where a company itself operates California-facing systems, directly collects information from California users, makes state-specific deployment decisions or exercises substantial control over California operations.
It is also important to note that the court did not decide whether the alleged call recording, transcription, AI analysis or vendor data use violated CIPA. A jurisdictional dismissal prevents the claims from proceeding in that court; it does not resolve the underlying compliance questions or necessarily prevent litigation in another appropriate forum.
What can businesses do now in light of this case?
Although CIPA claims involving third-party technologies remain an active area of litigation, businesses can take practical steps to reduce risk, strengthen potential defenses and develop a defensible factual record regarding how those tools are selected, configured and used.
Understand and document who controls the technology
Identify which entity selects the vendor, configures the platform, determines applicable policies, controls local implementation and accesses the resulting data. Agreements and operational practices should accurately reflect the responsibilities of parent companies, subsidiaries, affiliates and vendors. Note that it is common practice for vendors to include a Data Processing Agreement (DPA) as an attachment to their agreements, and DPAs commonly include provisions to comply with the California Consumer Privacy Act. Had Invoca used a DPA in its agreement, the court may have reached a different result.
Test the technology as deployed
Technical testing should confirm whether the technology is operating as intended (for example, whether any data is captured before notice or consent, what information reaches the vendor and whether the vendor is collecting more data than it is authorized to).
Provide notice before collection begins
In California and other all-party consent jurisdictions, companies should evaluate whether users receive sufficiently clear notice and any required consent.
Limit vendor use of communications
Contracts should clearly address whether the vendor may use collected or derived data for model training, product improvement, research, benchmarking or marketing. Appropriate restrictions should also cover retention, deletion, subprocessors, security and access rights.
Keep disclosures and implementation aligned
Call scripts, privacy notices, contracts, platform settings and actual data flows should tell the same story. Companies should retest after material configuration changes, vendor updates, new AI features or changes to call-routing systems.
Personal jurisdiction may provide a meaningful threshold defense for an out-of-state company that did not target California. It should not, however, be treated as a substitute for substantive compliance. The stronger approach is to understand both where operational decisions are made and how the technology actually handles customer communications before a demand letter or lawsuit puts those facts at issue.