Uber and Lyft Sue NYC Over the Deactivation Law

Last reviewed: June 12, 2026 — updated after attorney review of the enacted text of Local Law 52.

Key Takeaways

• Uber sued New York City in Manhattan federal court this week to block Local Law 52 of 2026 before its July 28 effective date. Lyft filed its own suit roughly 24 hours later, according to Reuters.
• The law bars large rideshare companies from deactivating drivers without “just cause” or a “bona fide economic reason” and requires 14 days’ notice before most deactivations. The Council passed it in December; then-Mayor Adams vetoed it on New Year’s Eve, and the Council overrode the veto 46-5 on January 29.
• A deactivated driver can go to court, not just to an agency. The law creates a private right of action alongside the DCWP complaint process, and a court must award a winning driver attorney’s fees — the engine that makes small cases worth a lawyer’s time.
• The burden of proof sits on the company. Uber or Lyft must prove just cause or a bona fide economic reason by a preponderance of the evidence. The driver does not have to prove the deactivation was wrong.
• New drivers get nothing for the first 30 days. The protections kick in only after a 30-calendar-day probation period that starts the first day you drive.
• Immediate removal is still allowed for account sharing, fraud, and egregious misconduct — violence, sexual harassment or assault, and discrimination are written into the carve-out. Even then, the company owes the driver a deactivation notice within 5 days.
• Uber and Lyft claim free-speech and due-process violations under the U.S. and New York constitutions. Uber calls the law “reckless”; Lyft calls it “hazardous.”
• For drivers, this is the closest thing to employment-style job protection app workers have ever gotten in New York, without anyone conceding employee status. If you were deactivated since 2019, start assembling your records now.
• For injured passengers, the safety framing cuts the other way. The law already lets companies remove dangerous drivers immediately. If a platform keeps a driver it had grounds to remove and that driver hurts someone, the company can’t blame the statute for its own retention choice.
• As of June 1, Uber faced 3,571 lawsuits alleging driver sexual misconduct in consolidated federal proceedings in San Francisco, according to Insurance Journal.

Uber went to Manhattan federal court this week to kill New York City’s driver deactivation law before it ever takes effect. Lyft followed a day later. The filings set up the biggest gig-economy fight in New York since the Taxi and Limousine Commission’s minimum pay rules, and the July 28 effective date means a judge will probably have to say something meaningful about it within the next six weeks.

I have an unusual seat for this one. My office represents gig workers fighting misclassification and represents companies and carriers defending injury claims. Both sides of this lawsuit are saying something true. Both are also overstating their case. Here is what the law actually does, what the complaints actually claim, and what drivers and injured passengers should be doing while the lawyers fight.

Already deactivated? This article is about the lawsuit. If Uber or Lyft has actually cut off your account, start with our driver-facing guide instead: Deactivated by Uber or Lyft in New York? Your Rights. It walks through when you can sue, DCWP vs. court, and what to save the day you lose access.

What happened, exactly

According to Insurance Journal’s June 11 report, Uber filed its complaint late Tuesday night in Manhattan federal court, asking a judge to block Local Law 52 of 2026 before its July 28 effective date. The company’s statement went straight at the Council:

“We are suing New York City to block a reckless new law that seeks to strip our ability to immediately remove potentially dangerous drivers and fraudsters from our platform, creating an immediate threat to public safety.”

Reuters reported that Lyft filed its own suit in the same courthouse about 24 hours later, calling the law “hazardous.” Both companies claim the law violates their free-speech and due-process rights under the U.S. and New York constitutions, and both say it threatens irreparable harm to their reputation and goodwill while keeping unsafe drivers on the road. A spokesman for the City’s law department said it is reviewing the complaint.

Council Speaker Julie Menin and Council Member Shekar Krishnan, the bill’s lead sponsor, answered with a joint statement: “This Council stands with workers and will continue to fight to ensure all app-based drivers have basic due process protections, so they are not unfairly deprived of their livelihoods without notice or an opportunity to appeal.”

So that’s the fight. Now the part most of the coverage skips: what the law actually says.

What Local Law 52 actually does

The law began life as Int. 0276-2024 in the City Council, which passed it in December 2025. Then-Mayor Eric Adams vetoed the bill on December 31 — in the final hours of his mayoralty — and the Council overrode the veto 46-5 on January 29, 2026, per amNY. It became Local Law 52 the same day. The law applies to high-volume for-hire vehicle services, which in practice means Uber and Lyft.

The core rules:

• A covered company may not deactivate a driver without just cause or a bona fide economic reason.
• Most deactivations require 14 days’ advance written notice.
• Drivers get a complaint process through the Department of Consumer and Worker Protection — and, separately, the right to file a civil action in court, with mandatory attorney’s fees if they win.
• The notice and just-cause requirements do not apply to deactivations for account sharing, fraud, or alleged egregious misconduct. The law’s text reaches violence, sexual harassment or assault, and discrimination. Even in those cases, the company must send a deactivation notice within 5 days.
• Protections begin only after a 30-calendar-day probation period that starts the first day a driver performs driving services.

Uber’s complaint also argues the law could force it to revisit deactivation decisions reaching back to 2019, per Insurance Journal. That is why every driver deactivated since then should be paying attention to this case, not just current drivers.

The employment-case playbook inside Local Law 52

I sat down with the enacted text after the complaints hit the docket, because coverage of new statutes is reliably wrong about the mechanics, and the mechanics are where cases get won. Six provisions stood out. Put them together and you get something none of the headlines captured: a deactivation case under this law is built like an employment case. The Council never used the word “employee,” but it borrowed the entire architecture.

First, a deactivated driver can sue. The law gives drivers two routes: file a complaint with the Department of Consumer and Worker Protection, or bring a civil action in court. That second route is a private right of action, and it changes everything about who enforces this law. An agency-only statute is enforced as fast and as often as the agency’s budget allows. A statute with a private right of action is enforced by every lawyer willing to take the case. Courts can order compensatory, injunctive, and declaratory relief — the enacted text spells out reinstatement and back pay.

Second, the lawsuit comes with legal fees. The text says the court shall order the company to pay a prevailing driver’s reasonable attorneys’ fees and costs. Shall, not may. If you’ve never litigated a fee-shifting statute, here is why that one word matters so much. A deactivated driver’s damages are lost earnings — real money to the driver, but usually five figures, which is too small for a contingency practice to chase against a defendant with Uber’s litigation budget. Fee-shifting fixes the math. It is the same engine that makes NYSHRL discrimination cases and wage-and-hour cases economically viable: the lawyer’s compensation comes from the statute, not from a slice of a small recovery, so a $20,000 deactivation case can get the same quality of counsel as a $2 million one. Companies settle fee-shifting cases differently for exactly this reason. Every month of fighting grows the fee exposure faster than the underlying claim.

Third, the company has to prove it was right. The statute puts the burden on the rideshare service to prove just cause or a bona fide economic reason by a preponderance of the evidence. The driver does not have to prove the deactivation was wrongful; the company has to prove it wasn’t. This is the provision Uber’s complaint hates most — the company accuses the city of setting up “kangaroo” proceedings in which judges, arbitrators, and DCWP officials must presume deactivations unjust while Uber proves otherwise, per Bloomberg Government’s report on the complaint. Here is what the complaint doesn’t mention: putting the burden on the employer is how just-cause discipline has worked in American labor arbitration for the better part of a century. In every union grievance over a termination, the employer carries the burden. Calling that a kangaroo court indicts every collective bargaining agreement in the country.

Fourth, just cause generally requires progressive discipline. Outside the egregious-misconduct carve-out, the company can’t go from zero to deactivation. It needs a discipline trail, and the law requires the discipline policy itself to be set out in a single written document covering the types of misconduct, the performance standards, and the procedures. Think about what app deactivations actually look like today: for most drivers, the first “warning” they ever receive is the deactivation. No written policy they ever saw, no documented intermediate steps, no chance to correct. Under this law, that history is not just unfair — it’s a failure of proof, and the burden is on the company.

Fifth, even “egregious” deactivations generate paper, fast. The carve-out lets a company remove a driver immediately for alleged violence, harassment, fraud, and the rest. But within 5 days it must send a notice of deactivation, and the driver has the right to dispute it. That 5-day clock matters more than it looks. It forces the company to commit to a stated reason while the facts are fresh, in writing, before anyone has lawyered the file. In litigation, the early written reason is the one the company is stuck with.

Sixth — and this is the gap drivers need to know about — the first 30 days are unprotected. The law defines a probation period of 30 calendar days starting the first day a driver performs driving services. During that window, none of these protections apply. A new driver deactivated on day 29 has no just-cause claim, no notice right, nothing. If you just started driving, the law does not cover you yet, and nothing about the lawsuit changes that.

So what should a driver actually do with this? Keep everything. The deactivation notice is now a legal document: it has to state the company’s reason, and that stated reason is what the company will be held to. Screenshot it, along with every in-app warning, rating dispute, and support chat that came before it — under a progressive-discipline regime, the absence of prior warnings is your evidence. On the DCWP-or-court choice, there’s no universal answer. The agency route costs nothing and DCWP can order reinstatement and back pay; the court route adds mandatory fees and puts a judge rather than an agency on the burden question. Which one fits depends on your damages, your timeline, and whether your deactivation overlaps with something bigger, like discrimination or retaliation for complaining about pay. Those overlapping claims exist under current law and don’t wait for July 28 — the just-cause concept here is the cousin of what we see in wrongful-termination cases on Long Island, where at-will employees only get traction when the firing crosses into discrimination or retaliation. Drivers under Local Law 52 will get more than most W-2 employees in New York ever do.

A lot of the city’s drivers work in Spanish, so one more pointer: deactivation after you complain about pay, safety, or working conditions can be retaliation under existing law, separate from anything in Local Law 52. Publicamos sobre esto en español — our guide to represalias laborales en Nueva York walks through how those claims work.

And because my office defends companies too, the defense-side note, offered without charge: if you run a platform or any business that terminates contractor relationships at volume, the progressive-discipline infrastructure has to exist before July 28, not after the first complaint. A written discipline policy, intermediate steps that actually get used, and a file documenting them — without that, every non-egregious deactivation is a case you carry the burden on and pay both sides’ lawyers for. Hospitals learned this with physician credentialing decades ago. The platforms have seven weeks.

What the law says vs. what the companies claim

Read Uber’s statement again. It says the law “seeks to strip our ability to immediately remove potentially dangerous drivers.” Then read the statute’s carve-out, which expressly permits immediate deactivation for alleged violence, sexual harassment or assault, discrimination, fraud, and account sharing. Those two things are in real tension, and the gap between them is where this case will be fought.

The driver side: the closest thing to job rights app workers have ever gotten here

Here is why this law matters more than its modest mechanics suggest. A just-cause standard is the spine of union contracts and civil-service protection. Employees at will don’t even get it. And New York’s app drivers are not employees at all. They are independent contractors, which under current law means a platform can cut off a driver’s income tonight, by automated decision, with no hearing and no stated reason that any neutral party ever reviews.

Local Law 52 would change that without touching classification. That is its political genius and its legal vulnerability at the same time. The Council didn’t declare drivers employees; it regulated the companies’ conduct toward them. Drivers get notice, a reason, and an appeal. They still don’t get unemployment insurance when deactivated, or workers’ comp when injured. That bundle turns on the employee question I covered at length in my analysis of the DOL’s 2026 independent-contractor rule and New York’s misclassification tests.

The two fights feed each other, though. Every procedural right drivers win as contractors becomes evidence in the classification debate: if the city can require just cause, and the platform controls pay, routes, and discipline, the “independent business” story gets harder to tell with a straight face. New York’s Attorney General already extracted $328 million from Uber and Lyft in 2023 over driver pay practices. The TLC’s minimum pay rules survived Lyft’s court challenge back in 2019 (Lyft sued; the rule stood). The deactivation law is the next brick in that wall, and the platforms know it. That, I suspect, is the deeper reason these complaints got filed seven weeks before the effective date rather than after a few enforcement actions. For the broader 2026 picture, see my guide to employment-law changes for gig workers and independent contractors.

One more wrinkle worth flagging: the law’s egregious-misconduct carve-out includes discrimination by drivers. But drivers also experience the other direction: riders and platforms making decisions infected by bias. Deactivation data has never been transparent enough to test that. A notice-and-appeal regime would generate, for the first time, a paper record of who gets deactivated and why. If you believe your deactivation involved discrimination, that is a separate claim from the deactivation itself; our employment discrimination practice page explains how those cases work in New York.

Deactivated since 2019? Do these five things now

Uber’s own complaint says the law could force a second look at deactivations going back to 2019, according to Insurance Journal. Nobody knows yet how reinstatement review would work in practice, and the lawsuit may delay or kill it. Prepare anyway. The driver who shows up with records beats the driver who shows up with a story.

The passenger side: Uber’s safety argument cuts both ways

Now the part of this story I find genuinely interesting as an injury lawyer, because almost nobody covering the lawsuit has noticed it.

Uber’s entire public case is built on safety: the law, it says, threatens its ability to remove dangerous drivers. Set aside that the statute’s carve-out already permits immediate removal for violence, assault, harassment, fraud, and discrimination. Focus on what the companies are conceding by making the argument at all: that they possess complaint data identifying potentially dangerous drivers, and that acting on it fast is essential to passenger safety.

That concession has consequences in civil litigation. When a rideshare driver injures a passenger — in a crash, or worse — one of the theories plaintiffs’ lawyers reach for is negligent hiring, retention, or supervision: the company knew or should have known the driver posed a risk and kept them on the platform anyway. Classification doesn’t shield this theory; it runs against the company’s own conduct, not the driver’s employment status, which is exactly why it matters in rideshare injury cases where the platforms otherwise hide behind the contractor label.

Local Law 52 makes that theory sharper, not duller. After July 28 (if the law survives), a company that keeps a driver despite complaints of violence or harassment cannot blame the statute; the statute explicitly let it remove that driver immediately. The retention decision is the company’s alone. And in any case filed after a deactivation regime with documented notice and appeals exists, discovery into what the platform knew, when, and what it did becomes far more concrete. The 3,571 pending sexual-misconduct suits consolidated in San Francisco federal court show how much of this litigation already exists; the first bellwether trials in mass programs like the social-media MDL show how consolidated proceedings eventually price this conduct.

To be fair to the companies, there is a real operational concern under the surface of the overstated press release. The carve-out covers alleged egregious misconduct, but lawyers will fight about what qualifies. Is a pattern of 1-star ratings with vague comments “egregious”? A single uncorroborated complaint? If platforms err toward keeping drivers to avoid DCWP appeals, and one of those drivers hurts someone, the company faces the negligent-retention suit. If they err toward removing drivers, they face the deactivation claim. Regulated industries live with exactly this squeeze all the time; ask any hospital that has handled a physician-credentialing fight. But it is a genuine cost, and pretending otherwise would be spin in the other direction.

The practitioner’s view: what to watch before July 28

For the lawyers following along, the next six weeks are about preliminary-injunction practice. To stop the law before its effective date, the companies must show a likelihood of success on the merits, irreparable harm absent an injunction, and that the balance of equities and public interest favor relief. Their complaints have already previewed the irreparable-harm theory: damage to brand, goodwill, and safety that money can’t later fix.

On the merits, a few observations — offered as standard doctrine, not predictions:

Due process is the steep climb. Courts have reviewed ordinary economic regulation with strong deference for nearly a century. A law telling a large company what process it owes before terminating a contractor relationship sits comfortably in the category of things legislatures regulate. The companies will try to frame it as something more: compelled association with dangerous individuals, and retroactive interference with settled decisions (that 2019 look-back is their best fact). The retroactivity piece is where I’d expect the due-process count to have its most serious bite.

The First Amendment count is the wildcard. Uber says requiring disclosure of rider feedback, ratings, and grievances to drivers under review compels speech and exposes riders to retaliation. Compelled commercial disclosure usually gets reviewed leniently when the required disclosure is factual and uncontroversial; whether complaint files fit that box is a fresh question. Novel doesn’t mean weak. It means unpredictable, and unpredictability is sometimes all you need for a preliminary injunction.

The city’s TNC litigation record is good but not perfect. The TLC’s driver minimum-pay rules survived Lyft’s 2019 challenge. The for-hire vehicle license cap was successfully defended at the initial stage, per the New York Taxi Workers Alliance. But the cruising cap was struck down in state court in December 2019 as arbitrary and capricious. Those were mostly state-law Article 78 fights; this one is federal and constitutional, so the track record is suggestive rather than controlling. Still: when New York City writes TNC rules carefully, it has tended to keep them.

Both sides are right about something

Because I work both sides of this street, let me say plainly what each side has earned.

The drivers and the Council are right that the current system is indefensible as process. A person whose full-time income depends on an app can lose it overnight, by automated decision, with no explanation a neutral ever reviews. We would not accept that for a taxi medallion, a liquor license, or a TLC license itself — all of which come with revocation procedures. “Independent contractor” describes a tax and benefits classification; it was never supposed to mean “no process of any kind, ever.”

The companies are right that complaint-driven removal decisions are genuinely hard, that some of what makes platforms safer than street hails is the speed of removal, and that a 2019 look-back imposes real costs on decisions made under the old rules. The 3,571 pending misconduct suits are the strongest fact in their brief, even though — irony fully noted — those suits mostly allege the companies did too little about dangerous drivers, not too much.

What neither side will say: this entire fight exists because New York keeps regulating around the classification question instead of answering it. Minimum pay rules, the AG’s wage settlement, now just-cause deactivation — each one grafts an employment-style protection onto contractor status. At some point the graft becomes the tree. That question is being litigated in a dozen forums right now, and it is the subject of our flagship misclassification analysis, which I’d point you to whether you drive for the apps or run a business that uses contractors.

Frequently Asked Questions

Can Uber deactivate drivers without warning in New York right now?

Yes. Until Local Law 52 takes effect (scheduled for July 28, 2026, unless a federal court blocks it), New York rideshare drivers are independent contractors with no statutory right to notice, a stated reason, or an appeal before deactivation. The new law would require just cause or a bona fide economic reason plus 14 days’ notice for most deactivations, with a complaint process through the Department of Consumer and Worker Protection or a lawsuit in court — after a 30-day probation period for new drivers.

What is NYC Local Law 52 of 2026?

It is the driver deactivation law the City Council enacted on January 29, 2026, by overriding then-Mayor Adams’ veto 46-5 (introduced as Int. 0276-2024). It bars high-volume for-hire vehicle services (Uber and Lyft) from deactivating drivers without just cause or a bona fide economic reason, requires 14 days’ advance notice in most cases, and lets a deactivated driver complain to DCWP or sue in court. Immediate deactivation remains allowed for account sharing, fraud, and alleged egregious misconduct including violence, sexual harassment or assault, and discrimination — followed by a written notice within 5 days.

Why are Uber and Lyft suing New York City over the deactivation law?

Both companies filed suits in Manhattan federal court in June 2026 claiming the law violates their free-speech and due-process rights under the U.S. and New York constitutions. Uber says the law strips its ability to immediately remove dangerous drivers and that disclosing rider complaints to drivers under review compels speech and risks retaliation; it also objects to revisiting deactivations going back to 2019. The city’s law department says it is reviewing the complaints.

I was deactivated by Uber or Lyft — do I have any rights today?

You may. Even before Local Law 52, a deactivation that involves discrimination, retaliation for protected activity, or unpaid earnings can support claims under existing law. New York’s Attorney General recovered $328 million from Uber and Lyft in 2023 over driver pay practices. And if the new law survives the court challenge, deactivations since 2019 may get a second look. Preserve your deactivation notices, trip data, and earnings records now, and get legal advice about your specific situation.

Can I sue Uber or Lyft for deactivating me in NYC?

Once Local Law 52 takes effect (July 28, 2026, unless a court blocks it), yes. The law gives deactivated drivers a private right of action — you can file a civil lawsuit instead of, or in addition to, a DCWP complaint. A court can order reinstatement, back pay, and other relief, and the company must pay a winning driver’s reasonable attorney’s fees and costs. Deactivations involving discrimination, retaliation, or unpaid wages can support claims under existing law even before the effective date.

Can I sue Uber for deactivating me in NYC?

Once Local Law 52 takes effect (July 28, 2026, unless a court blocks it), yes — the law gives deactivated New York drivers a private right of action to sue in court, with reinstatement, back pay, and mandatory attorney’s fees if you win. But the right answer for your situation depends on your facts, your damages, and whether discrimination, retaliation, or unpaid wages are mixed in (those claims exist today, before the effective date). If you have actually been deactivated, our Uber and Lyft driver deactivation rights guide walks through suing vs. a DCWP complaint and how to choose.

What do I do if Uber or Lyft deactivated my account?

Preserve everything before you lose access: screenshot the deactivation message and every prior warning, request your driver data (trips, ratings, complaint flags), pull at least 12 months of earnings, and write down the trigger event with dates. Do not argue your case in the in-app support chat — preserve, don’t perform. Our step-by-step driver deactivation guide covers the day-one checklist and your options under Local Law 52.

Does Local Law 52 cover new drivers?

Not right away. The law has a 30-calendar-day probation period that starts the first day a driver performs driving services. During those 30 days, the just-cause, notice, and appeal protections do not apply. A driver deactivated during probation has no claim under this law, though other laws (anti-discrimination, wage protections) still apply from day one.

Who has to prove the deactivation was justified?

The company. Local Law 52 puts the burden on the rideshare service to prove just cause or a bona fide economic reason by a preponderance of the evidence — the driver does not have to prove the deactivation was wrongful. This burden allocation is the centerpiece of Uber’s objection to the law; its complaint calls the resulting process “kangaroo” proceedings. It is also how just-cause termination cases have always worked in labor arbitration.

Can I sue Uber if a dangerous driver injures me as a passenger?

You can pursue claims against the driver and, on the right facts, against the company, including negligent hiring, retention, or supervision if the platform kept a driver it knew or should have known was dangerous. New York requires $1.25 million in liability coverage while a rideshare trip is active. Note that Local Law 52 expressly permits immediate removal of drivers for violence, assault, and harassment, so the companies cannot point to the statute to excuse keeping a dangerous driver. Every case turns on its facts; values differ widely.

Will the deactivation law take effect on July 28, 2026?

Unknown. Expect the companies to seek a preliminary injunction before the effective date, which requires showing a likelihood of success on the merits and irreparable harm. A court could block the law entirely, block parts of it (the 2019 look-back is the most vulnerable piece), or let it take effect while the case proceeds. We will update this article as the docket moves.

Talk to us — drivers, passengers, and counsel

If you’ve actually been deactivated, start here: our evergreen Uber/Lyft Driver Deactivation Rights guide covers when you can sue, DCWP vs. court, the 30-day probation gap, and exactly what to save the day you lose access.

If you drive for the apps: deactivated since 2019, or worried about a pending complaint against your account? Bring your records. We represent gig workers in deactivation, misclassification, discrimination, and wage matters across Long Island and the five boroughs. The consultation is free: (516) 750-0595.

If you were hurt in a rideshare: whether you were a passenger, a pedestrian, or another driver, the insurance answer depends on facts you may not know yet, and the $1.25 million policy exists whether or not the carrier mentions it. Free consultation, no fee unless we recover: (516) 750-0595 or contact our office online.

For attorneys: we accept per-diem, appellate, and co-counsel engagements in rideshare injury, no-fault, and employment matters, including negligent-retention theories against TNC defendants and coverage fights across the three-tier TNC insurance structure. If Local Law 52 survives, the deactivation paper trail will change discovery in these cases — happy to compare notes. Attorney inquiries answered same day: (516) 750-0595.

This article reports on litigation filed the week of June 8, 2026, and will be updated as the cases develop. Facts drawn from Insurance Journal, Reuters, and the New York City Council’s legislative record. Nothing here is legal advice; every case differs.