Uber's own deactivation policy lists a driver being reported for a crash during a trip as one of the reasons an account can lose access, under its "unsafe driving" category - whether or not you were at fault.
We have not reviewed Lyft's equivalent policy with the same level of detail, so we're not making Lyft-specific claims here.
What Uber's policy actually says
Uber's published deactivation policy lists reports that a driver was involved in a crash during a trip as a factor that can trigger a safety review. Accounts are commonly placed on a temporary hold while that review happens, and Uber may ask for proof the vehicle has been repaired before reinstating you.
Some widely repeated claims - like a fixed number of accidents in a fixed number of years automatically triggering deactivation - are not things we found in Uber's own published policy. We're leaving them out rather than repeating them as fact.
Fault matters
Uber's review process gives weight to whether you were at fault. Drivers who weren't are less likely to face permanent removal, though a temporary hold during the investigation is still common either way.
If it happens to you
Uber publishes an in-app appeal process with a stated seven-business-day decision window.
Lyft
We have not sourced an equivalent Lyft policy with the same specificity, so we're not going to tell you what to expect there yet.
Do I have to report an accident to Uber or Lyft? →
Uber's deactivation policy is national - but what your coverage pays during a trip still depends on your state. Open your state and jump straight to what we have verified.
Still have questions?
Tell us what happened. If we do not already have an answer, your question may help us build one.
Ask ClaimedUp →