The Safe and Private Rides Act requires transportation network companies (TNCs) to register any driver-installed camera that records passengers, notify riders about those cameras, and give riders a clear, easily accessible option in the company app to opt out of being matched with vehicles that have such cameras. The bill also restricts when companies may retain or transfer passenger recordings—only permitting retention for criminal reporting, insurance purposes, or to determine compliance with the company’s terms of service—and requires a passenger-facing reporting mechanism for breaches.
This is an operational bill with privacy and product-design consequences: platforms must change onboarding and app UI, maintain a camera registry, and build complaint-handling workflows. It also creates a civil-enforcement path via the Federal Trade Commission by treating violations as unfair or deceptive acts, while shielding companies from liability for drivers’ noncompliance if the company itself followed the statute’s registration, notice, and opt-out requirements.
At a Glance
What It Does
The bill forces TNCs to require drivers to register any in‑vehicle camera that records passengers, notify customers of registered cameras, and offer an opt-out for riders via a clearly displayed app control that is independent of terms of service. It bans retention or transfer of passenger recordings except for criminal reports, insurance, or TOS‑compliance purposes, and assigns enforcement authority to the FTC under its unfair or deceptive acts framework.
Who It Affects
Directly affects transportation network companies and their app/product teams, drivers who install dashcams or interior cameras, passengers who use ride-hailing services, insurers and law enforcement that currently rely on footage, and the FTC which will enforce compliance. App developers and customer-support operations must implement new UI, registry, and reporting flows.
Why It Matters
This bill creates a federal consumer‑privacy rule specific to ride-hailing that requires affirmative rider control (an opt-out) and narrows permissible uses of in‑car recordings. For compliance officers and product teams, it sets clear operational requirements and a practical safe-harbor for companies that follow them, while giving the FTC a ready-made enforcement lever.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Act establishes a straightforward compliance regime for cameras that record passengers in vehicles used by transportation network companies. First, every driver who uses such a camera must register it with their TNC so the company can compile a list of vehicles with cameras.
The company must then notify passengers about any registered camera connected to their ride and present a conspicuous opportunity in the app to opt out of being matched with vehicles that include passenger‑facing recording. The statute requires the opt-out control to be accessible, revocable, and independent from a user’s acceptance of terms of service.
On data handling, the bill tightly limits when a recording of a passenger can be retained or transferred: only to report criminal activity, for insurance claims, or to assess compliance with the TNC’s own terms of service. The company must provide a mechanism for passengers to report being recorded without notice or being matched with a camera-equipped vehicle after they opted out.
That complaint process creates an operational requirement for customer support and recordkeeping.Liability and enforcement are bifurcated. If a company implements the registration, notice, opt-out, retention limits, and reporting mechanism as required, the bill bars civil liability against the company for a driver’s noncompliant actions.
At the same time, violations are treated as unfair or deceptive acts enforceable by the Federal Trade Commission with the same remedies and procedures available under the FTC Act. The Act takes effect 180 days after enactment.Finally, the text defines the covered entities and vehicles: it targets entities that use a digital network to connect customers and drivers and excludes noncommercial carpool/vanpool arrangements and certain dedicated services.
The definition of a motor vehicle is the common four‑wheeled, public‑road vehicle. Those definitions delimit the bill’s reach and will be important when applying the statute to edge cases like shared microtransit or nontraditional passenger services.
The Five Things You Need to Know
TNCs must require drivers to register any camera in their vehicle that records video images of passengers and notify passengers about each registered camera.
The app must display a clear, prominent opt-out control—independent of the company’s terms of service—and allow riders to revoke consent through an accessible, easily navigable mechanism.
TNCs may not retain or transfer passenger recordings except to report criminal activity, for insurance purposes, or to determine compliance with the company’s terms of service.
Violations are enforced by the Federal Trade Commission as unfair or deceptive acts under the FTC Act, giving the FTC full investigatory and remedial powers.
The bill bars liability for a TNC that complies with the registration, notice, opt-out, retention, and reporting requirements if an affiliated driver nevertheless violates those rules; the statute becomes effective 180 days after enactment.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Names the measure the 'Safe and Private Rides Act.' This is a housekeeping provision but signals the bill’s dual focus on passenger privacy and ride safety.
Driver camera registry, passenger notice, and app opt-out
Requires TNCs to collect registration information from drivers for any camera that records passengers, to notify each passenger of registered cameras, and to implement a clear, prominent opt-out on the company application. Practically, that means platforms must build or extend driver‑onboarding workflows to capture camera presence, surface a visible notice to riders during booking or in-profile settings, and provide a matching filter so riders who opt out aren’t matched to camera-equipped vehicles.
Limits on recording retention and passenger reporting mechanics
Prohibits retaining or transferring passenger recordings except for three narrow purposes: reporting criminal activity, insurance claims, or determining compliance with the TNC’s terms. The bill also requires a passenger-facing mechanism to report being recorded without notice or being matched to a camera vehicle after opting out. Subsection (b) sets the opt‑out standards: revocable consent, prominent placement in app settings, independence from terms of service acceptance, and only inferring opt-out from a clear affirmative action by the user. These provisions create both technical and policy requirements for data minimization and customer support workflows.
Limitation of liability for compliant companies
Grants TNCs a statutory safe harbor: if a company has complied with the registration, notice, opt-out, retention, and reporting obligations, the statute bars liability for an affiliated driver’s subsequent violations. That shifts the legal risk calculus: companies get a compliance-based shield, while drivers and possibly insurers remain primary actors for misconduct that occurs despite company processes.
FTC enforcement and remedies
Treats violations as unfair or deceptive acts under the Federal Trade Commission Act and gives the FTC the same investigatory and remedial powers it already uses for consumer protection enforcement. The provision also makes clear that the FTC’s other authorities are preserved. For enforcement teams, this converts the statute’s requirements into an FTC compliance and enforcement playbook rather than a new private right of action.
Effective date and definitions
Sets the effective date at 180 days after enactment and defines key terms: 'Commission' (FTC), 'motor vehicle' (four‑wheeled public‑road vehicles), and 'transportation network company' (digital networks connecting customers to drivers), with specific exclusions for noncommercial carpools and certain dedicated services. These definitions determine which services and devices fall inside the statute and which do not.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Riders concerned about in‑car surveillance: gain explicit notice and a concrete opt-out mechanism, giving them reliable control over whether they enter vehicles that record passengers.
- Privacy and consumer‑protection teams: receive a clear statutory standard to enforce and advocate for; the law narrows permissible uses of footage and demands data‑minimizing retention rules.
- Compliant TNCs and their legal teams: obtain a statutory safe harbor from platform liability for driver misconduct if the company implements the required registry, notices, opt-out and reporting mechanisms.
- FT C and regulators: benefit from a bright‑line mandate that converts camera‑in‑vehicle practices into an enforceable unfair or deceptive acts framework, simplifying oversight.
- App‑design and product teams at TNCs: gain clarity about required UI elements and opt-out behavior, allowing them to design standardized controls across platforms.
Who Bears the Cost
- Transportation network companies: must invest in driver onboarding, maintain a camera registry, change booking/matching logic, update privacy policies, and stand up complaint handling and auditing—creating engineering and operational costs.
- Drivers who rely on cameras for safety or evidence: may lose the ability to record passengers or will face reduced ridematch opportunities if many riders opt out, and may need to disclose devices and follow company policies.
- Customer support and compliance teams: will need to process opt-out preferences, investigate reports of unnotified recording, and maintain logs to preserve the liability safe harbor, increasing staffing and training burdens.
- Insurers and plaintiffs: will face restricted access to recordings that historically were used for claims and litigation, because the bill limits retention and transfer to narrow categories.
- FTC and enforcement resources: while empowered, the FTC will face additional casework to adjudicate compliance disputes and to assess whether companies’ opt-out mechanisms meet the statute’s standards.
Key Issues
The Core Tension
The central tension is between empowering passenger privacy through an affirmative, revocable opt-out and preserving the safety, evidence‑gathering, and anti‑fraud functions that in‑vehicle cameras provide to drivers and platforms. Protecting riders by limiting recordings and retention can reduce available evidence for safety incidents and insurance claims; conversely, preserving broad recording powers undermines passenger privacy. The statute tries to thread that needle with narrow retention exceptions and a company safe harbor, but doing so shifts accountability toward drivers and regulators rather than platforms—creating a trade-off between privacy protection and practical enforceability.
The bill draws a bright line around notice, opt-out, and limited retention, but several implementation details are unresolved and create practical risks. First, the statute says drivers must ‘register’ cameras with the TNC but does not specify required registration data, verification procedures, or how companies should detect undeclared cameras.
That gap creates a compliance burden: platforms must choose whether to rely on driver self‑attestation, periodic audits, or technical detection—each choice has costs and imperfect accuracy. Second, the retention carve-outs are narrow but ambiguous in practice: 'insurance purposes' and 'to determine compliance with terms of service' can be litigated, and the bill does not set retention windows, access controls, or security standards for stored footage.
The liability safe harbor reduces platform exposure but shifts accountability. If companies are insulated from suits when they followed the statute, injured passengers may have limited remedies against platforms and must pursue drivers directly—who may lack resources.
The FTC enforcement route fills that gap to a degree, but FTC actions typically seek broad injunctive relief and penalties rather than individual damages. Finally, the opt-out requirement interacts awkwardly with matching algorithms: platforms must prevent matches to camera vehicles for opted-out riders, yet the bill does not address whether drivers can condition acceptance of rides on knowing passenger opt-out status or whether drivers can refuse riders who opt out—raising potential discrimination and operational friction.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.