TheMurrow

Congress Is About to ‘Ban’ Car Repair Monopolies—But the Real Fight Is Over One Plug That Can See Where You Drove

Washington’s next auto war isn’t emissions or tariffs—it’s who controls the software logs and telematics data that make repair possible. The REPAIR Act could open access, but also widen the data pipe.

By TheMurrow Editorial
March 10, 2026
Congress Is About to ‘Ban’ Car Repair Monopolies—But the Real Fight Is Over One Plug That Can See Where You Drove

Key Points

  • 1Track the real move in Congress: the REPAIR Act targets fair access to vehicle repair data—not a literal “ban” on automakers or dealers.
  • 2Follow the choke point: OBD‑II is symbolic, but modern repair hinges on telematics, OEM servers, and software controls that can gate diagnostics.
  • 3Weigh the tradeoff: broader access could revive independent repair, yet FTC authority to expand “vehicle-generated data” raises privacy and cybersecurity stakes.

The next big car fight in Washington isn’t about tailpipes or tariffs. It’s about data—who gets it, who controls it, and whether a vehicle owner can choose a repair shop without hitting a digital paywall.

For decades, “right to repair” sounded like a practical dispute over parts and tools. Modern cars changed the stakes. A repair today often requires access to software, diagnostic logs, and the streams of information a vehicle generates every time it moves, charges, brakes, or phones home. That information can be the difference between a quick fix at a neighborhood garage and a mandatory appointment at a dealership.

The most common headline shorthand says Congress is “about to ban” something—usually a “repair monopoly.” What’s actually moving on Capitol Hill is narrower, and in some ways more consequential: a bill that would force the auto industry to open up access to vehicle repair data on fair terms. The heart of the battle is not a single wrench, but the digital gatekeepers that now sit between drivers and their own vehicles.

“The modern repair fight isn’t about a bolt you can’t reach. It’s about a file you can’t access.”

— TheMurrow Editorial

What Congress is really considering: the REPAIR Act, not a “ban”

Two bills—one in the House and one in the Senate—form the spine of the current federal push for auto right-to-repair.

### The House bill: H.R. 1566
In the 119th Congress, the key House proposal is H.R. 1566, the “Right to Equitable and Professional Auto Industry Repair Act (REPAIR Act).” It was introduced on Feb. 25, 2025 by Rep. Neal Dunn (R-FL) with bipartisan support, including Rep. Marie Gluesenkamp Perez (D-WA). The latest logged action is procedural but meaningful: on Feb. 10, 2026, the bill was forwarded by the House Commerce, Manufacturing, and Trade Subcommittee to the full committee by voice vote, according to Congress.gov.

That “voice vote” matters because it signals the measure cleared a hurdle without forcing members to record a position—often a sign leadership believes it can move without blowing up into a partisan brawl.
Feb. 10, 2026
H.R. 1566 was forwarded by the House Commerce, Manufacturing, and Trade Subcommittee to the full committee by voice vote (per Congress.gov).

The Senate companion: S. 1379

The Senate version is S. 1379, introduced Apr. 9, 2025 by Sen. Ben Ray Luján (D-NM) and Sen. Josh Hawley (R-MO). That pairing—Democrat and Republican—telegraphs what both sides see in the issue: populist consumer politics on one hand, anti-monopoly competition policy on the other.

The important clarification for readers: the REPAIR Act does not “ban” automakers from existing, nor does it outlaw dealers. The bill is fundamentally a data-access and competition measure aimed at the post-sale repair market—diagnostics, service, maintenance—especially as cars become more software-driven.

“Calling it a ‘ban’ misses the point. The bill’s real lever is access—access to the data that makes repair possible.”

— TheMurrow Editorial

The bill’s promise: fair access to repair data, tools, and “critical repair information”

Supporters frame the REPAIR Act in plain terms: if you own the car, you should be able to choose who fixes it—and that choice should not be quietly defeated by proprietary software locks.

### What the REPAIR Act targets
According to the bill text on Congress.gov, the REPAIR Act’s core goal is to ensure vehicle owners and their chosen repairers can obtain:

- Vehicle-generated data
- Critical repair information
- Tools needed to diagnose and fix vehicles

The access standard is crucial. The bill uses the familiar competition-policy phrasing: “fair, reasonable, and non-discriminatory” terms. That language is designed to prevent a nominal “yes, you can access it” that is priced or structured so heavily that only dealership networks can realistically comply.

What the REPAIR Act says owners and repairers should be able to get

  • Vehicle-generated data
  • Critical repair information
  • Tools needed to diagnose and fix vehicles
  • Access on “fair, reasonable, and non-discriminatory” terms

Why this matters more now than 10 years ago

In older vehicles, a competent technician could diagnose many problems with physical inspection and a scan tool. In newer cars, diagnostics increasingly depend on software logs, calibration routines, and manufacturer-controlled systems. In practice, the ability to repair can turn into the ability to authenticate, decrypt, or connect to an OEM server.

The legislation tries to pull that power back toward the owner and independent shop. Opponents argue the system already works; supporters counter that access is tightening as vehicles become connected devices on wheels.

For the average driver, the takeaway is simple: the bill aims to stop a world where “you can repair it” becomes “you can repair it—if the manufacturer says so.”

Key Insight

Modern repair disputes often hinge on software authorization and OEM servers—not just parts, tools, or mechanical know-how.

“One plug” and the real-world choke point: OBD‑II and beyond

Talk to mechanics and you’ll hear a deceptively modest phrase: “one plug.” The plug is usually the OBD‑II portOn-Board Diagnostics, a standardized interface required on U.S. light-duty vehicles starting with the 1996 model year, as described in reporting such as Tom’s Guide.

### What OBD‑II does—and what it doesn’t
Historically, OBD‑II was closely associated with emissions diagnostics and check-engine codes. It gave repairers a standardized way to read trouble codes and basic system information across brands. That standardization helped create a competitive aftermarket for scan tools and repair services.

Modern cars, though, are no longer defined by what you can read from a port under the dash. The more contentious question is who controls the richer streams of data and functions that increasingly sit behind:

- Physical access (scan tools, OBD‑II devices)
- Telematics (vehicle-to-cloud communications)
- Software and cryptographic controls that can restrict access in the name of cybersecurity

A Congressional Research Service (CRS) analysis underscores that the contest has moved from hardware interfaces to software authorization and data governance. The OBD‑II port remains symbolic—proof that standardization can work—but it may no longer be sufficient for comprehensive repair access.
1996
OBD‑II became a required standardized interface on U.S. light-duty vehicles starting with the 1996 model year.

The privacy edge of “just plugging in”

Even basic plug-in devices can raise privacy issues. As NTIA materials have noted in related discussions, vehicle data can include or enable inferences about geolocation and driving behavior. Some devices include GPS; others derive sensitive patterns indirectly from vehicle signals.

The public policy problem is that the same data that helps diagnose a transmission fault can also reveal where a person drives, when they stop, and how they behave behind the wheel.

“The fight isn’t only about whether you can fix your car. It’s about how wide the data pipe becomes once Washington mandates access.”

— TheMurrow Editorial

The “data grab” critique: how the REPAIR Act could expand what counts as vehicle data

The sharpest criticism of the REPAIR Act is not that it helps independent shops. The criticism is that it could widen the aperture for data sharing far beyond what a repair requires.

### CRS: the definition can expand
According to the CRS analysis, the bill would allow the Federal Trade Commission (FTC)—in consultation with NHTSA—to expand the definition of “vehicle-generated data,” potentially beyond repair-related data, while considering cybersecurity and privacy.

That design choice is a policy Rorschach test. To supporters, it’s a flexible mechanism to keep up with fast-changing vehicle tech. To critics, it’s an open-ended authority that could normalize broad data extraction under the banner of repair.

Why the expansion authority matters

When lawmakers write tech policy, definitions do the heavy lifting. “Vehicle-generated data” can be narrow—diagnostic trouble codes and service logs—or expansive—continuous telemetry, location, driver behavior metrics, and more. The CRS point is that the bill leaves room for the FTC to shape that boundary over time.

For consumers, the risk is not abstract. A system designed to let a trusted mechanic access necessary repair information could become an ecosystem where intermediaries collect and monetize data, unless privacy rules and enforcement are strong, clear, and workable.

Editor’s Note

The hinge question is definitional: will “vehicle-generated data” stay tightly repair-scoped, or drift toward broader telemetry and behavioral data over time?

The industry pushback: “we already solved this” vs. “OEMs are tightening control”

The debate is often portrayed as manufacturers versus independent repair. The reality is a tangle of interests: automakers, dealer networks, aftermarket parts makers, tool companies, independent garages, and consumer advocates. The bill has bipartisan sponsors because it slices across conventional lines.

### Opponents: unnecessary, burdensome, and risky
Auto dealer and manufacturer-aligned opponents argue the bill is unnecessary because of existing industry arrangements, including a 2014 Memorandum of Understanding (MOU) and later commitments. The National Automobile Dealers Association (NADA) has described the REPAIR Act as creating a new regulatory framework and administrative burdens.

NADA also argues the proposal could enable data brokers or certain third parties to sell vehicle data, and raises concerns about consumer control over data deletion, as characterized in its legislative materials.

Those arguments land with lawmakers who are wary of broad federal mandates—especially when they touch cybersecurity and privacy. A mandated access regime that is poorly secured could create new attack surfaces, and opponents insist automakers have incentives to keep systems locked down for safety.
2014
Industry opponents cite a 2014 Memorandum of Understanding (MOU) and later commitments as evidence that right-to-repair access is already addressed.

Supporters: access is shrinking in practice

Supporters—often aligned with the aftermarket and independent repair sector—argue the practical reality is moving in the other direction: OEMs increasingly restrict access to the information needed for maintenance and repair, nudging owners toward dealerships with higher prices and longer waits.

Testimony in House materials from the independent repair perspective has emphasized that a workable framework can preserve cybersecurity and intellectual property protections while restoring competitive repair markets. The argument is not “open everything,” but “open what is necessary, on fair terms, to the owner’s chosen repairer.”

The disagreement is partly philosophical and partly empirical: are existing commitments enough, or are they being outpaced by software-centric cars and telematics systems?

The core argument clash

Pros

  • +More competition in post-sale repairs; predictable access for independents; limits “dealer-only” lock-in

Cons

  • -New regulatory burdens; cybersecurity attack-surface worries; risk of broader third-party data monetization

Massachusetts as the preview: the telematics battle that won’t stay local

If the federal fight feels theoretical, Massachusetts shows what it looks like on the ground.

### Question 1 (2020) and the telematics turning point
In 2020, Massachusetts voters approved Question 1, expanding the state’s earlier right-to-repair framework. The new requirement targeted telematics—the vehicle-to-cloud systems that increasingly carry the data repairers need.

The law required that beginning with model year 2022, vehicles with telematics must provide owners access through a standardized open-access platform, enabling them to share repair data with independent shops. Reporting including NBC Boston has tracked the resulting conflict, including years of litigation and disputes that contributed to delayed or uneven enforcement.

Massachusetts matters because it isolates the core question: when data no longer lives primarily in the car, but in the cloud, what does “right to repair” even mean?
Model year 2022
Massachusetts’ Question 1 required telematics-equipped vehicles (starting model year 2022) to provide owner access via a standardized open-access platform.

What the Massachusetts fight teaches Washington

Three lessons travel well:

1. Telematics is the new choke point. A standardized port is less relevant when the richest diagnostic information is transmitted remotely.
2. Cybersecurity becomes the universal argument. Opponents warn that opening access increases risk; supporters say security can be built without monopoly control.
3. Implementation is everything. A right on paper can collapse without practical standards, enforcement, and clear accountability.

The federal REPAIR Act, in part, is an attempt to avoid a patchwork of state rules and to create a national baseline. Whether it succeeds depends on how it handles the twin anxieties Massachusetts exposed: security and data governance.

Three Massachusetts lessons for federal lawmakers

  1. 1.Telematics is the new choke point when diagnostic data lives in the cloud.
  2. 2.Cybersecurity becomes the go-to argument on both sides.
  3. 3.Implementation determines whether a “right” works in practice or collapses in standards disputes.

What it means for drivers and independent shops: practical takeaways, not slogans

Most readers don’t care which subcommittee forwarded what by voice vote. The real question is what changes at the service counter—and what tradeoffs come with it.

### Practical implications if a federal framework advances
If a bill like the REPAIR Act became law as designed, consumers could plausibly see:

- More repair options, especially for software-heavy diagnostics
- Less forced channeling to dealerships for routine fixes that require proprietary access
- More price competition and potentially shorter wait times, depending on local shop capacity

Independent repairers could gain more predictable access to the information needed to service late-model vehicles. Aftermarket tool makers could build products against clearer access requirements rather than brand-by-brand workarounds.

If a federal access framework advances, consumers could see

  • More repair options for software-heavy diagnostics
  • Less forced channeling to dealerships for routine fixes
  • More price competition and potentially shorter wait times

The privacy and security questions that won’t go away

The same framework could also raise risks if rules are vague or enforcement is weak:

- Expanded access could increase the number of entities capable of collecting vehicle data.
- Consumers might not understand what they are authorizing when they consent to “share data with my repairer.”
- Cybersecurity claims can be genuine. A poorly designed access system could become an entry point for fraud or malicious intrusion.

The CRS observation—FTC authority to expand “vehicle-generated data”—is the hinge. A narrow definition aimed at repair is one policy. A gradually expanding scope that includes non-repair telemetry is another.

A serious federal solution would treat privacy as infrastructure, not a footnote: clear limits, transparency, and meaningful enforcement.

Key Takeaway

A repair-access mandate without strong privacy guardrails can become a data-access mandate—expanding who can collect, keep, and monetize sensitive vehicle information.

Conclusion: the next repair bill is a data bill—so readers should treat it like one

The REPAIR Act is not a simple morality play about greedy manufacturers or heroic independent mechanics. It’s a contest over the rules of access in a world where cars behave like networked computers.

On one side: a bipartisan argument that ownership should include the practical ability to maintain and repair what you buy, without proprietary locks turning independent service into an impossibility. On the other: a warning that mandated access can widen into a data-extraction regime and introduce real cybersecurity risk.

The most honest framing is also the most bracing: modern right-to-repair policy is a decision about how much of your car’s digital life can be shared, with whom, and under what safeguards. The “one plug” story is the approachable metaphor. The real story is governance—standards, definitions, and enforcement—before the access mandate becomes a data mandate.
T
About the Author
TheMurrow Editorial is a writer for TheMurrow covering explainers.

Frequently Asked Questions

Is Congress “banning” car repair monopolies?

No. The leading federal proposal is the REPAIR Act (H.R. 1566 / S. 1379), focused on access to vehicle repair data, tools, and critical repair information on fair, reasonable, and non-discriminatory terms—aimed at post-sale competition, not banning firms.

What is H.R. 1566, and where is it now?

H.R. 1566 is the House REPAIR Act, introduced Feb. 25, 2025 by Rep. Neal Dunn (R-FL) with bipartisan support including Rep. Marie Gluesenkamp Perez (D-WA). On Feb. 10, 2026 it was forwarded by the House Commerce, Manufacturing, and Trade Subcommittee to the full committee by voice vote (Congress.gov).

What is S. 1379?

S. 1379 is the Senate companion bill, introduced Apr. 9, 2025 by Sen. Ben Ray Luján (D-NM) and Sen. Josh Hawley (R-MO). It similarly focuses on ensuring owners and their chosen repairers can access vehicle-generated data and repair information needed for modern vehicles.

What does “one plug” mean in this debate?

It refers to the OBD‑II port, the standardized on-board diagnostics interface required on U.S. light-duty vehicles starting with the 1996 model year. But the modern dispute increasingly involves telematics and software-controlled access beyond what a physical port provides.

Why do critics call it a “data grab”?

A CRS analysis notes the REPAIR Act would allow the FTC, in consultation with NHTSA, to expand the definition of “vehicle-generated data,” potentially beyond repair-related data, while considering cybersecurity and privacy—raising concerns about monetization and privacy risks.

Why does Massachusetts keep coming up?

Massachusetts’ Question 1 (2020) required that starting with model year 2022, telematics-equipped vehicles provide owners access via a standardized open-access platform to share repair data with independent shops. Litigation and enforcement challenges highlight how hard telematics-era implementation can be.

More in Explainers

You Might Also Like