Blog

California settles with Lyft for $1.8 million over browser-based opt-out

The California Attorney General settled with Lyft for $1.8 million over the lack of a simple in-app opt-out. What this means for app-only services.

· By

A hand holds a smartphone on a pavement, a finger hovering above the screen, while a car drives away in the background.
California settled with Lyft for $1.8 million because the opt-out was not in the app itself but in a browser.Image: IamVera.ai — original editorial illustration

On 29 October 2026 the California Attorney General settled with Lyft for $1.8 million because the app offered no simple opt-out from the sale or sharing of personal data but sent users to a browser. The takeaway: anyone delivering a service solely through an app must offer the privacy choice natively in that app, with minimal steps and without unnecessary identity checks.

The announcement is not a large penalty by the standards of privacy enforcement. In our analysis, its significance lies in the practical point emphasized by the state: a formally available right may be difficult to exercise when the process is burdensome. In our assessment, the case is relevant to organisations that serve customers mainly through a mobile app because it highlights the risk of separating a privacy choice from the main service channel.

What exactly did the California Attorney General decide in the Lyft case?

On 29 October 2026 Attorney General Rob Bonta announced a settlement of $1.8 million in civil penalties with Lyft, over alleged violations of the California Consumer Privacy Act (CCPA) and the Unfair Competition Law. According to the official announcement from the Office of the Attorney General, Lyft must additionally offer an in-app opt-out and a clear consumer notice. Importantly, the accompanying proposed judgment states that Lyft admits no liability or facts. The court has therefore not found the allegations proven.

Why did the state consider Lyft's browser-based opt-out insufficient?

In the complaint by the State of California against Lyft, the Office of the Attorney General alleges that Lyft collected and shared or sold data such as IP addresses and imprecise geolocation for targeted advertising, without a native opt-out in the app. According to the complaint, users were led through multiple screens to a browser and had to supply login details or additional information again there.

The core is the relationship between data use, the user interface and the enforceability of the choice. Lyft delivers its service solely through an app. When the route to the privacy choice lies outside that channel, requires multiple steps and asks users to resubmit information, the state alleged that the process created too high a barrier. The CCPA rules, whose relevant version took effect on 14 August 2020, set requirements for consumer notice, the handling of requests and identity verification; the overview of the CCPA regulations places those obligations in context.

What concrete obligations does the proposed judgment impose on Lyft?

The proposed final judgment and permanent injunction translates the settlement into concrete, verifiable obligations. They go beyond a sum of money and touch design, risk assessment and monitoring.

  • Offer a clear opt-out link or setting within the app itself.
  • Carry out opt-outs across the relevant Lyft services, not limited to one component.
  • Inform consumers transparently about the sale or sharing of their data.
  • Carry out risk assessments for, among other things, the sale or sharing of personal data and the use of geolocation for advertising.
  • The proposed judgment provides for a monitoring and reporting programme over three years.
  • The proposed judgment provides for payment of $1.8 million within thirty days of the effective date.

What the sources leave open is the precise design. The sources largely leave the precise design of the in-app choice open. The judgment requires a clear opt-out link or setting within the app; the complaint additionally describes why the state regarded a route through multiple screens and additional information as a barrier. In our assessment, a practical implementation would place the choice in a logical location in the app settings, minimize the number of actions required, and request only information genuinely needed to apply the choice to the correct account; these are implementation recommendations, not additional terms expressly stated in the judgment.

What does this settlement mean for directors and privacy professionals at app-only services?

Our analysis is that organisations delivering services almost solely through an app should assess whether their privacy choices are available in the main user channel, because the Lyft allegations and remedy highlight a comparable design risk; in our recommendation, product owners and the privacy department jointly map where the opt-out actually sits and how many screens a user needs to reach it. Because the complaint alleges that Lyft’s particular redirect, multiple screens and additional login information created a barrier, our analysis is that services using a separate web-domain privacy portal should assess whether their own route unnecessarily hinders the choice. In our recommendation, lawyers should assess in the short term whether the chosen route hinders rather than facilitates the choice and revise the arrangement if it does. Because the judgment requires risk assessments for sale, sharing and geolocation use, in our recommendation a one-off privacy statement is insufficient; the controller records per data flow which data is shared for advertising, on which legal basis, and documents that assessment before rolling out new advertising integrations. Because the monitoring and reporting programme runs for three years, in our analysis compliance becomes an ongoing duty of demonstrability; in our recommendation the board appoints a responsible person who periodically checks whether opt-outs are genuinely carried through across all services and whether the evidence remains in order. We saw the same logic earlier in the DPC fine against MTCH over an incomplete self-service download tool: regulators look at the outcome for the user, not at the existence of a button.

This case fits a broader line in which regulators combine data practices and the workability of rights, such as the suspension of Grok training after a request from the Irish regulator. For the European reader it is a useful mirror: although the CCPA is not the GDPR, the underlying question also touches on pseudonymisation under the GDPR and the duties that still apply. Anyone who sets up privacy choices and accountability seriously will find more context in our topic hub on AI privacy and GDPR obligations. The practical lesson stays simple: the right must work in the place where the user uses the service.

Sources and references

  1. Privacy Rights Can’t Be Left in the Rearview: Attorney General Bonta Secures $1.8 Million Settlement with LyftCalifornia Department of Justice, Office of the Attorney General · 2026-10-29
  2. Complaint for Injunction, Civil Penalties, and Other Equitable Relief: The People of the State of California v. Lyft, Inc.California Department of Justice, Office of the Attorney General · 2026-10-28
  3. [Proposed] Final Judgment and Permanent InjunctionCalifornia Department of Justice, Office of the Attorney General · 2026-10-29
  4. CCPA RegulationsCalifornia Department of Justice, Office of the Attorney General · 2026-11-17

Sources: The article relies on the official announcement, the complaint, the proposed judgment and the CCPA regulations page of the California Office of the Attorney General.

← All articles in this topic ← All articles