Skip to main content
Photo of a Law Library

Over-the-Air in Personam: Purposeful Availment Through Over-the-Air Updates

PDF

Samuel R. Boyd[1]*

“We’re a court . . . . We really don’t know about these things. You know, these are not like the nine greatest experts on the internet.”

Associate Justice Elena Kagan.[2]**

Introduction

A court must have personal jurisdiction over every party to a suit before it can pass binding judgment. And yet, personal jurisdiction law is ever more complicated by modern technology. In fact, the Supreme Court has not provided any specific guidance on how to analyze contacts made possible through modern technology in its personal jurisdiction precedent. Lower courts have been left to apply the Court’s general rules to various technologies, developing and applying different tests to help distinguish when such contacts are sufficient for jurisdiction to follow. Precedent regarding the ramifications of internet contacts is particularly unsettled. However, this paper will show that as technologies improve and become more impactful, the analysis regarding whether such technology should convey personal jurisdiction may actually become easier because such technological contacts more clearly meet the general tests laid down by the Supreme Court.

One example of such technology is over-the-air updates (OTAUs). OTAUs have been around for a few decades, but are becoming increasingly popular, powerful, and integral to product lifecycles. This technology, particularly as deployed by Tesla for its automobiles, has significant impacts on updated products and the safety of those around the product. This paper will show that OTAU usage can be a legitimate basis for in personam personal jurisdiction over an entity, even where it has not directed other significant activity towards a forum.

This paper proceeds in the following sections: Section II presents Supreme Court precedent necessary to understand in personam personal jurisdiction; Section III explains OTAUs and how they function; and Section IV applies OTAUs to personal jurisdiction precedent through a case study—Tesla’s OTAU usage in relation to South Carolina.

In Personam Personal Jurisdiction Precedent Overview

Personal jurisdiction requirements are derived almost entirely from the Due Process Clause’s requirement that defendants have an adequate ability to defend themselves through notice of litigation.[3] There are two kinds of personal jurisdiction: in personam, which is personal jurisdiction over a party before the court; and in rem, which is personal jurisdiction over a piece of property subject to litigation.[4] This paper deals entirely with in personam jurisdiction. In the seminal case for modern in personam personal jurisdiction law, International Shoe Company v. Washington, the Supreme Court made clear that the main issue in personal jurisdiction analysis is whether exercising jurisdiction comports with “traditional notions of fair play and substantial justice.”[5] A secondary consideration is comity between the states, but this concern has never been determinative in Supreme Court precedent.[6]

Once a party has been properly served, state courts obtain personal jurisdiction through state legislators passing “long-arm” statutes.[7] Federal courts also gain personal jurisdiction this way, among others, because federal courts have essentially the same jurisdiction as their state court counterparts.[8] Such long-arm statutes properly confer personal jurisdiction on courts in the vast majority of circumstances, but, in fringe cases, such statutes are so broad that the Supreme Court invalidates them in accordance with Due Process.[9] As a court’s jurisdiction arising from a long-arm statute must also be fairly exercised, whether a court has personal jurisdiction over a defendant is based on a two-pronged test: (1) whether the state long-arm statute provides personal jurisdiction over the defendant under the facts, and (2) if so, whether such provision complies with constitutional due process requirements.[10]

There are two approaches legislatures use when crafting state long-arm statutes.[11] The first method, which is the more traditional method, is to enumerate circumstances in which the state may exercise jurisdiction. Historically, it was this kind of statute that occasionally granted jurisdiction to state courts in circumstances that would otherwise be improper under the constitutional analysis of fair play and substantial justice.[12] That is why the Supreme Court developed the second prong. The second method is to craft a long-arm statute saying the state will exercise jurisdiction to the full extent allowed under the United States Constitution.[13] This collapses the above two prong test into just the second prong.[14] Regardless of the specifics of a long-arm statute, there are three ways to establish personal jurisdiction under the test: traditional ways, contacts-based general personal jurisdiction, and contacts-based specific personal jurisdiction.

Traditional Ways to Establish Personal Jurisdiction

There are a few traditional ways to establish personal jurisdiction over a party by meeting both prongs of the above test: (1) showing that the party is a citizen of the forum state; (2) in certain circumstances, serving the party with process in the forum state; (3) the party’s waiver of any personal jurisdiction defense; and (4) the party’s consent to suit.[15]

Courts have personal jurisdiction over an entity that is a “citizen” of the state in which it sits.[16] An individual’s place of citizenship is where the individual is domiciled.[17] A corporation, on the other hand, is citizen of the state in which it is incorporated and the state that is its “principal place of business.”[18] A corporation’s principal place of business is generally where its “nerve center” (i.e., its headquarters) is located.[19] Furthermore, in unique circumstances, properly serving an individual with process, known as “tagging” can establish personal jurisdiction in that forum.[20] Additionally, all personal jurisdiction arguments are also waivable by failing to object to a court’s adjudication of a claim against a defendant.[21]

In a similar vein as waiver, parties may consent to personal jurisdiction.[22] That is why personal jurisdiction arguments are usually only an issue for defendants—plaintiffs necessarily consent to suit by filing a claim.[23] Recently, business registration statutes have been central to the discussion of consenting to personal jurisdiction. In Mallory v. Norfolk Southern, the Supreme Court held that Pennsylvania’s foreign business registration statute conferred personal jurisdiction over a corporation doing business in the state under the traditional consent theory.[24] In Mallory, there were two Pennsylvania statutes at issue, 15 Pa. Cons. Stat. § 411 and 42 Pa. Cons. Stat. § 5301(a)(2)(i), (b).[25] Per § 411, any non-Pennsylvania based corporation must register with the Pennsylvania Secretary of State to do business within its borders.[26] Further, § 5301(a)(2)(i) explicitly said that, by registering under § 411, the foreign corporation consented to “any cause of action” levied against it in the state.[27] Despite the defendant’s argument that such sweeping jurisdiction would be unfair and would improperly take too many cases away from other states, the Court held that, because the defendant had “taken full advantage of its opportunity to do business in [Pennsylvania]” and had followed the statutes to a tee, exercising jurisdiction in this way was fair.[28]

The final and most complicated way to establish personal jurisdiction is through contacts analysis.[29] Such analysis tallies up all the ways that a defendant has interacted with the forum, and then asks whether such interaction makes it fair for the defendant to be haled into litigation there.[30] There are two kinds of contacts-based personal jurisdiction, general and specific. General personal jurisdiction allows a court to hear any type of litigation against a party, but specific personal jurisdiction only allows a court to hear claims that “arise out of or relate to” the state specific contacts that created such specific personal jurisdiction.[31] Both of these arise from the Court’s language in International Shoe, stating that a state’s courts may be properly authorized to assert personal jurisdiction so long as such assertion comports with “traditional notions of fair play and substantial justice” guaranteed by the due process clause.[32]

Contacts-Based General Personal Jurisdiction Precedent: The “At Home” Test

Contacts establish general personal jurisdiction for any cause of action against a corporation in a forum where its contacts make it “at home” in the forum. The first iteration of general personal jurisdiction by consequence of contacts analysis was created by the Supreme Court in Perkins v. Benguet Consolidated Mining Co. when it held that a court can constitutionally exercise jurisdiction over a defendant if the defendant had “continuous and systematic” contacts in the state at the time of service.[33]

In Perkins, the Court held that the defendant had continuous and systematic contacts with Ohio where the defendant mining company’s president returned to Ohio to run the company from home but the company had no mining operations in Ohio.[34] The plaintiff sued the defendant for losses related to the mining company’s alleged improper dividend reimbursement and failure to issue additional shares.[35] The company at no point ran any mining operation in Ohio, but had to temporarily halt all mining operations elsewhere due to the Second World War.[36] However, the president’s activities in Ohio included operating bank accounts, sending employee salary checks, rehabilitating closed mining operations overseas, exchanging business related correspondence, and housing of company files.[37] The president was served by the plaintiff as these interim operations were ongoing.[38] The Court reasoned that the president’s activities, despite the fact that no mining operations were conducted in Ohio, were sufficient to give the defendant fair notice of potential litigation in all forms because such contacts constituted “continuous and systematic supervision of the necessarily limited wartime activities of the company.”[39] Therefore, the Court held that the Ohio courts could exercise general personal jurisdiction over the defendant, even for the unrelated claim regarding share and dividend dispersal.[40]

While the continuous and systematic test was never overruled, the Court clarified in Daimler AG v. Bauman that the test requires continuous and systematic contact such that the company can be rightly considered “at home” in that state.[41] In Daimler, the Court held that general personal jurisdiction was improper where the defendant was sued in California District Court based on the contacts of one of the defendant’s subsidiary companies.[42] The defendant in Daimler was “a German public stock company, headquartered in Stuttgart, that manufacture[d] Mercedes–Benz vehicles in Germany.”[43] One of its subsidiaries operated in the United States to distribute the defendant’s vehicles to dealers, including dealers in California.[44] However, the subsidiary was incorporated in Delaware and its principal place of business was New Jersey.[45] The plaintiffs, citizens of Argentina, brought a claim under the Alien Tort Statute.[46] The plaintiff argued that California could exercise personal jurisdiction over the defendant in this unrelated suit because its subsidiary’s contacts with California were continuous and systematic in nature, thus justifying general personal jurisdiction under the reasoning of Perkins.[47]

The Court rejected the plaintiff’s argument as an expansive and “unacceptably grasping” standard.[48] The Court reasoned that general personal jurisdiction, while not exclusively available over a corporation in its state of incorporation or its principal place of business, should only be available in instances where the contacts are similarly extensive.[49] The Court said the defendant, even assuming the contacts of its subsidiary were transferable to it, had only a small part of its business conducted in California and could not fairly be expected to defend all potential suits in that forum.[50] Thus, the Court held that a corporation must essentially be “at home” in a forum to be subject to general personal jurisdiction.[51]

This additional language greatly restricted prevailing notions of when general personal jurisdiction was proper. However, the Court maintains that the Daimler decision did not overrule, or even conflict with, the Perkins decision; stating that Perkins was an unusual circumstance where the corporation’s principal place of business temporarily became Ohio, thus making the defendant essentially at home in Ohio even if the Court did not use that language to describe it in the decision.[52]

The Court applied this rule again in BNSF Ry. Co. v. Tyrrell where it held that the defendant corporation was not “at home” in Montana because it was not incorporated or headquartered there, and its approximately 2,000 employees and 2,000 miles of railroad track in the state were insufficient because the company had contact with many other states in a similar fashion.[53] The Court cited the reasoning from Daimler that “the general jurisdiction inquiry does not focus solely on the magnitude of the defendant’s in-state contacts. . . . [a] corporation that operates in many places can scarcely be deemed at home in all of them.”[54] This means that to be “at home” a corporations contacts in a state must be (1) continuous and systematic, (2) uniquely larger than its contacts in other states of which it is not a citizen, and (3) of similar or greater magnitude than its contacts within its state(s) of citizenship.

Contacts-Based Specific Personal Jurisdiction Precedent: Purposeful Availment

Specific personal jurisdiction arises from “minimum contacts” analysis.[55] Minimum contacts exist where a party “purposefully avails itself of the privilege of conducting activities within the forum State.”[56] Courts break that down into the following three elements: (1) whether the defendant purposefully availed itself of conducting business in the forum, (2) whether the claim sufficiently arises from or relates to such availment, and (3) if both are true, whether exercising jurisdiction would be fair and reasonable.[57] The second and third elements are dependent on the first element and include highly fact-specific inquiries. Consequently, courts have described purposeful availment as the “sine qua non for in personam jurisdiction.”[58]

As the remainder of this Section demonstrates, the Supreme Court has found purposeful availment in the following three general categories of cases that are distinguishable by the type of contacts in each: direct and/or targeted effects contacts, stream-of-commerce contacts, and expected relationships contacts. Some cases within these categories include contacts that fit under the logic of another category, but each case will be discussed within the type of reasoning that seemingly provided the most force for the decision.

Direct and/or Targeted Effects Contacts

Direct contact cases are the simplest and include the kinds of contacts that are rarely debated like physical presence. One of many examples is Keeton v. Hustler Magazine, Inc., in which the Court held that the defendant magazine had sufficiently availed itself of the forum’s laws by circulating its magazines such that it should anticipate being sued for any libelous content in those magazines.[59] The defendant magazine company in Keeton was a citizen of Ohio and California.[60] The plaintiff made five libel allegations in a suit in New Hampshire, despite being a resident of New York.[61] Those libel allegations were combined claims for all nationwide publications, not just the New Hampshire ones.[62] The defendant consistently circulated between 10,000 and 15,000 magazines in New Hampshire.[63]

The Court held that the defendant could foresee being sued in New Hampshire based on the content of its magazines because it circulated magazines in the state, saying that such circulation constituted purposeful availment that looks entirely different from “random, isolated, or fortuitous” contacts.[64] Furthermore, despite the lower court’s reasoning that New Hampshire was not a sufficiently interested forum to have jurisdiction over the libel that arose from nationwide publications, the Court held that states have a heightened interest in adjudicating torts that occur within their territory.[65] It then stated that such heightened interest extends to non-residents bringing related claims originating outside the state, thereby justifying New Hampshire in hearing all the libel claims.[66]

Furthermore, the Court treats targeted effects similarly to direct contacts through a test established in Calder v. Jones.[67] In Calder, two Floridian writers were sued in California for an intentionally libelous article they wrote in Florida.[68] The plaintiff in Calder was a Californian professional entertainer.[69] The writers’ physical contacts with California were limited to some phone calls, business trips, and occasional personal trips.[70] They wrote an article libeling the plaintiff that relied upon California sources and was then heavily circulated in California.[71] The Court reasoned that, as “California is the focal point both of the story and of the harm suffered,” the writers’ contacts were sufficient “based on the ‘effects’ of their Florida conduct in California.”[72] It further stated, “[a]n individual injured in California need not go to Florida to seek redress from persons who, though remaining in Florida, knowingly cause the injury in California.”[73] Thus, despite such wrongs not constituting physical presence or contact in the traditional sense of the word, such targeted effects were contacts sufficient to establish specific personal jurisdiction.

This effects test was the subject of litigation in many lower courts and of academic writing because it was unclear how targeted conduct must be, how wrongful it must be, or how unique the effects must be to a forum.[74] The Court provided some clarity, but not much, in Walden v. Fiore, where it deemed the Calder effects test unmet and that personal jurisdiction would be improper.[75] The plaintiffs in Walden were Nevada citizens.[76] The plaintiffs were about to leave Puerto Rico by plane with a substantial amount of cash won through gambling when TSA agents searched their persons, followed by defendant DEA agents arriving and questioning the plaintiffs.[77] The DEA agents learned of the plaintiffs’ citizenships, let them board the plane, but then filed a misleading report in Georgia that Atlanta DEA agents then used to confiscate the plaintiffs’ legitimate winnings once the plaintiffs reached Atlanta for their layover flight to Nevada.[78]

The plaintiffs contended that since they felt the brunt of the illegitimate seizure in Nevada, and since the defendant agents could have foreseen as much based on the plaintiffs’ citizenship, the effects test should have been met.[79] The Court rejected this argument.[80] It reasoned that since the DEA agents only interacted with citizens of Nevada but had no actual connection to Nevada itself, personal jurisdiction could not follow.[81] It went on to say that “however significant the plaintiff’s contacts with the forum may be, those contacts cannot be ‘decisive in determining whether the defendant’s due process rights are violated.’”[82] This distinguished the case from Calder where the writers gathered information in California and wrote an article that was then circulated in California.[83] Accordingly, the effects test seems to require express aiming at a forum by the defendant, not just an action in one forum that may later have impacts in a different forum.

Stream-of-Commerce Contacts

Another kind of contact that an entity can have with a forum is through the stream-of-commerce. Normally, these contacts occur when a product, or a piece of it, goes through multiple parties before ending up in the hands of an injured customer. In such cases, the courts developed case law to determine which of the multiple parties in the chain of control over the product that caused the injury may properly be sued in the forum in which the injury occurred.

World-Wide Volkswagen Corp. v. Woodson is one case where stream-of-commerce reasoning is discussed.[84] In that case, the Court had to determine whether the defendant automobile retailer and its wholesale distributor could be sued in a state where an accident occurred that was different from the place the vehicle was sold.[85] The Court held it could not.[86] The plaintiffs in Volkswagen purchased a vehicle from defendants in New York while they lived in the state.[87] Then, as the plaintiffs were driving through Oklahoma, another vehicle struck them, causing a fire that severely injured the plaintiffs.[88] The plaintiffs filed suit in Oklahoma, alleging that the fuel system used in the vehicle caused heightened injuries.[89] The defendant, however, had no contacts with Oklahoma.[90]

The Supreme Court of Oklahoma upheld jurisdiction, finding that Oklahoma’s long-arm statute granted jurisdiction in this case and reasoned that the mobile nature of automobiles and the fact that the defendant substantially profited from sales of automobiles necessarily put the defendant in a position that it should foresee litigation in Oklahoma.[91] The Court rejected that argument and reversed the Supreme Court of Oklahoma’s judgment.[92] It stated that even where a state and plaintiff have strong interests in adjudicating a case in a forum and the defendant would not be burdened by such locale, jurisdiction is improper where, as in the case before the Court, the product’s presence in the forum was based wholly on the unilateral and unincentivized activity of the nonresident plaintiffs.[93] The Court further stated that foreseeability of a product’s presence in a forum is a factor weighed towards whether a plaintiff has purposefully availed itself of a forum and should foresee litigation there; it is not enough on its own.[94]

The stream-of-commerce theory was further explained in J. McIntyre Machinery, Ltd. v. Nicastro, where the Court held that a manufacturer could not be sued in a state where it could foresee that its products would end up in the forum but took no action to take advantage of the forum.[95] The plaintiff in that case was injured in his home-state of New Jersey by a product manufactured in England by the defendant.[96] The defendant argued that it had not purposefully availed itself of New Jersey’s laws by targeting it as a state because it only sold its products to a general United States distributor, all of its United States physical contacts occurred in other states, and no more than four of its products ever ended up in New Jersey.[97] The Court accepted this argument, saying that contacts directed generally at the United States are insufficient to establish purposeful availment for an individual state.[98] Accordingly, it found that four products in New Jersey and a complete absence of other directed contacts was an insufficient basis for jurisdiction.[99] Stated simply, these cases essentially determined that specific jurisdiction exists under a stream-of-commerce theory when an entity develops a market in a given state.

Expected Relationships Contacts

The Court further acknowledged the importance of ongoing connections with a forum in Burger King Corp. v. Rudzewicz, where it held that failure to physically interact with a forum is no bar to purposeful availment where the defendant negotiated a contract contemplating an ongoing relationship with a forum’s residents.[100] The defendant in Burger King, was a Michigan franchisee being sued by Burger King in Florida for breach of their twenty-year franchisee contract.[101] Burger King was incorporated and headquartered in Florida at the time of negotiating the franchisee contract with the defendant.[102] However, all negotiations occurred in Michigan at one of Burger King’s locations.[103] The franchisee had no physical contacts with Florida other than a brief training in Miami near the beginning of the contract.[104] Over time, the franchisee fell behind on its required payments, but failed to halt business after Burger King exercised its right to revoke the franchisee’s operation privileges.[105] Burger King sued in Florida to enjoin the franchisee’s continual operation and for owed payments.[106]

The franchisee argued that it could not be haled into Florida courts for litigation because it had never negotiated in Florida and its breach did not happen in Florida.[107] Burger King responded by pointing to a clause in the contract which stated:

This Agreement shall become valid when executed and accepted by BKC at Miami, Florida; it shall be deemed made and entered into in the State of Florida and shall be governed and construed under and in accordance with the laws of the State of Florida. The choice of law designation does not require that all suits concerning this Agreement be filed in Florida.[108]

The Court found Burger King’s argument more persuasive.[109] It reasoned that “[a]lthough such a provision standing alone would be insufficient to confer jurisdiction, . . . when combined with the 20-year interdependent relationship [the defendant] established with Burger King’s Miami headquarters” the defendant had purposefully availed himself of Florida’s laws.[110] Thus, the Court held specific jurisdiction was proper.[111]

All three of these kinds of cases had some of their logic applied in Ford Motor Company v. Montana Eighth Judicial District Court, where the Court held that the state could exercise personal jurisdiction over the defendant, even though the plaintiffs purchased the vehicles elsewhere and then drove them to the state.[112] In that case, the two suits at issue each involved a Ford vehicle that was the subject of litigation in one state where the plaintiffs lived and the crash occurred, but each vehicle had been sold by Ford in an entirely different state.[113] The vehicles only reached the forum state by a combination of resale and individual driving.[114] However, Ford had other contacts with the state: it advertised heavily in the state, had repair shops and services, and had sold those types of vehicles in the state.[115]

Ford argued that the courts could not properly exercise jurisdiction because, like in Volkswagen, it was the unilateral action of another that put the vehicles in those states.[116] The Court rejected that argument, stating that Volkswagen was decided not solely on unilateral action, but also on the fact that the defendant in Volkswagen had not developed a market in that state for those vehicles.[117] Here, Ford developed a market for its vehicles in the state by advertising and “work[ing] hard to foster ongoing connections to its cars’ owners” through repair shops and servicing.[118] Thus, the Court held “[w]hen a company like Ford serves a market for a product in a State and that product causes injury in the State to one of its residents, the State’s courts may entertain the resulting suit.”[119] This reasoning seemingly combines direct contacts, stream-of-commerce, and relationship expectation considerations in one case to come to the conclusion that the defendant could be properly subjected to personal jurisdiction in the state.

Over-the-Air Updates (OTAUs) Explained

With the legal framework now provided, OTAUs can be explained. An OTAU, for the purposes of this paper, is the wireless delivery of data to change how an endpoint on a network functions.[120] An endpoint of a network refers to the final recipient of data on a network.[121] Examples would be a cellphone receiving a phone call or a vehicle receiving an OTAU. OTAUs are a legally relevant classification of contacts requiring special consideration because they are intangible contacts that have unique and substantial real-world impacts on a product’s functionality. As this paper intends to show that such updates can establish personal jurisdiction, it will focus on the subset of OTAUs most likely to confer personal jurisdiction under current precedent—automobile updates. However, while modern vehicles, especially those squarely in the self-driving or assisted driving category, are an example of potentially jurisdictionally relevant OTAU usage, such legal relevance may analogize to Internet of Things (IoT) medical devices,[122] Software as a Service (SaaS) relationships,[123] and many other highly integrated IoT devices like Smart Home devices. [124]

The automotive and mobile phone industries pioneered OTAUs over the last few decades.[125] Since then OTAUs have proliferated almost all IoT and cellular devices including smartphones, tablets, computers, automobiles, and miscellaneous household devices like Smart TVs.[126] OTAUs can theoretically be deployed through any over-the-air data transfer technology with sufficient range and speed for a given task.[127] The most common modes of deployment are through cellular and Wi-Fi networks.[128] Cellular networks rely upon cell towers sending and receiving signals as intermediary nodes in a network between senders and receivers.[129] Wi-Fi networks function by connecting at home IoT devices to an internet service provider’s routers, physical cable network, or other hardware necessary to connect the sender and receiver.[130]

OTAU network diagrams can range from simple to extraordinarily complex depending on the implementation. The simplest network only has two points: a control system that sends the data and an endpoint that receives and implements it. Such a simple network is almost never used because usually there are many routers or cell towers necessary in-between to get the data from sender to receiver. Further complicating the network, OTAU systems can use a centralized or decentralized model.[131] In a centralized networking model, each end point receives its information from a single central sender.[132] However, a decentralized model uses multiple nodes acting as senders to assigned subsets of receivers.[133]

Such decentralized OTAU networks frequently utilize “the cloud” or “cloud computing,” particularly in the automotive industry since networks include millions of different vehicle endpoints.[134] The cloud is a phrase that developed through tech industry lingo that refers to a method of decentralized computing and data storage that is more powerful and versatile than previous iterations of data networks.[135] Previously, a network consisted of endpoints that could run programs to complete complex tasks with data, and the in-between components, like routers and servers, merely passed data according to communication protocols.[136] A cloud networking model diffuses computing tasks to the in-between points as well through a process called virtualization that allows each point to run multiple different tasks as if it were different computers running many programs.[137] This reduces the processing power needed at the endpoints of the network, improving efficiency and preventing bottlenecking, a term describing when networks experience what could best be analogized as a traffic jam.[138]

OTAUs are continually being improved and pushed into more use-cases. The most complex use-case to date is automobile updates. Each modern vehicle includes anywhere from 80–150 Electronic Control Units (ECUs),[139] which are basically small computers, and roughly “100 million lines of software code.” [140] The amount of code is expected to rise to 300 million by 2030.[141] Comparatively, passenger airplanes only use about 15 million lines of code.[142] Accordingly, such updates are extremely complex, difficult, and if done improperly, dangerous. And yet, the economic incentives to use OTAUs are so strong that they will only be utilized more heavily.

Tesla used the first OTAU for automobiles in 2012 with the Tesla Model S.[143] Since then, almost every recognizable name in automobile manufacturing has implemented OTAUs in some way—ranging from updating the infotainment systems, which are the little screens in most modern cars that control the radio, climate, GPS, etc.,[144] to updating core safety and driving features in vehicles.[145]

Furthermore, there are many parts to an automobile OTAU. A single network may include or be responsive to the following entities: “Car, Cloud Server, Mobile Phone, [Original Equipment Manufacturer] (OEM), Spare part OEM, Software Distributor (SD), Car Owner, Service Center, Cellular Operator, Insurance Company [,] and Law and Enforcement Personnel.”[146] These entities are not always entirely separate legal parties though. For example: a single OEM may also provide the spare parts and the software for the component.[147] Accordingly, automobile OTAU networks can be quite complex, but they all accomplish the same task—changing the functionality of a vehicle.

Personal Jurisdiction Law Applied to Over-the-Air Updates

With the general technological discussion out of the way, OTAUs can be analyzed under current precedent. As noted above, there are the traditional methods of establishing personal jurisdiction and contacts-based general and specific personal jurisdiction. It seems unlikely that OTAUs will have a significant impact on the traditional methods or do enough to confer general personal jurisdiction through contacts, so that analysis will be quickly provided up front. However, it is very likely that OTAU contacts can meet specific personal jurisdiction purposeful availment requirements. This paper will prove that thesis with concrete facts, using Tesla’s operations in South Carolina as a case study.

OTAUs’ Minimal Impacts on Traditional and General Personal Jurisdiction

OTAUs do not have any legal effect on citizenship, consent, waiver, or service of process. Those concepts exist wholly separate from sending updates. In light of Mallory, there may be an argument that sending updates in a state should constitute foreign business operations, thus requiring registration, and thereby requiring consent under certain statutory schemes.[148] But that argument is not unique to OTAUs, it is personal jurisdiction derived from statutory interpretation, which is not the focus of this paper.

OTAUs may have minimal relevance to general personal jurisdiction contacts analysis because the contacts caused by OTAUs can potentially consolidate actions, thereby making a company appear more “at home” in a forum. As discussed above, OTAUs reduce the number of physical recalls or in-person repairs necessary for vehicles. Instead, a company can fix such issues remotely through an OTAU. Thus, all the physical presence a company would have had in a forum before OTAUs, would shift to an intangible contact stemming from a different forum. In the narrow circumstance where a company uses a centralized network and controls almost all the steps of OTAUs from a single forum, that one central forum would be the home-base for all those contacts in a way that appears systematic, continuous, and unique as required by the Daimler precedent.[149]

However, even where a company uses a centralized network model, if that central server is in a different area than a significant and unique separate part of the company’s activities, it is very unlikely that the company would be considered at home in that forum because those contacts would be like the insufficient, significant contacts of the defendant in BNSF.[150] Such update contacts would be similar because in BNSF even 2000 miles of railroad and thousands of employees were insufficient since such activity constituted only a small portion of the railroad’s business.[151] Thus, even if such contacts bring a forum closer to a company’s “home,” this would only be relevant in a small sliver of cases where the server is also in a state where the company was almost already at home anyway.

Additionally, with the more common decentralized networks, the origin of an update can be seriously debated. Is the origin the place where leadership gave the go-ahead to send the update? The place(s) from which the code was first uploaded? Or maybe whichever node first received the applicable code from software engineers? Or perhaps whichever node the endpoint contacted for the download? This is like the kind of diffused management the Court indicated would complicate nerve center jurisdiction analysis in Hertz Corp. v. Friend dicta.[152] Without more precedent to clarify where the origin contact would be, it is unlikely that a court would use such a model to find a business “at home” in a forum. Accordingly, OTAUs likely have minimal impact on the at home analysis as well.

OTAUs Can Constitute Purposeful Availment—Tesla in South Carolina as a Case Study

On the other hand, OTAU contacts can constitute purposeful availment. This section presents Tesla as an example of a business that may be liable for injury in a state that likely bears no jurisdiction over it for its non-OTAU contacts but may be subject to specific personal jurisdiction based on its OTAUs. Furthermore, Tesla is a good case study because its practices are becoming increasingly relevant to South Carolinians as more and more of Tesla’s vehicles and technology are on the roads.[153] This subsection proceeds as follows: (1) establishes the likelihood of litigation against Tesla in South Carolina, (2) explains why a South Carolina Court would have to analyze specific jurisdiction based on Tesla’s OTAU usage, (3) explains Tesla’s OTAU usage, and (4) shows why current Supreme Court precedent would classify OTAU usage as purposeful availment.

Likelihood of Litigation Against Tesla in South Carolina

As of September 2022, there are approximately 6,400 registered Tesla vehicles in South Carolina.[154] Every single one of those vehicles is built to receive OTAUs that regularly “add new features and enhance existing ones.”[155] Those new features enter South Carolina roads within hours, or even minutes, of download, leaving little room to catch errors between update and road use.[156] Furthermore, it is no secret that driving is an inherently risky endeavor, especially in South Carolina: South Carolina leads the nation in deaths per mile driven.[157] This statistic reflects not only a tragic waste of human life, but also a serious blow to the financial interests of everyone involved with a crash, even where involvement is merely tangential.[158] In addition, South Carolina has many undermaintained roads,[159] poor signage visibility,[160] and sky-high rates of intoxicated drivers.[161] Each of these factors, among others, make South Carolina a particularly difficult place to deploy advanced vehicle guidance software–especially if the software purports to be “self-driving.”[162] And yet, Tesla allows its advanced “self-driving” software on South Carolina roads, seemingly with no defined geographical deployment zones.[163] Various academic writers have suggested that automaker’s increased technological connectivity to vehicles on the roads inevitably corresponds to increased liability exposure.[164] Furthermore, these vehicles, especially in such conditions, will almost invariably cause a fatal or destructive crash while in the state, making it a question of when a crash will occur, not if.[165] Accordingly, should a crash occur with one of these vehicles, Tesla will almost certainly need to prepare its legal team.

In fact, such a crash may have already occurred. On September 18, 2022, a Tesla crash near Lake Murray cost two people their lives when the vehicle “left the road” and smashed into a tree, causing a fiery scene in which both the driver and front passenger were killed.[166] South Carolina Highway Patrol began an investigation, but no explicit indication of cause was reported in the news coverage of the accident.[167] Again, on July 28, 2023, in Phoenix, South Carolina a Tesla inexplicably plunged into a private home’s pool after crashing through a substantial brick privacy fence.[168] While there were no injuries reported, the vehicle, fence, and pool were irreparably damaged.[169] The cause of the crash was once again unclear; all that could be said was that the vehicle appeared to be going faster than it should have been.[170] Even more recently, on October 12, 2023 in Sumter County, South Carolina, a man died in a fiery Tesla single-vehicle crash after being ejected from the flipping vehicle.[171] Again, the cause was unclear.[172] Such causal unclarity makes clear that litigation asserting Tesla should bear part of the liability for the crashes is possible.

Furthermore, even if Tesla had been sued, Tesla’s practice of including forced arbitration provisions in each of its buyer contracts obscures the visibility of litigation against them.[173] In fact, seven senators recently urged Tesla to end its use of forced arbitration stating, among other things, “we . . . have no visibility into what complaints may have already been made and what other potential safety issues with Tesla vehicles may exist.”[174] Thus, it is clear that Tesla already has been, or at least will be in the near future, the subject of South Carolinian litigation. What remains unclear is whether South Carolina courts can obtain personal jurisdiction over Tesla in such suits based on Tesla’s uniquely situated business and the factual scenario presented.

Why a South Carolina Court Would Have to Analyze Specific Jurisdiction Based on Tesla’s OTAU Usage

The relevance of OTAUs in personal jurisdiction law is that they may establish personal jurisdiction in cases where other ways to establish personal jurisdiction do not apply. To prove that relevance in a real-world example, this subsection shows how traditional and general personal jurisdiction likely do not apply to Tesla in South Carolina. Furthermore, it shows how South Carolina’s long-arm statute, when interpreted in accordance with the Due Process Clause and applied to Tesla’s non-OTAU contacts, would likely not confer personal jurisdiction for a substantial swathe of likely litigation. Accordingly, OTAUs will be particularly relevant to personal jurisdiction analysis over Tesla in South Carolina.

Inapplicability of Traditional and General Jurisdiction to Tesla in South Carolina

As discussed above, a state traditionally has jurisdiction over parties that are its citizens. Furthermore, waiver, some kinds of service of process, and consent conclusively satisfy a state’s long-arm and a defendant’s constitutional due process requirements, thereby subjecting an entity to state court personal jurisdiction on those issues. Finally, general jurisdiction follows from contacts that make a company “at home” in a state. In Tesla’s case, it is likely that none of these apply, and a court would be required to analyze Tesla’s contacts with South Carolina under specific personal jurisdiction precedent.

Tesla is not a citizen of South Carolina because Tesla Motors, Inc. is incorporated in Texas,[175] and its headquarters, which is most likely its nerve center, is also in Texas.[176] Also, it seems likely that Tesla would not waive a potential personal jurisdiction defense that may increase its bargaining power for settling a case, so waiver likely does not apply. Furthermore, the situations where service of process may establish personal jurisdiction are heavily dependent on the specific facts of a case, so such possibilities will not be addressed in depth here.

Finally, consent is likely inapplicable here because there is little indication that Tesla has consented to litigate suits regarding vehicle liability in South Carolina. A potential argument that Tesla has consented to such suits would rely on the recent decision in Mallory regarding the impact of business registration statutes. South Carolina’s business registration statute, S.C. Code Ann. § 33-15-101 et seq., requires every “foreign” corporation, meaning any non-South Carolina corporation, to register with the South Carolina Secretary of State before doing business in the state.[177] An ostensible plaintiff could argue that, due to that registration, Tesla necessarily consented to general personal jurisdiction, or at least jurisdiction in relation to its business in the state.

However, S.C. Code Ann. § 33-15-101 is distinguishable from the statute in Mallory, 42 Pa. Cons. Stat. § 5301(a)(2)(i), (b), because registration in South Carolina only explicitly requires the corporation to consent to personal jurisdiction for adjudication of tax liability—it does not say that such entities consent to general personal jurisdiction in the state.[178] Furthermore, it would seem only a few parts of the Mallory decision became precedent due to splits, and many of the justices wrote separately about the potential invalidity of such jurisdictional grants as a violation of other constitutional provisions.[179] Thus, a South Carolina court would not likely apply the Mallory precedent to its business registration statute where it has no such explicit consent provision. Thus, while it is possible that in a specific case, consent, waiver, or service might establish personal jurisdiction over Tesla, this paper addresses the more likely scenario in which none of those apply.

Finally, it is clear based on Tesla’s non-South Carolina contacts that it is not “at home” in South Carolina under Daimler and BNSF because it sells a substantially larger portion of vehicles in California and many other non-citizen states than it does in South Carolina.[180] Thus, any South Carolina court would need to justify its jurisdiction through specific personal jurisdiction contacts analysis.

The Reach of South Carolina’s Long Arm

South Carolina’s enumeration long arm statute says that South Carolina courts can exercise personal jurisdiction over an entity so long as jurisdiction arises from the entity’s following actions:

(1) transacting any business in this State; (2) contracting to supply services or things in the State; (3) commission of a tortious act in whole or in part in this State; (4) causing tortious injury or death in this State by an act or omission outside this State if he regularly does or solicits business, or engages in any other persistent course of conduct, or derives substantial revenue from goods used or consumed or services rendered in this State; (5) having an interest in, using, or possessing real property in this State; (6) contracting to insure any person, property, or risk located within this State at the time of contracting; (7) entry into a contract to be performed in whole or in part by either party in this State; or (8) production, manufacture, or distribution of goods with the reasonable expectation that those goods are to be used or consumed in this State and are so used or consumed.[181]

But, over time, the South Carolina Supreme Court, through standard principles of statutory interpretation, shifted away from analyzing the factors separately and transmuted this long arm from an enumeration long arm into the newer approach by holding that these eight circumstances simply mean South Carolina courts can exercise jurisdiction in any case that due process permits.[182] Thus, the only question here is whether due process would allow South Carolina courts to exercise general or specific jurisdiction based on such OTAU contacts. Due to the principle of constitutional avoidance, this analysis usually takes into account both state and federal constitutional considerations.[183] The discussion below assumes state constitutionality and addresses rights afforded by the United States Constitution only. Thus, as discussed above, the most determinative question is whether a party purposefully availed itself of a forum.

Tesla’s Non-OTAU Contacts Likely Do Not Constitute Purposeful Availment

Despite the growing number of Tesla vehicles in South Carolina, Tesla, Inc. has very limited contacts with South Carolina,[184] making OTAUs its most significant contact with the state. Firstly, Tesla has no physical dealerships in South Carolina.[185] This is due, at least in part, to S.C. Code Ann. § 56-15-45(D), which protects South Carolina car dealerships by precluding vehicle manufacturers from running their own dealerships in the state.[186] There is little indication that this statute will be changed any time soon, as a bill to amend that section of the code died in committee just last year.[187] So, it is unlikely that Tesla will have any dealerships in South Carolina for the foreseeable future. Furthermore, Tesla just recently announced that it will open a distribution facility in Greenville, South Carolina in mid-2024 that will be its “inaugural” facility in the state.[188] The facility will only redistribute parts, and will not be a base for vehicle sales or manufacturing.[189]

Accordingly, Tesla relies upon internet sales or customer travel to its Charlotte, North Carolina, or various Georgia dealerships for South Carolinians to obtain a Tesla vehicle. Even such internet sales require vehicle pickup from their out-of-state locations when customers do not want to pay for home delivery of a purchased vehicle.[190] Furthermore, Tesla maintains no repair facilities in the state.[191] In fact, it appears that the only physical assets Tesla maintains in the state are its charging stations, and even those are sparse, with only a few dozen locations in the entire state.[192] Those stations are also more heavily concentrated in developed areas.[193]

Additionally, Tesla relies heavily on word-of-mouth to promote its brand.[194] It only recently announced that it intends to begin advertising its vehicles.[195] It is not clear on what platforms and to what extent it will do so.[196] It seems unlikely that Tesla would advertise in a significant way in South Carolina as it is not its main market.[197]

Furthermore, while Tesla does offer home-address vehicle servicing and repairs,[198] Tesla states that its vehicles “require [no] annual maintenance,” so such at-home service is only upon request.[199] This is due in part to OTAUs, but also because Teslas are exclusively electric vehicles.[200] The Tesla service page states, “[u]nlike gasoline cars, Tesla vehicles require no traditional oil changes, fuel filters, spark plug replacements or emission checks. Even brake pad replacements are rare because regenerative braking returns energy to the battery, significantly reducing wear on the brakes.”[201] It goes on to recommend a very small list of regular maintenance tasks, most of which only need to be completed once every few years.[202] Thus, home services are likely few and far in between and only cover a small percentage of potential vehicle malfunctions.

Accordingly, Tesla’s non-OTAU contacts with South Carolina are minimal and likely do not constitute purposeful availment. Even if a court disagreed and held that such acts do constitute purposeful availment, it is likely that only a small subset of litigation would arise out of or relate to Tesla’s non-OTAU contacts. Therefore, South Carolina courts would likely need to analyze Tesla’s OTAU contacts to obtain specific personal jurisdiction relating to a product-liability action against Tesla.

Tesla’s OTAUs Explained

Tesla’s only apparent remaining contacts are with its roughly 6,400 current vehicles[203] through OTAUs. Tesla maintains and expands almost all of its vehicles’ software through OTAUs.[204] According to Tesla CEO Elon Musk, each Model 3 vehicle body is designed to have a “million mile life,” and the battery packs should last between 300–500 thousand miles.[205] That means with a single battery replacement, a Tesla vehicle could last 44–74 years based on Department of Transportation average vehicle driver statistics.[206] However, it is likely more appropriate to view that timeline as an electric vehicle longevity goal, as that timeline seems farfetched. After all, Tesla only puts an eight-year warranty on vehicles currently, whereas Kia and Hyundai offer ten-year warranties in some circumstances.[207] While electric vehicle longevity is difficult to predict given electric vehicle newness, it is probably reasonable to credit them with a twenty-year lifespan with a single battery replacement.[208]

Tesla also uses a decentralized cloud-based computing update network, and Tesla has equipped all of its vehicles with the capability to connect to cellular and Wi-Fi networks.[209] Furthermore, Tesla is widely recognized as the leader in OTAU usage among automobile manufacturers, with “[n]early every vehicle component and system” upgradable by OTAUs.[210] It also pushes promotions about additional purchasable vehicle software upgrades, like activating heated seats, to its vehicle owners using the Tesla App.[211] That kind of transaction would not be possible without OTAUs.

However, not all systems within a Tesla vehicle employ OTAUs in the same way. Functions that are central to the vehicle or are already unlocked by the vehicle owner are subject to automatic prompts to update.[212] To access updates, Tesla vehicles regularly check various Tesla cloud servers for software updates and receive other diagnostic information.[213] This can include everything from infotainment systems to automatic braking systems and assisted steering.[214] But whether each component is subject to automatic update prompts or has upgrades stuck behind a paywall is up to Tesla.[215]

Additionally, Tesla generally equips its vehicles with all the hardware necessary for the implementation of monetizable features, but not necessarily all the software.[216] This requires the vehicle to be engineered from the beginning with continual interactions with the vehicle in mind. Tesla’s pay to activate policies pervade even the most sophisticated operations of the vehicles because advanced software in certain models is subject to activation and deactivation based on a vehicle owner’s continued payments.[217] Tesla’s three marketed levels of assisted driving software, “Autopilot,” “Enhanced Autopilot,” and “Full Self-Driving” (FSD),[218] each can be deployed through a subscription plan or made inherent to a purchased vehicle.[219] A Model 3 vehicle could one day be a basic Model 3 equipped only with Autopilot, the next day be the Enhanced version boasting greater road performance, and the next day be purportedly FSD.[220] Even worse, a payment plan may lapse, and a previously FSD vehicle may go back to Autopilot and a driver be unaware of the change.

Since Tesla monetizes the software, that necessarily requires each vehicle be associated with a particular account and owner; thereby requiring a connection with verifiable information between sender and receiver. This means Tesla must have enough Personal Identifiable Information (PII), like “VIN, region, [and] model,” for each user vehicle to ensure effective rollout of updates.[221] Tesla admits such PII includes the region of the vehicle.[222] Additionally, Tesla receives data back from each vehicle’s driving information to train its vehicle AI,[223] and, regardless of whether a Tesla vehicle is using cellular or Wi-Fi deployment, such networks can be used to identify the geographical location of a vehicle endpoint.[224] That means Tesla knows the physical location of the vehicles it updates.[225]

Furthermore, the power of such OTAUs is uncontestable; after all, changing from a basic model to an FSD vehicle which can purportedly “drive itself almost anywhere with minimal driver intervention” will certainly impact vehicle functionality, safety, and consumer expectations.[226] Yet these capability changes can be sent from an entirely separate forum. So, this vehicle is morphing its capabilities while potentially just sitting still in a garage somewhere—and Tesla is the one controlling such capabilities.

The augmentation power of these updates is often used to Tesla’s legal and economic benefit as well because Tesla secures compliance with various administrative safety standards through its OTAUs. In December of 2023 alone, Tesla had two massive “recalls” mandated by the National Highway Traffic Safety Administration (NHTSA).[227] The first was Tesla’s largest recall, requiring almost all Tesla vehicles on the road in the United States—nearly 2 million vehicles—to receive an update to the Autopilot feature to better engage drivers.[228] The second, required Tesla to send an update out to roughly 120,000 vehicles, to prevent doors from opening in crashes.[229] Similarly, in a January 2023 NHTSA safety recall report, every single Tesla FSD vehicle on the road was deemed a safety risk because each one was pending installation of, or was already using, a Tesla FSD software package that was not up to safety standards.[230]

This happens on the international scene as well. In May 2023, China required Tesla to recall approximately 1.1 million vehicles, nearly every vehicle it sold in the country, to address an issue with faulty braking systems.[231] Before the days of OTAUs, Tesla would have been required to physically access each vehicle included in these recalls. But Tesla did not have to do so, instead it merely pushed an update out that brought the vehicles into compliance,[232] saving a veritable truckload of cash.[233]

On the other hand, Tesla’s OTAUs do have some limits. In a July 2023 report, NHTSA identified approximately one thousand Tesla vehicles out of safety specifications due to front-facing camera misalignment, a problem that can cause the vehicle to perceive the world around it incorrectly.[234] This recall is noteworthy because it was a traditional physical recall,[235] thereby highlighting the current limits of OTAUs. Where a physical component is defective that is potentially crucial to diagnosing issues or simply lacks the physical infrastructure necessary to be manipulated remotely, a physical recall is still necessary. This may explain Tesla’s resistance to a recent Reuters report chiding Tesla’s physical suspension systems.[236] Such a recall would almost certainly require physical intervention. And yet, the Reuters investigation drew the attention of Congress members, and Tesla may have to recall the vehicles anyway.[237]

However, the circumstances where Tesla’s OTAUs cannot solve vehicle issues do not change the fact that OTAUs can augment many integral vehicle components. Accordingly, Tesla has developed a system of vehicle management that gives Tesla far more connectivity and control over each vehicle than has been seen in the past. That system should also provide courts specific personal jurisdiction over Tesla under current legal precedent.

Tesla’s OTAUs Constitute Purposeful Availment

Supreme Court precedent across each category of contact supports a finding that Tesla’s OTAU usage should constitute purposeful availment of South Carolina as a forum because the overlapping similarities between OTAU usage and types of contacts the Court determined constituted purposeful availment far outweigh any potential distinctions. The similarities between OTAUs and each kind of contact will be discussed in turn.

While physical contact with or presence in a forum is not required for personal jurisdiction, it is worth discussing to what extent OTAUs will be considered physical contacts under the law. As discussed, OTAU data comes in the form of either cellular or Wi-Fi radio waves to a particular endpoint in a forum. Radio waves are a particular frequency of wave that occurs on the same spectrum as visible light.[238] Some courts may already recognize OTAUs as physical contacts with a forum because under the “modern trend” of trespass law, courts have adopted tort law accepting light as a basis for trespass where light damages property.[239] This is similarly true for battery, as sending light out to cause epileptic seizures has been sufficient contact for battery.[240]

Another route one could take to argue that OTAUs are physical contacts is based on the processing power required to receive such updates. In Compuserve Inc. v. Cyber Promotions, a district court upheld a trespass to chattels claim based on the defendant sending spam emails through plaintiff’s servers because the electronic signals were being processed by the servers and diminishing each server’s processing capacity.[241] Similarly, one could argue that, since an OTAU must be processed by an endpoint and implemented, each OTAU is necessarily a physical contact with that endpoint. Accordingly, some courts may view OTAU contacts as actions not just directed at a forum or in relation to it, but actually in the forum. Such actions, like in Keeton, are almost always considered purposeful availment.

Furthermore, even where a court is unwilling to see OTAUs as physical presence, the Calder effects test likely indicates Tesla’s OTAU usage constitutes purposeful availment. As noted, Tesla’s updates are frequently used to bring software into compliance with safety regulations and Tesla knows the location of the users that receive the updates. In a case where Tesla knowingly or negligently sent out an unsafe update to users, the targets would each be in forums in which users are to receive updates and the effects would be uniquely felt in those forums through the real-world impact of an unsafe self-driving vehicle. This argument is even stronger where Tesla sends an update to a particular user who purchased a vehicle upgrade because, rather than potentially interacting with multiple targets and forums at a time and obfuscating the targeting analysis, it would be a specific target in a single forum. This distinguishes Tesla’s OTAU use from the contacts contemplated in Walden, because in Walden the actions of the DEA agents did not rely on any Nevada contacts, whereas Tesla would be relying on update infrastructure and contacting a vehicle that is already in the forum to accomplish its goals. Accordingly, in Tesla’s case it may be unnecessary to go any further into case law to support an argument that its OTAUs constitute purposeful availment.

Even so, Tesla’s OTAUs are significant under stream-of-commerce contacts considerations because it uses its OTAUs to maintain its vehicles in any reachable forum. Stream-of-commerce cases state that where a manufacturer or distributor can foresee its product arriving in a forum, and it takes steps to develop that market, it has purposefully availed itself of the forum. As Tesla uses its OTAUs to maintain vehicles and prevent the necessity of manual recalls, one of the largest benefits of OTAUs is that such capabilities improve the marketability of such vehicles in any place where cellular or Wi-Fi capabilities exist. Those capabilities are legally significant because they are much like the capabilities that established jurisdiction over the defendant in Ford Motor Co.

Recall that in Ford Motor Co. one of the Court’s deciding factors was that the defendant had repair and service shops in the state. In Tesla’s case, since its vehicles are almost solely dependent on OTAUs, such updates basically replace the need for such shops and serve the same purpose. In both cases the infrastructure ensures the party controls vehicle repairs, parts, and functioning, trades on the company’s reputation to incentivize vehicle presence in the forum, and provides measurable economic benefit to the infrastructure owner. Thus, it would be counter-intuitive to find that the defendant’s infrastructure in Ford Motor Co. constituted purposeful availment of a forum but Tesla’s implementation of a system with similar effects in the forum does not.

Tesla would likely point to World-Wide Volkswagen Corp. and Nicastro to argue that all South Carolina vehicles were necessarily sold in other states, and it is therefore unforeseeable that the vehicles would be in South Carolina. However, foreseeability is a non-issue in Tesla’s OTAU case because the company has live information about where the vehicles are to update them and, unlike the four products that reached the forum in Nicastro, there are roughly 6,400 Tesla vehicles in South Carolina. Accordingly, Tesla may argue that it could not foresee the vehicles being in South Carolina at the time of sale, which still seems unlikely since purchasers disclose residency upon purchase, but even so, such an argument is irrelevant since Tesla purposefully contacts the vehicles through OTAUs after the vehicle has entered the forum. This is what distinguishes Ford Motor Co. and Tesla’s OTAU usage from previous stream-of-commerce cases. In other stream-of-commerce cases, there were minimal, if any, post-sale contacts contemplated in relation to the product. But Ford Motor Co. stands for the proposition that such planned post-sale contacts and infrastructure establish foreseeability and can constitute purposeful availment. Accordingly, such precedent also supports the proposition that OTAUs can constitute purposeful availment.

Finally, Tesla’s OTAUs land squarely within the reasoning used to uphold personal jurisdiction in Burger King Corp. and other reasoning in Ford Motor Co. because Tesla’s OTAUs prove that a long-term relationship was contemplated with the residents of the forum when they purchased the product. The fact that Tesla’s OTAUs are meant to maintain vehicles throughout the vehicle’s entire lifespan and that such a lifespan is approximately twenty years, establishes a long-term relationship exists between Tesla and its vehicles through OTAUs. This is much like the 20-year relationship that was a substantial basis for conferring jurisdiction in Burger King Corp. The argument becomes even stronger as vehicle longevity increases. Such a relationship strongly indicates that contacts between Tesla and its vehicles in various forums are not “random, isolated, or fortuitous” contacts, but rather part of a string of expected activity with the capacity to affect many lives. Furthermore, since Tesla vehicles purportedly last anywhere from 44–74 years for the average driver, or there is at least a goal to make them last that long, the relevance of this factor will likely only increase.

Accordingly, Supreme Court precedent, regardless of the type of contact in question, supports the idea that OTAUs can constitute purposeful availment of a forum. Thus, when such considerations are combined like the Court did in Ford Motor Co., Tesla’s OTAUs almost necessarily constitute purposeful availment of South Carolina’s market. Furthermore, many significant forms of litigation could arise out of or relate to Tesla’s OTAU purposeful availment, and there are no apparent reasons why subjecting it to such litigation would offend principles of fairness. Thus, Tesla’s OTAUs are likely a constitutional basis to subject Tesla to the power of South Carolina courts, allowing South Carolinians to obtain in-state adjudication of their rights.

Conclusion

Over-the-air updates (OTAUs) are a powerful technological tool for businesses that benefit both the seller and buyer of products. Tesla uses that tool in a cutting-edge way to enhance its products, maintain customer relationships, and increase the reach of its business. It does this by building its vehicles from the ground-up with OTAU technology in mind and consistently improving its implemented technologies in response to new developments in safety. While such use will likely have minimal effects on traditional personal jurisdiction law or the general personal jurisdiction “at home” test, under current facts, it will likely be the main basis for any South Carolina court to properly exercise specific personal jurisdiction over Tesla. The number of similarly legally significant OTAU uses will likely only increase, not just in the automotive industry, but also in fields like medical implants, Smart Home devices, or other IoT devices. Accordingly, OTAUs depart from the trend of technology complicating personal jurisdiction because they are a kind of technological intangible contact that can be so impactful on a forum that they make personal jurisdiction purposeful availment analysis easier. Thus, while the Court is not an expert on the internet, its precedent still indicates that OTAUs deserve special attention when discussing the forums in which a defendant may properly be sued.

  1. * J.D. Candidate, May 2025, University of South Carolina Joseph F. Rice School of Law. I would like to thank Professor Bryant Walker Smith for serving as my advisor for this paper. Also, a special thanks to Professor Scott Bauries and Professor Amy Leventis for their continual assistance in understanding the doctrine of personal jurisdiction and assistance with academic writing, respectively. Finally, thank you to the entirety of South Carolina Law Review for their hard work and feedback; I am forever grateful for the opportunity to work alongside such outstanding individuals.
  2. ** Oma Seddiq, Supreme Court Justices Aren’t ‘the 9 Greatest Experts on the Internet,’ Elena Kagan Said as They Heard a Major Tech Case, Bus. Insider: Pol. (Feb. 21, 2023, 5:29 PM EST), https://www.businessinsider.com/supreme-court-google-tech-social-media-section-230-justices-internet-2023-2 [https://perma.cc/BN29-4K5P]. 
  3. . See Amdt14.S1.7.1.1 Overview of Personal Jurisdiction and Due Process, Const. Annotated, https://constitution.congress.gov/browse/essay/amdt14-S1-7-1-1/ALDE_000009
    07/#essay-14 [https://perma.cc/MCZ5-73Y2].
  4. . In Personam, Cornell L. Sch.: Legal Info. Inst., https://www.law.cornell.edu/
    wex/in_personam [https://perma.cc/G2Q7-TEB8]; In Rem, Cornell L. Sch.: Legal Info. Inst., https://www.law.cornell.edu/wex/in_rem [https://perma.cc/2HB4-8QPG].
  5. . Int’l Shoe Co. v. Washington, 326 U.S. 310, 316 (1945).
  6. . See Mallory v. Norfolk S. Ry. Co., 600 U.S. 122, 144 (2023). 
  7. . See 4 Charles Alan Wright & Arthur R. Miller, Federal Practice and Procedure § 1068 (4th ed. 2023).
  8. . See Fed. R. Civ. P. 4(k)(1)(A) (establishing federal court personal jurisdiction over any entity that is “subject to the jurisdiction of a court of general jurisdiction in the state where the district court is located”); see also Fed. R. Civ. P. 4(k)(1)(B)–(C) (providing for additional circumstances where a federal court may obtain personal jurisdiction).
  9. . See Mallory, 600 U.S. at 143–46 (debating whether Pennsylvania long-arm statute, combined with registration statute, unconstitutionally permitted long-arm jurisdiction).
  10. . Vedder, Price, Kaufman & Kamholz, P.C., Long-Arm Statutes: A Fifty-State Survey i (2003).
  11. . See Wright & Miller, supra note 5.
  12. . See id.
  13. . See id.
  14. . See id.
  15. . See generally id., § 1064 (discussing traditional bases of personal jurisdiction).
  16. . See Ashleigh E. Edward, When a Corporation Is “At Home”: Personal Jurisdiction over Out-of-State Defendants, Cosgrave Vergeer Kester LLP, https://www.cosgravelaw
    .com/wp-content/uploads/2015/03/When-a-Corporation-Is-At
    -Home.pdf [https://perma.cc/P8B
    H-5MG6].
  17. . See Goodyear Dunlop Tires Operations, S. A. v. Brown, 564 U.S. 915, 924 (2011) (“For an individual, the paradigm forum for the exercise of general jurisdiction is the individual’s domicile”). 
  18. . Hertz Corp. v. Friend, 559 U.S. 77, 80 (2010) (quoting 28 U.S.C. § 1332(c)(1)).
  19. . Id. at 81. The Hertz Court left open the possibility that telecommuting or other internet uses may disrupt the efficacy of the “nerve center” test. Id. at 95–96.
  20. . See Burnham v. Superior Ct. of Cal., 495 U.S. 604, 627–28 (1990); Cody J. Jacobs, If Corporations Are People, Why Can’t They Play Tag?, 46 N.M. L. Rev. 1, 1 (2016).
  21. . See Fed. R. Civ. P. 12(h) (providing that failure to raise personal jurisdiction argument in preliminary motions or in any pleading constitutes waiver of such argument). But see Collateral Attack, Cornell L. Sch.: Legal Info. Inst., https://www.law.cornell.edu
    /wex/collateral_attack [https://perma.cc/TK5D-QCNW] (explaining exception to the aforementioned rule regarding waiver).
  22. . See generally Scott Dodson, Plaintiff Personal Jurisdiction and Venue Transfer, 117 Mich. L. Rev. 1463 (2019) (discussing contours of a plaintiff’s ability to consent to personal jurisdiction).
  23. . Id. at 1466 (“[P]laintiffs arguably have similar entitlements to the protections of personal jurisdiction. In most cases, consent obviates any protections: the plaintiff’s act of filing a complaint in a court manifests the plaintiff’s consent to the personal jurisdiction of that court for purposes of resolving the claims asserted in that complaint.”).
  24. . See Mallory v. Norfolk S. Ry. Co., 600 U.S. 122, 144–46 (2023). 
  25. . Id. at 127.
  26. . Id. at 134. (citing 15 Pa. Cons. Stat. § 411 (2014)). 
  27. . Id. at 127. (citing 42 Pa. Cons. Stat. § 5301(a)(2)(i), (b) (2019)).
  28. . Id. at 141.
  29. . See generally Int’l Shoe Co. v. Washington, 326 U.S. 310 (1945) (providing explanation, justification, and application of contacts analysis).
  30. . See id. at 316–17.
  31. . See Wright & Miller, supra note 5, § 1067.1; Int’l Shoe, 326 U.S. at 316–17.
  32. . Int’l Shoe, 326 U.S. at 316 (quoting Milliken v. Meyer, 311 U.S. 457, 463 (1940)).
  33. . See Perkins v. Benguet Consol. Mining Co., 342 U.S. 437, 445–46 (1952). 
  34. . Id. at 447–48.
  35. . Id. at 438–39. ­
  36. . See id. at 447–48. 
  37. . Id.
  38. . Id. at 448.
  39. . Id.
  40. . See id. at 447–49.
  41. . Daimler AG v. Bauman, 571 U.S. 117, 127–33 (2014) (explaining that the Daimler Court was not overruling Perkins by adding the explicit language of being “at home,” because the Perkins defendant had its activities limited to the forum in a way that made it at home—even if the Court did not use that language in the Perkins decision.). 
  42. . See id. at 134–42.
  43. . Id. at 121.
  44. . Id.
  45. . Id.
  46. . Id. at 117.
  47. . See id.
  48. . Id. at 138, 141.
  49. . See id. at 137–39.
  50. . See id. at 136–37.
  51. . Id. at 119.
  52. . See id. at 129–30 (“We held that the Ohio courts could exercise general jurisdiction over [the defendant in Perkins] without offending due process. That was so, we later noted, because ‘Ohio was the corporation’s principal, if temporary, place of business.’”) (quoting Keeton v. Hustler Mag., Inc., 465 U.S. 770, 780 n.11 (1984)).
  53. . BNSF Ry. Co. v. Tyrrell, 581 U.S. 402, 414 (2017).
  54. . Id. (quoting Daimler AG, 571 U.S. at 139–40 n.20).
  55. . See Wright & Miller, supra note 5, § 1067.1; see also Int’l Shoe Co. v. Washington, 326 U.S. 310, 316 (1945). 
  56. . Ford Motor Co. v. Mont. Eighth Jud. Dist. Ct., 592 U.S. 351, 352 (2021) (quoting Hanson v. Denckla, 357 U.S. 235, 253 (1958)).
  57. . Wright & Miller, supra note 5, § 1069.
  58. . Compuserve, Inc. v. Patterson, 89 F.3d 1257, 1263 (6th Cir. 1996) (quoting S. Mach. Co. v. Mohasco Indus., Inc., 401 F.2d 374, 381–82 (6th Cir. 1968)).
  59. . See Keeton v. Hustler Mag., Inc., 465 U.S. 770, 781 (1984).
  60. . See id. at 772.
  61. . Id.
  62. . Id. at 775.
  63. . Id. at 772.
  64. . Id. at 774.
  65. . Id. at 776.
  66. . Id.
  67. . Calder v. Jones, 465 U.S. 783 (1984). 
  68. . Id. at 783.
  69. . Id.
  70. . Id. at 785–86.
  71. . Id.
  72. . Id. at 789 (citing World-Wide Volkswagen Corp. v. Woodson, 444 U.S. 286, 297–98 (1980); Restatement (Second) of Conflicts of Law § 37 (Am. L. Inst. 1971)).
  73. . Id. at 790.
  74. . For example, in Dudnikov v. Chalk & Vermilion Fine Arts, Inc., the Tenth Circuit heard arguments regarding whether tortious or wrongful conduct need be alleged or if effects targeted at a forum are enough. The court dodged this issue by finding that the complaint alleged sufficiently wrongful conduct to meet the effects test regardless. See Dudnikov v. Chalk & Vermilion Fine Arts, Inc., 514 F.3d 1065, 1071 (10th Cir. 2008); see also Teresa J. Cassidy, Civil Procedure – Effects of the “Effects Test”: Problems of Personal Jurisdiction and the Internet: Dudnikov v. Chalk & Vermilion Fine Arts, Inc., 514 F.3d 1063 (10th Cir. 2008), 9 Wyo. L. Rev. 575, 591–92 (2009).
  75. . See Walden v. Fiore, 571 U.S. 277, 277–78 (2014).
  76. . Id. at 280.
  77. . Id. at 279–80.
  78. . Id. at 280–81.
  79. . See id. at 289–90.
  80. . Id.
  81. . Id. at 290.
  82. . Id. at 285 (quoting Rush v. Savchuk, 444 U.S. 320, 332 (1980)).
  83. . Id. at 290.
  84. . World-Wide Volkswagen Corp. v. Woodson, 444 U.S. 286, 297–98 (1980).
  85. . Id. at 287.
  86. . See id. at 299.
  87. . Id. at 288.
  88. . Id.
  89. . Id.
  90. . Id. at 288–89.
  91. . Id. at 290–91.
  92. . Id.
  93. . See id. at 297–99. 
  94. . Id. at 296–97.
  95. . See J. McIntyre Mach., Ltd. v. Nicastro, 564 U.S. 873, 885–87 (2011). 
  96. . Id. at 878.
  97. . Id.
  98. . See id. at 885–87.
  99. . Id.
  100. . See Burger King Corp. v. Rudzewicz, 471 U.S. 462, 476, 487 (1985). 
  101. . Id. at 466–68.
  102. . Id. at 464.
  103. . Id. at 488–89 (Stevens, J., dissenting).
  104. . See id. at 466–67.
  105. . Id. at 468.
  106. . Id. at 468–69.
  107. . Id. at 469.
  108. . Id. at 481.
  109. . See id. at 487.
  110. . Id. at 482.
  111. . Id. at 487.
  112. . Ford Motor Co. v. Mont. Eighth Jud. Dist. Ct., 592 U.S. 351, 354–55 (2021).
  113. . Id.
  114. . Id. at 357.
  115. . Id.
  116. . Id. at 366–68.
  117. . See id.
  118. . Id. at 365.
  119. . Id. at 355.
  120. . See Erica Mixon & Colin Steele, OTA Update (Over-the-Air Update), TechTarget: Mobile Computing (Dec. 2022), https://www.techtarget.com/searchmobile
    computing/definition/OTA-update-over-the-air-update [https://perma.cc/C6T8-7Q72]. The differences between OTA updates, relating to software, and FOTA updates, relating to firmware, are not addressed in this paper. Instead, OTAUs will be an acronym used to refer to all over-the-air update processes for purposes of exploring the situations where such processes constitute legally significant contacts under personal jurisdiction law. For more information distinguishing between SOTA and FOTA see generally Software-Over-the-Air (SOTA) Versus Firmware-Over-the-Air (FOTA) and JamaicaCAR, aicas realtime, https://donar.messe.de/exhibitor/hannovermesse/ 2017/P8824
    21/whitepaper-fota-vs-sota-eng-504662.pdf [https://perma.cc/YZ6V-EEQB].
  121. . See id.
  122. . See generally Darshan Talati, Understanding the Working of Embedded IoT Medical Devices, eInfochips (Jan. 25, 2024), https://www.einfochips.com/blog/understanding
    -the-working-of-embedded-iot-medical-devices/ [https://perma.cc/WVG4-DNMG] (describing components of IoT-enabled medical devices and how they function). 
  123. . See generally What is SaaS?, SalesForce, https://www.salesforce.com/in/saas/ [https://perma.cc/7KT6-9RRY] (explaining history, characteristics, and features of SaaS).
  124. . See How to Approach OTA Updates for IoT, Medium: Temboo (June 8, 2018), https://medium.com/@temboo/how-to-approach-ota-updates-for-iot-d088c217b31c [https://perma.cc/S9VP-6YTS]. 
  125. . See Sam Byford, Tesla Model S Getting First Ever Over-the-Air Car Firmware Upgrade Next Week, The Verge (Sep. 24, 2012, 9:00 PM), https://www.theverge.com/2012/
    9/24/3385506/tesla-model-s-over-the-air-car-firmware-update [https://perma.cc/N73K-HZQD]
    ; Mixon & Steele, supra note 118.
  126. . Mixon & Steele, supra note 118. 
  127. . See generally Denis A. Pankratev et al., Wireless Data Transfer Technologies in a Decentralized System, in 2019 IEEE Conference of Young Russian Researchers in Electrical & Electric Engineering 620 (IEEE 2019), https://ieeexplore.ieee.org
    /document/8656671 [https://perma.cc/M3FN-FH4J] (discussing problems and potential solutions relating to data exchange between modules of a decentralized system via wireless communication channels).
  128. . Mixon & Steele, supra note 118.
  129. . See The Difference Between Internet, Ethernet, Wifi and Cellular, Signal Boosters: Blog (Sep. 14, 2020), https://www.signalboosters.com/blog/internet-ethernet-wifi-bluetooth-and-cellular-whats-the-difference/ [https://perma.cc/96XT-XQ97]. 
  130. . See id.
  131. . Pankratev et al., supra note 125, at 620 (explaining Wi-Fi decentralization); Kendall Perez et al., Decentralizing Cellular Networks, Magma: Blog (June 8, 2022), https://m
    agmacore.org/blog/decentralizing-cellular-networks/ [https://perma.cc/YCF8-ZEAR]. 
  132. . See Pankratev et al., supra note 125, at 620.
  133. . See id.
  134. . See Deploy Over-the-Air Infrastructure Using Open Source Technologies, Red Hat (Apr. 13, 2022), https://www.redhat.com/en/resources/deploy-over-the-air-infrastructure-overview [https://perma.cc/WN2B-DUYN]. 
  135. . See Grace Lewis, Basics About Cloud Computing, Carnegie Melon: Software Eng’g Inst. (Sept. 2010), https://tv-prod.s3.amazonaws.com/documents%2Fnull-Cloudcomputingbasics.pdf [https://perma.cc/D49B-WAUY]; What is the Cloud?: Cloud Definition, Cloudflare, https://www.cloudflare.com/learning/cloud/what-is-the-cloud/ [https://perma.cc/X3BU-7K5W].
  136. . See What is the Cloud?: Cloud Definition, supra note 133.
  137. . Id.
  138. . See Jim O’Reilly, Resolve a Bottleneck with these Techiniques, TechTarget: Data Center (Mar. 10, 2015), https://www.techtarget.com/searchdatacenter/tip/Dissolve-a-network-bottleneck-with-these-techniques [https://perma.cc/M4BQ-P6UQ].
  139. . ECUs Uncovered: The Secret Engine Behind Your Car!, AutoPi.io (Oct. 23, 2023), https://www.autopi.io/blog/what-is-electronic-control-unit-definition/#:~:text=How%20Many
    %20ECUs%20Does%20ato%20150%20ECUs%20or%20more [https://perma.cc/48EX-7APJ].
  140. . Opinion Writers, Vehicle Cybersecurity: Control the Code, Control the Road, Vehicle Dynamics Int’l (Mar. 18, 2020), https://www.vehicledynamicsinternational.com/fe
    atures/vehicle-cybersecurity-control-the-cod
    e-control-the-road.html#:~:text=Recent%20years
    %20have%20seen%20huge,lines%20of%20code%20by%202030 [https://perma.cc/AGY8-H6
    54].
  141. . Id.
  142. . Id.
  143. . Byford, supra note 123.
  144. . See Justin Fischer, Over-the-Air (OTA) Updates: How Automakers Are Betting on Software to Keep up with the Pace of Innovation, CarEdge (Oct. 2, 2023), https://caredge
    .com/guides/ota-updates-for-cars [https://perma.cc/F8LT-XC3E].
  145. . See id.; By 2028, Automakers Will Save US$1.5 Billion Using Over-the-Air Updates to Fix Recalled Cars, ABIresearch (May 3, 2023), https://www.abiresearch.com/press/by-20
    28-automakers-will-save-us15-billion-using-over-the-air-updates-to-fix-recalled-cars/
    [https://
    perma.cc/NNY9-KWFY]. 
  146. . Subir Halder et al., Secure OTA Software Updates in Connected Vehicles: A Survey, 178 Comput. Networks art no. 107343, at 3 (2020).
  147. . See id. at 2.
  148. . See generally Mallory v. Norfolk S. Ry. Co., 600 U.S. 122 (2023) (finding under a traditional consent theory that a foreign business registration statute conferred personal jurisdiction over a corporation doing business in the state).
  149. . See Daimler AG v. Bauman, 571 U.S. 117, 119 (2014).
  150. . See BNSF Ry. Co. v. Tyrrell, 581 U.S. 402, 413­­–14 (2017).
  151. . See id.
  152. . See Hertz Corp. v. Friend, 559 U.S. 77, 95­–96 (2010). 
  153. . See Rebecca Elliot, Tesla Reports Uptick in Vehicle Deliveries After Price Cuts, WSJ (Apr. 2, 2023, 1:16 PM), https://www.wsj.com/articles/tesla-reports-uptick-in-vehicle-deliveries-after-price-cuts-981863fd [https://perma.cc/T48H-U5UB].
  154. . Herb Frazier, Big Story: Effort to Break Direct Car Sale Ban Stalls at Statehouse, Statehouse Rep. (Sept. 2, 2022, 11:42 AM), https://www.statehousereport.com
    /2022/09/02/
    big-story-effort-to-break-direct-car-sale-ban-stalls-at-statehouse/ [https://perma.cc
    /MCE5-3J48]. 
  155. . Software Updates, Tesla, https://www.tesla.com/support/software-updates#:~:text
    =Tesla%20vehicles%20 receive%20over%2Dthe,Software’% 20tab%20on%20 your%20
    touch
    screen [https://perma.cc/57ZP-BRLM].
  156. . See id.
  157. . See Fatality Facts 2021: State by State, IIHS HLDI (May 2023), https://www.iihs.org/topics/fatality-statistics/detail/state-by-state#fn1 [https://perma.cc/X4QA-6UKC]. 
  158. . Bryant Walker Smith, Automated Driving and Product Liability, 2017 Mich. St. L. Rev. 1, 21–25 (2017). 
  159. . Mark Joye, South Carolina Roads: Rated the Worst in America, Joye L. Firm, https://www.joyelawfirm.com/2019/12/south-carolina-ranks-worst-for-roads-in-usa/ [https://pe
    rma.cc/N97R-UUZB].
  160. . See id.
  161. . IHHS HLDI, supra note 155 (indicating that over a third of vehicular deaths in South Carolina in 2021 involved alcohol).
  162. . See Bryant Walker Smith, How Governments Can Promote Automated Driving, 47 N.M. L. Rev. 99, 114–17 (2017). 
  163. . See Frazier, supra note 152 (providing that 6,400 Tesla vehicles are currently registered in South Carolina); Autopilot and Full Self-Driving Capability, Tesla, https://www.tesla.com/support/autopilot#:~:text=Autopilot%20comes%20standard%20on%20every,and%20Full%20Self%2DDriving%20Capability [https://perma.cc/5AVD-R568] (“Autopilot comes standard on every new Tesla.”).
  164. . See generally Bryant Walker Smith, Proximity-Driven Liability, 102 Geo. L.J. 1777 (2014) (“This Article argues that commercial sellers’ growing information about, access to, and control over their products, product users, and product uses could significantly expand their point-of-sale and post-sale obligations toward people endangered by these products.”).
  165. . Bryant Walker Smith, Driving at Perfection, Stan. L. Sch.: The Ctr. for Internet & Soc’y (Mar. 11, 2012, 3:20 PM), https://cyberlaw.stanford.edu/blog
    /2012/03/
    driving-perfection [https://perma.cc/A7EX-NGJR] (discussing how systems invariably fail).
  166. . Christopher Buchanan, Fiery Crash Involving Electric Car Kills 2 Near Lake Murray, News19 (Sept. 18, 2022, 12:12 PM), https://www.wltx.com/article/traffic/two-dead-electric-car-tree-catches-fire-lake-murray/101-7ca404ff-9980-42bd-afb7-7efdfbbaf9da [https://
    perma.cc/2BSY-YP3N].
  167. . Id.
  168. . Tesla Crashes Through Wall, Plunges into Phoenix Backyard Pool, Fox Carolina (July 28, 2023, 7:21 PM), https://www.foxcarolina.com/video/2023/07/28/tesla-crashes-through-wall-plunges-into-phoenix-backyard-pool/ [https://perma.cc/6Y5M-54WP].
  169. . Id.
  170. . Id.
  171. . Christopher Buchanan, Man Dies After Being Ejected from Fiery Wreck in Sumter County, Coroner Says, News19 (Oct. 12, 2023, 4:47 PM), https://www.wltx.com/article
    /traffic/sumter-county-crash-one-dead-thursday-morning/101-14295940-cec0-4029-97b2-1147
    79846680 [https://perma.cc/QN7D-Q786]. 
  172. . See id.
  173. . See Lauren Feiner & Lora Kolodny, Tesla Urged by Seven Senators to End Forced Arbitration for Workers and Customers, CNBC (May 8, 2023, 5:18 PM), https://www.cnbc.com/2023/05/08/tesla-urged-by-senators-to-end-arbitration-for-employees-c
    onsumers.html [https://perma.cc/K8UB-JPLA].
  174. . Id.
  175. . See Eric Revell, Elon’s Exodus: Tracking Musk’s Business Incorporation State Changes, Fox Bus. (Feb. 16, 2024, 8:00 AM), https://www.foxbusiness.com/technology/elons
    -exodus-tracking-musks-business-incorporation
    -state-changes [https://perma.cc/FH8G-Y8KJ].
  176. . See Gigafactory, Tesla: Careers, https://www.tesla.com/giga-texas [https://perma
    .cc/LP2Z-9EGV].
  177. . Tesla is no exception. See S.C. Sec’y of State, Tesla, Inc., Bus. Entities Online, https://businessfilings.sc.gov/BusinessFiling/Entity/Profile/337eb3c6-776c-45bc-8fbb-449854
    8b0626 [https://perma.cc/A783-FMR4].
  178. . Compare 42 Pa. Cons. Stat. § 5301(a)(2)(i), (b) (2019) with S.C. Code Ann. §§ 33-15-105, -107 (2006).
  179. . See Mallory v. Norfolk S. Ry. Co., 600 U.S. 122, 143–46 (2023).
  180. . See Tesla Sales by State 2024, World Population Rev., https://worldpop
    ulationreview.com/state-rankings/tesla-sales-by-state
    [https://perma.cc/Y9AG-VR3L].
  181. . S.C. Code Ann. § 36-2-803 (Supp. 2023).
  182. . See State v. NV Sumatra Tobacco Trading, Co., 379 S.C. 81, 89, 666 S.E.2d 218, 222 (2008) (“South Carolina’s long-arm statute has been construed to extend to the outer limits of the due process clause. Because South Carolina treats its long-arm statute as coextensive with the due process clause, the sole question becomes whether the exercise of personal jurisdiction would violate due process.”).
  183. . See Wright & Miller, supra note 5, § 1069.
  184. . This only refers to the parent corporation—Tesla, Inc. While Tesla may have subsidiaries that operate independently for certain tasks in South Carolina, subsidiary contacts are considered separately. See generally James M. Beck, Post-BMS: Jurisdiction over Subsidiary ≠ Jurisdiction over Parent, Drug & Device L. (Apr. 9, 2019), https://www.druganddevicelawblog.com/2018/04/post-bms-jurisdiction-over-subsidiary-%E2
    %89%A0-jurisdiction-over-parent.html
    [https://perma.cc/8D7Z-FUBQ] (discussing effect of subsidiary’s contacts on whether parent has purposefully availed itself of a forum).
  185. . See US Tesla Stores & Galleries, Tesla, https://www.tesla.com/findus/list/stores
    /
    United+States [https://perma.cc/DVB7-B9VH].
  186. . See S.C. Code Ann. § 56-15-45(D) (Supp. 2023).
  187. . See Frazier, supra note 152.
  188. . Stephanie Moore, Tesla Opening Facility in Greenville County, Company Announces, WYFF 4 (Jan. 18, 2024, 12:54 PM), https://www.wyff4.com/article/south-carolina-tesla-greenville-county/46436985 [https://perma.cc/6GLG-TPSL].
  189. . See id.
  190. . See generally Taking Delivery, Tesla, https://www.tesla.com/support/taking-delivery [https://perma.cc/WYQ9-8ADG] (explaining Tesla delivery policy and procedure).
  191. . See US Tesla Service Centers, Tesla, https://www.tesla.com/findus/list/services
    /United%
    20States [https://perma.cc/VKA6-ZEUN].
  192. . See Go Anywhere, Tesla, https://www.tesla.com/trips [https://perma.cc/Z9QD-ZLBQ].
  193. . See id.
  194. . Advertising Age Names Tesla One of “America’s Hottest Brands”, Tesla (Apr. 20, 2010), https://www.tesla.com/blog/advertising-age-names-tesla-one-%E2%80%9Camerica%
    E2%80%99s-hottest-brands%E2%80%9D
    [https://perma.cc/2LLW-QJUL].
  195. . Chris Isidore, Tesla Will Advertise for the First Time, CNN: Bus. (May 16, 2023, 7:58 PM), https://www.cnn.com/2023/05/16/business/tesla-advertising/index.html [https://p
    erma.cc/7LUP-LBWM].
  196. . See id.
  197. . See Tesla Sales by State 2024, supra note 178 (demonstrating South Carolina is not even in the top 50% of Tesla markets based on estimated sales for 2021–22).
  198. . See Preparing for a Mobile Service Appointment, Tesla, https://www.tesla.com/
    support/mobile-service [https://perma.cc/XP58-XNRZ].
  199. . See id.; Vehicle Maintenance, Tesla, https://www.tesla.com/support/vehicle-maintenance#:~:text=your%20Tesla%20vehicle.-,Unlike%20gasoline%20cars%2C%20Tesla
    %20vehicles%20require%20no%20traditional%20oil%20changes,reducing%20wear%20on%20the%20brakes [https://perma.cc/G86P-G52C].
  200. . See Vehicle Maintenance, supra note 197.
  201. . Id.
  202. . See id.
  203. . See Frazier, supra note 152 (providing that 6,400 Tesla vehicles are currently registered in South Carolina).
  204. . See Software Updates, supra note 153.
  205. . Elon Musk (@elonmusk), X (Apr. 13, 2019, 12:18 PM), https://twitter.com/elonmusk/status/1117099861273219073 [https://perma.cc/9SX8-79L2].
  206. . See Jacob Marsh, How Long Does a Tesla Car Battery Last?, energysage (May 4, 2023), https://www.energysage.com/electric-vehicles/how-long-do-tesla-car-batteries-last/ [https://perma.cc/6H9H-DSNT].
  207. . Nick Zamanov, How Many Years Will an Electric Car Last?, Cyber Switching (Nov. 26, 2022), https://cyberswitching.com/how-many-years-will-an-electric-car-last/ [https://perma.cc/H8EE-LKB2].
  208. . See id.
  209. . See Giedrius Pakalka & Alius Noreika, How Tesla Cars Connect to Internet? (Easy Guide), Technology.org, https://www.technology.org/how-and-why/how-tesla-cars-connect-to-internet/ [https://perma.cc/ZQ8K-Z38U]; see also Brian Wang, Future Tesla AI Cloud Vs Amazon AWS, Google Cloud, Alibaba, Next Big Future (Aug. 22, 2021), https://www.nextbigfuture.com/2021/08/future-tesla-ai-cloud-vs-amazon-aws-google-cloud-ali
    baba.html [https://perma.cc/HN92-QNZP].
  210. . See Fischer, supra note 142.
  211. . See Upgrades, Tesla, https://www.tesla.com/support/upgrades#tesla-accordion-123-are-over-the-air-software-updates-no-longer-free [https://perma.cc/K57P-DQS7].
  212. . See Software Updates, supra note 153 (“When an update is available, we will notify you through an alert on your vehicle’s touchscreen and the Tesla app. . . . We do not send software updates to individual vehicles upon request.”).
  213. . See Andrew Tierney, Reverse Engineering the Tesla Firmware Update Process, Pen Test Partners (Feb. 12, 2020), https://www.pentestpartners.com/security-blog/reverse-engineering-the-tesla-firmware-update-process/ [https://perma.cc/STL5-EJ6V] (discussing how Tesla hardcodes in communication protocols with its servers that loop to ensure accurate and secure data transfers for its firmware update process).
  214. . Sean O’Kane, Tesla Can Change So Much with Over-the-Air Updates that It’s Messing with Some Owners’ Heads, The Verge (June 2, 2018, 1:00 PM), https://www.theverge.com/2018/6/2/17413732/tesla-over-the-air-software-updates-brakes [htt
    ps://perma.cc/G95M-7D3J] (“Tesla has shipped OTA updates to its cars for years now that have changed everything from its Autopilot driver assistance system to the layout and look of its touchscreen interfaces. At one point last year, it even used an update to extend the range of some cars to help customers evacuate the path of Hurricane Irma.”).
  215. . See id.
  216. . See id.; see also Autopilot and Full Self-Driving Capability, supra note 161.
  217. . See Autopilot and Full-Self Driving Capability, supra note 161 (describing the levels of automation); Full Self-Driving Capability Subscriptions, Tesla, https://www.tesla.com/support/full-self-driving-subscriptions [https://perma.cc/7QQA-QCSM] (describing payment plan for full self-driving capability).
  218. . Autopilot and Full-Self Driving Capability, supra note 161. The prudence of Tesla labelling each software package this way is beyond the scope of this paper, but it should be noted that this software—when placed in the standard six ascending levels of driving automation (L0–L5)—ranges from level 1 to level 2+ by most standards. See Bryant Walker Smith, How Reporters Can Evaluate Automated Driving Announcements, 2020 J.L. & Mobility 1, 4 (2020). Only recently have level 3 automated vehicles become commercially available, and still even those vehicles are far from level 5 automation, the level that comports most clearly with the layman understanding of a self-driving vehicle. Furthermore, such level 3 vehicles are only permitted in specific places. See Mercedes-Benz, Automated Driving Revolution: Mercedes-Benz Announces U.S. Availability of DRIVE PILOT – The World’s First Certified SAE Level 3 System for the U.S. Market, Mercedes-Benz: Media Newsroom USA (Sept. 27, 2023), https://media.mbusa.com/releases/automated-driving-revolution-mercedes-benz-announces-us-availability-of-drive-pilot-the-worlds-first-certified-sae-level-3-system-for-the-us-market [https://perma.cc/9QC8-8WQA] (announcing Mercedes-Benz’s first of the kind level 3 driving car).
  219. . See Autopilot and Full Self-Driving Capability, supra note 161.
  220. . See id.
  221. . See generally Lennon Cihak, Why Tesla Doesn’t Update All of Its Vehicles at Once, not a tesla app (Oct. 11, 2022), https://www.notateslaapp.com/tesla-reference/921/why-tesla-doesn-t-update-all-of- its-vehicles-at-once [https://perma.cc/DH2B-WCMW] (describing how Tesla releases its updates).
  222. . See id.
  223. . See Obtain a Copy of the Data Associated with Your Tesla Account, Tesla, https://www.tesla.com/support/privacy#:~:text=Tesla%20vehicles%20record%20operational%20and,the%2Dair%20to%20our%20servers [https://perma.cc/KGJ5-572X] (discussing some of the data recorded by vehicles and how Tesla accesses it); Agam Shah, How Tesla Uses and Improves Its AI for Autonomous Driving, Enterprise AI (Mar. 8, 2023), https://www.enterpriseai.news/2023/03/08/how-tesla-uses-and-improves-its-ai-for-autonomous
    driving/#:~:text=Tesla%20mines%20its%20network%20of,cars%20through%20FSD%20software%20upgrades
    [https://perma.cc/5TAS-4UHP].
  224. . See generally Univ. of S. Cal., Is Your Mobile Provider Tracking Your Location? New Technology Could Stop It, ScienceDaily (Aug. 12, 2021), https://www.sciencedaily.
    com/releases/2021/08/210812135929
    .htm [https://perma.cc/KPT5-MGZC] (discussing cellular location tracking); Chris Hoffman, How Devices Use Wi-Fi to Determine Your Physical Location, How-To Geek (Jan. 18, 2021), https://www.howtogeek.com/708500/how-devices-use-wi-fi-to-determine-your-physical-location/ [https://perma.cc/9527-LX68] (discussing how Wi-Fi alone is enough to determine physical location in many instances).
  225. . See Cihak, supra note 219 (stating that Tesla updates its vehicles based on a regional rollout system); see also Mark Harris, Who Actually Owns Tesla’s Data?, IEEE Spectrum (Aug. 5, 2022), https://spectrum.ieee.org/tesla-autopilot-data-ownership [https://perma.cc/VT4H-66QR] (arguing that the breadth of data collected under the Tesla self-driving apparatus alone would make it almost impossible to not know a vehicle’s location and the owner of the vehicles). But see Disclaimers, Tesla, https://www.tesla.com/ownersmanua
    l/model3/en_jo/GUID-2E8E5E0B-DAA8-40B8-9804-45
    F5960538DF.html#:~:text=Tesla%2
    0does%20not%20disclose%20the%20data%20recorded%20%20in,the%20vehicle%20owner%20or%20identification%20information.%20More%20items [https://perma.cc/G667-9SWZ] (claiming that Tesla does not save location data related to specific vehicles in its Event Data Recorder (EDR) except in the event of a crash).
  226. . Again, the propriety of Tesla’s verbiage is contestable because its vehicles are not safe for unsupervised use. See Autopilot and Full Self-Driving Capability, supra note 161, for Tesla’s descriptions.
  227. . Alain Sherter, Tesla Recalls More than 120,000 Vehicles Because Doors Can Unlatch in a Crash, CBS News (Dec. 22, 2023, 11:19 AM), https://www.cbsnews.com/news/
    tesla-recall-2023-doors-lock-autopilot-nhtsa/
    [https://perma.cc/5F8K-CL69].
  228. . See id.
  229. . See id.
  230. . See Nat’l Highway Traffic Safety Admin., U.S. Dep’t of Transp., 23V-085, Part 573 Safety Recall Report (2023), https://static.nhtsa.gov/odi/rcl/2023/RCLRPT-23V085-3451.PDF [https://perma.cc/S98M-8MB5].
  231. . Nora Naughton, Tesla Is Recalling Almost Every Car It Has Ever Sold in China, Bus. Insider (May 12, 2023, 11:23 AM), https://www.businessinsider.com/tesla-issues-recall-cars-china-2023-5 [https://perma.cc/Q4T4-ZCPK].
  232. . See id. Note that the term software here is used generally. Distinctions between firmware and software may be important for a more nuanced discussion of effected systems, but such distinctions will not be addressed here. See Tatsiana Tsiukhai, How OTA Technology Helps Update Connected Cars on the Fly, Softeq (June 17, 2021), https://www.softeq.com/bl
    og/ota-technology-updating-connected-cars-on-the-go
    [https://perma.cc/S5G8-PECW] for a discussion of OTAUs that includes firmware versus software distinctions.
  233. . See Lurah Lowery, OEM Shift to OTA Recall Fixes Predicted to Occur by 2028, Repairer Driven News (May 9, 2023), https://www.repairerdrivennews.com/2023/05/09 /oem-shift-to-ota-recall-fixes-predicted-to-occur-by-2028/ [https://perma.cc/WX5X-XFN2] (discussing the financial advantages of using OTAUs).
  234. . See Nat’l Highway Traffic Safety Admin., U.S. Dep’t of Transp., 23V-489, Part 573 Safety Recall Report (2023), https://static.nhtsa.gov/odi/rcl/2023/RCLRPT-23V489-8374.PDF [https://perma.cc/JYZ7-XH7S].
  235. . Kevin Armstrong, Tesla Issues Physical Recall After Identifying a Forward-Facing Camera Issue, not a tesla app (July 25, 2023), https://www.notateslaapp.com/news/1532
    /tesla-issues-physical-recall-after-identifying-a-forward-facing-camera-issue
    [https://perma.cc/
    3N26-848E].
  236. . See Steve Stecklow, Exclusive: Two US Senators Call for Tesla Recalls After Reuters Investigation, Reuters (Dec. 28, 2023, 7:45 AM), https://www.reuters.com/business/
    autos-transportation/two-us-senators-call-tesla-recalls-after-reuters-investigation-2023-12-27/
    [https://perma.cc/6Q97-9ZYQ].
  237. . See id.
  238. . See The Electromagnetic Spectrum, NASA Hubblesite (Sept. 30, 2022), https://hu
    bblesite.org/contents/articles/the-electromagnetic-spectrum [https://perma.cc/EQD4-8YA9].
  239. . See Int’l Union of Painters & Allied Trades Dist. Council 15 Loc. 159 v. Great Wash Park, LLC, No. 67453, 2016 WL 4499940, at *2 (Nev. App. Aug. 18, 2016).
  240. . See Debra Cassens Weiss, Sending a Flashing GIF to Provoke a Seizure Can Constitute Battery, Federal Judge Rules, ABA: ABA Journal (June 7, 2018, 7:00 AM), https://www.abajournal.com/news/article/sending_a_flashing_gif_to_provoke_a_seizure_can_constitute_battery_federal [https://perma.cc/P3Z5-465A].
  241. . See Compuserve Inc. v. Cyber Promotions, Inc., 962 F. Supp. 1015, 1025–28 (S.D. Ohio 1997).