The ‘Right to Repair’ Bill Isn’t About Fixing Cars—It’s About Who Owns the Data Your Vehicle Generates (and 3 groups are fighting over it in Congress right now)
Modern repairs increasingly require access to telematics and software permissions that can be routed through an automaker’s cloud. The REPAIR Act would decide whether that data access is a legal right—or a gated platform.

Key Points
- 1Track the shift: right to repair now hinges on telematics and software permissions, not just manuals, tools, or diagnostic codes.
- 2Understand the bill: the REPAIR Act (H.R. 1566 / S. 1379) targets repair-and-maintenance data access with FTC oversight and reporting.
- 3Follow the power blocs: aftermarket wants access, automakers want controlled authentication for safety and revenue, regulators must balance security and competition.
The fight over right to repair isn’t on the garage floor anymore
Modern vehicles are computers on wheels, constantly generating and transmitting vehicle-generated data through embedded software and telematics systems. That data is what a shop needs to diagnose a failing sensor, calibrate a camera after a windshield replacement, or reset a software lock after a part swap. The newest battleground is not the garage floor—it’s the data stream.
Automakers have learned something every platform company already knows: control the interface, control the market. If diagnostics and authorizations flow through an automaker’s proprietary cloud, then repair access becomes a question of permission, pricing, and gatekeeping—often far from the customer’s view.
Congress is now testing whether access to repair data is a consumer right, a safety risk, or simply the next high-stakes market for digital control. The federal bill at the center of that test is bluntly named, and the politics around it are anything but.
Right to repair has become a fight over who gets to see—and use—the car’s data exhaust.
— — TheMurrow
The real shift: from manuals and tools to telematics and software locks
Put differently: in the connected-car era, you can have the right wrench and still not have the right permission. The repair relationship increasingly runs through software rules that are designed upstream—by manufacturers and their authorized systems—and enforced downstream at the moment a shop needs to complete work.
This is why the debate has escalated from “access to information” to “access to systems.” Manuals and codes matter, but the practical ability to finish a repair can now depend on telematics interfaces, server-side approvals, and OEM-controlled workflows that don’t sit in the shop at all.
What “vehicle-generated data” actually means in practice
- Diagnose faults and confirm repairs
- Calibrate sensors and safety systems after service
- Access software-driven functions tied to a part replacement
- Perform maintenance using the same information available to franchised dealers
The more vehicle systems migrate to software and sensors, the more a repair becomes a negotiation with the car’s operating rules. Even basic work can require data access that only the manufacturer—or its approved channel—can reliably provide.
And because these access points are increasingly mediated by telematics and embedded software, the “where” of repair can shift too: the decisive barrier might not be in the bay, but behind a login, a subscription, or a remote authorization path.
Repair-relevant vehicle-generated data can include
- ✓Diagnose faults and confirm repairs
- ✓Calibrate sensors and safety systems after service
- ✓Access software-driven functions tied to a part replacement
- ✓Perform maintenance using the same information available to franchised dealers
Why the stakes expanded beyond repair
That’s why the fight attracts more than mechanics and hobbyists. It implicates how a multi-sided market will function: who gets to compete, who sets the fees, who owns the customer relationship, and who gets to monetize the data exhaust created by ordinary driving.
In platform markets, interface control is market control. Congress is now being asked whether connected cars should evolve like open ecosystems—where owners can designate service providers—or like locked platforms, where effective choice depends on what the manufacturer’s channel allows.
The REPAIR Act, explained: what Congress is debating in 2025–2026
Here are the core, research-grounded facts:
- H.R. 1566 was introduced February 25, 2025, with Rep. Neal Dunn (R-FL) listed as sponsor. (Congress.gov)
- A Senate companion, S. 1379, is also titled the REPAIR Act and appears in the 119th Congress; third-party legislative trackers and Congress.gov list April 9, 2025 as the introduction date. (Congress.gov)
- The bill text defines “telematics system” and sets up a federal oversight role that includes FTC involvement and reporting to Congress after enactment. (Congress.gov)
The bill’s blunt naming hides a complex and consequential question: whether access to modern repair inputs—especially telematics-derived data and software interfaces—should be guaranteed by law, or remain within manufacturer-controlled systems.
In other words, this isn’t only about tools in the physical world. It’s about the terms under which digital systems that are essential to repair are made available, and whether those terms are set through public policy or private contracts.
The REPAIR Act isn’t a culture-war slogan. It’s an argument about whether repair access lives in law—or inside a private cloud.
— — TheMurrow
The policy mechanism, not the slogan
The bill also contemplates a meaningful federal compliance footprint. The text explicitly points toward FTC rulemaking/oversight and periodic reporting structures. That matters because it signals Congress is not merely expressing a preference; it is proposing enforcement architecture.
The practical significance is in the definition of “comparable” access. If the standard is real parity—usable, timely access that enables independent shops to complete repairs end-to-end—then the market changes. If “access” can be technically provided but functionally obstructed, then the status quo can persist under new labels.
Key Insight
Where the bill stands now: the 2026 procedural picture
Two dated milestones from the current cycle anchor the REPAIR Act’s recent movement:
- January 2026: A House subcommittee hearing included testimony on the REPAIR Act and related proposals. Witnesses and stakeholders debated whether the measure would strengthen consumer choice or create safety and security risks. (Repairer Driven News, Jan. 15, 2026)
- February 10, 2026: The Auto Care Association reported the bill was forwarded by a House Energy & Commerce subcommittee to the full committee. (Auto Care Association, Feb. 10, 2026)
Those steps do not guarantee passage. They do show the issue has moved from advocacy slogans into the machinery of Congressional bargaining.
The procedural picture matters because it reveals something else: the closer a proposal gets to real committee action, the more stakeholders must argue about text, definitions, enforcement, and implementation—not just principles.
Why this matters even before a final vote
- Who owns the data your car generates?
- Who decides which shop can see it?
- What counts as “repair and maintenance” versus something else?
Even a stalled bill can reframe the rules businesses assume they can enforce.
This is part of why “momentum” is not only a vote count. It’s also the way a debate changes behavior: what manufacturers disclose, what shops can demand, what consumers learn to ask, and what regulators prepare to police.
Editor’s Note
The three blocs fighting over it: access, control, and risk
One bloc wants competition to remain viable in an era where telematics and software are essential repair inputs. Another wants to keep repair-related access inside authenticated systems in the name of safety, cybersecurity, and brand integrity—while also protecting a lucrative service channel. A third bloc is tasked with balancing both realities while minimizing privacy harms.
Understanding the debate this way helps explain why the talking points can feel mismatched. One side is arguing about market access. Another is arguing about risk exposure. Another is arguing about enforceable, administrable rules.
The conflict isn’t only philosophical. It is structural: connected cars turn repair into a form of controlled digital access, and different institutions have different reasons to either open that access or keep it narrow.
1) Independent repair and the aftermarket: access as competition
Their core demand is straightforward: a statutory right to access repair and maintenance data and tools, including telematics-derived data, without being forced into OEM-controlled channels or fragmented, proprietary subscriptions. (CAR Coalition)
They frame the issue as one of competition and consumer choice. If only franchised dealers can reliably access repair-relevant telematics data, then drivers may have a “choice” in theory but not in practice.
From their perspective, the market failure is predictable: when a critical input to repair is controlled by a single entity, downstream markets—independent service, parts competition, and price pressure—can narrow even if the vehicle owner technically “owns” the car.
2) Automakers and franchised dealer systems: control as safety and brand integrity
Even in a world where many independent shops are highly professional, automakers have incentives to keep repair-related access inside authenticated systems they control. Dealer networks are also a major revenue channel, and the data stream can be an asset for ongoing services.
This argument has both a public-interest version and a business-interest version. The public-interest claim is that controlling access reduces the attack surface and prevents unsafe outcomes. The business-interest reality is that control of the diagnostic and authorization pathway can steer customers, pricing, and ongoing service relationships.
The tension is that both can be true at the same time—and policy has to account for both.
3) Regulators and consumer advocates: the uneasy middle
For regulators, the hardest part is designing access without creating a security free-for-all. For consumer advocates, the question is whether “owner access” becomes real in a system where the most valuable functions are mediated by remote services.
In practice, this bloc has to answer implementation questions that slogans can avoid: what does safe authentication look like, what constitutes “repair and maintenance,” what privacy protections are necessary, and how to prevent “compliance” that is technically present but practically unusable.
This is why enforcement architecture matters. If regulators can’t measure and enforce meaningful access, the policy goal can be defeated by design choices.
A modern car can be repaired with a wrench—but permission may still be required.
— — TheMurrow
The technical heart of the dispute: what counts as “access” in a connected car?
The REPAIR Act text makes the dispute explicit by addressing telematics systems and the data needed for repair and maintenance. (Congress.gov)
This is the point where policy meets systems engineering. A requirement that looks straightforward—provide repair data—can be implemented in ways that either enable genuine competition or preserve control.
So the core design problem is to define access in a way that is operationally meaningful: not just a theoretical right, but a practical capability that lets owners and their chosen shops complete repairs safely and efficiently.
Access can be equal on paper and unequal in practice
- Proprietary portals that require multiple subscriptions
- Authentication bottlenecks that delay repairs
- Limited data fields that omit calibration or configuration information
- Terms of service that prohibit common workflows
The policy challenge is not simply mandating access. It’s defining access so that it is usable, timely, and comparable to what franchised dealers receive—without eroding security.
This is also why enforcement matters: without accountability, “access” can become a compliance theater—nominally available, practically constrained.
Common choke points that can make “access” unusable
- ✓Proprietary portals that require multiple subscriptions
- ✓Authentication bottlenecks that delay repairs
- ✓Limited data fields that omit calibration or configuration information
- ✓Terms of service that prohibit common workflows
Why telematics makes the fight national, not local
That’s why the REPAIR Act’s federal structure matters. State-by-state fights can create a patchwork, but cloud-mediated diagnostics don’t respect state borders. A national standard is attractive to industry—if it is written on terms they can live with.
This is the core mismatch between older right-to-repair fights and the current one. In a manual-and-tools world, information can be distributed and used locally. In a telematics-and-cloud world, the manufacturer can centralize control and apply it everywhere at once.
A single federal rule can either constrain that centralization—or legitimize it by setting a floor that is easy to meet but hard to use.
Real-world stakes: what changes for drivers, shops, and cost
When repairs depend on software approvals and telematics data, the practical unit of consumer experience becomes friction. A job that would have been straightforward in a purely mechanical era can become a logistical and contractual challenge.
This friction affects the entire ecosystem. It shapes which shops can compete, how quickly vehicles return to the road, and whether price competition is real. It also changes ownership: what it means to “own” a product that is increasingly governed by remote systems.
The issue isn’t whether independent shops can do sophisticated work. Many already do. The issue is whether they can do it with timely, complete access—or whether the market is structured so that only OEM channels can finish the last mile of the repair.
Case study: the calibration problem after routine repairs
Nothing in the public debate suggests independent shops cannot do this work. The problem is whether they are allowed to do it efficiently, at scale, and without being structurally disadvantaged.
This is the lived reality of the shift from physical to digital constraints. The physical part can be replaced, but the system may still require a software-mediated handshake before it will function normally.
And because this involves safety-related systems, the consequences of restricted access aren’t just inconvenience—they can determine whether a vehicle’s driver-assistance features are restored promptly and correctly.
What “choice” looks like when data is gated
- Fewer shops able to complete a job end-to-end
- Longer wait times because authorizations or tools are delayed
- Less pricing competition when only one channel can finish the repair
The aftermarket argues that limited access threatens the independent repair sector’s ability to compete. (CAR Coalition)
This is how a policy dispute turns into a consumer outcome. Even if a driver is legally free to choose a shop, the effective choice can collapse when only one channel has dependable access to the permissions and data needed to close the repair.
Over time, that dynamic can reshape local service markets: fewer independent shops investing in capabilities they can’t reliably use, and more repair volume flowing through dealer channels by default.
Practical takeaways right now
- Will routine repairs require dealer-only authorizations?
- Does the vehicle rely on telematics for diagnostics and resets?
- Can an independent shop access the needed repair and maintenance functions?
- What ongoing subscriptions or portal fees are effectively built into ownership?
These questions are not political. They are basic due diligence for a product that increasingly behaves like a platform.
Questions to ask before buying or servicing a connected car
- ✓Will routine repairs require dealer-only authorizations?
- ✓Does the vehicle rely on telematics for diagnostics and resets?
- ✓Can an independent shop access the needed repair and maintenance functions?
- ✓What ongoing subscriptions or portal fees are effectively built into ownership?
Safety, cybersecurity, and privacy: the strongest objections and the hardest design work
The January 2026 subcommittee hearing captures this core divide: stakeholders argued over whether the REPAIR Act strengthens safety or creates new risks. (Repairer Driven News)
This is where the debate becomes hardest to resolve cleanly. Connected vehicles are legitimately part of a networked security environment. But a blanket claim that any access is too risky can also function as a veto over competition.
The policy task is to design access that is sufficiently controlled—authenticated, auditable, limited to repair and maintenance—without allowing security concerns to be used as a general-purpose rationale for market foreclosure.
Security risks are real—even if they’re sometimes overstated
The policy problem is to distinguish between:
- Repair-and-maintenance access needed for legitimate service
- Broader behavioral data access that could enable surveillance or misuse
The REPAIR Act’s emphasis is on repair and maintenance access. (Congress.gov) How regulators interpret and enforce those boundaries will matter as much as the text itself.
This distinction is critical because the phrase “vehicle data” can mean wildly different things depending on context. Repair access might require certain diagnostic and calibration data, but not necessarily a broad feed of location history or behavioral analytics. The closer policy gets to implementation, the more these boundaries determine whether consumers gain control—or lose privacy.
Why the FTC role matters
At the same time, FTC implementation would need to coordinate with safety and cybersecurity realities. Poorly designed access mandates could create vulnerabilities. Overly cautious rules could preserve the status quo under a new label.
That makes the FTC’s potential role a major signal in the bill: Congress is not only picking a side in an industry dispute. It is proposing a governance framework that would have to translate legal standards into operational rules.
Whether that framework becomes a real constraint on gatekeeping—or a procedural layer that changes little—would depend on how “access” is defined and enforced in practice.
What happens next: the broader market Congress is really regulating
Access to repair data sits upstream of:
- Independent service competition
- Aftermarket parts ecosystems
- Warranty and insurance dynamics
- Subscription feature models tied to software
- Fleet analytics and operational tooling
Congress rarely gets a clean chance to set the terms of platform competition before the platform becomes entrenched. Connected vehicles are approaching that point. The REPAIR Act is a bid to define the rules while the market is still malleable.
A critical detail is timing: H.R. 1566 was introduced February 25, 2025, the Senate companion S. 1379 is listed in April 2025, and the bill advanced out of a House Energy & Commerce subcommittee to the full committee as of February 10, 2026, according to the Auto Care Association. (Congress.gov; Auto Care Association)
The political question is whether Congress has the appetite to regulate data access in a way that both preserves security and prevents private tollbooths. The economic question is who gets to monetize the car’s data stream when repairs depend on it.
A reasonable reader can hold two thoughts at once: modern cars need strong cybersecurity, and owners should not lose functional control of their property because access is routed through a manufacturer’s server.
The REPAIR Act isn’t only about whether you can choose your mechanic. It’s about whether the connected-car economy will function like an open market or a controlled platform.
— — TheMurrow
1) What is the REPAIR Act?
2) Why is “telematics” central to right to repair now?
3) Who supports the REPAIR Act and why?
4) What are the main arguments against it?
5) Where is the bill in Congress as of early 2026?
6) What would the FTC do under the REPAIR Act?
7) What should car owners do now?
Frequently Asked Questions
What is the REPAIR Act?
The REPAIR Act is federal right-to-repair legislation focused on automobiles. The House version is H.R. 1566, introduced February 25, 2025; a Senate companion is S. 1379, listed as introduced in April 2025. It targets access to repair and maintenance data, tools, and software, including telematics-related access. (Congress.gov)
Why is “telematics” central to right to repair now?
Modern vehicles transmit vehicle-generated data through telematics systems and embedded software. Diagnostics, calibrations, and parts pairing can depend on remote authorizations and software locks, shifting leverage from physical tools to cloud-mediated data access. (Congress.gov; CRS via Congress.gov)
Who supports the REPAIR Act and why?
Independent repair shops, aftermarket parts makers, and groups like the Auto Care Association and the CAR Coalition argue statutory access is needed for real consumer choice and competition, especially if OEM channels otherwise dominate connected-vehicle service. (CAR Coalition; Auto Care Association)
What are the main arguments against it?
Opponents cite safety, cybersecurity, and privacy risks—arguing broader telematics access could increase tampering or data misuse. These concerns were debated during a January 2026 House subcommittee hearing. (Repairer Driven News)
Where is the bill in Congress as of early 2026?
The Auto Care Association reported H.R. 1566 was forwarded by a House Energy & Commerce subcommittee to the full committee as of February 10, 2026, following a January 2026 subcommittee hearing. (Auto Care Association; Repairer Driven News)
What would the FTC do under the REPAIR Act?
The bill contemplates FTC involvement in oversight and includes reporting to Congress after enactment, signaling an enforcement structure. The real impact would depend on how rules define usable access while addressing security and privacy. (Congress.gov)















