May 13, 2026 · 10 min read

The Opt Out Window Closes May 29: Google Will Pay $135 Million Because Android Phones Were Calling Home in the Background—Even While Idle

Taylor v. Google settled on the eve of trial. The complaint says Android devices transmitted user data over cellular even when the phone was idle and Wi-Fi was already available — a setup the plaintiffs valued at roughly $300 million a year in stolen consumer data.

The settlement notice for Taylor et al. v. Google LLC went out to roughly 100 million Android users in the United States. The case, filed in 2020 in the Northern District of California and presided over by Magistrate Judge Virginia K. DeMarchi, ended this spring with Google agreeing to pay $135 million into a common fund. Preliminary approval was granted on March 5, 2026. The opt out and objection deadline is May 29, 2026 — 16 days from now — and the final fairness hearing is scheduled for June 23.

Most coverage of the settlement has focused on the per user payout, which will likely come in between $1 and $1.50 once the fund is divided across the class. That number is small enough that a lot of people will tune out. The complaint behind it is not small. The plaintiffs alleged that Android devices, by design, were transferring data to Google's servers over the cellular network even when the phone was idle, every installed app was closed, and the device was already connected to a Wi-Fi network that could have carried the traffic for free.

Three Android smartphones resting on a wooden desk in a home office, one showing a cellular data signal indicator, suggesting devices that quietly transmit data even when not in use

What the Plaintiffs Said Android Was Actually Doing

The class representatives — Joseph Taylor, Mick Cleary, and Jennifer Nelson — filed in 2020 with a single forensic claim. They ran packet captures on stock Android handsets and documented network traffic to Google domains under conditions where nothing on the phone should have been transmitting.

Specifically, the complaint described:

Cellular transmissions while the device was idle. Screen off, no user input, no foreground app. The phone continued sending data to Google servers.
Cellular transmissions while Wi-Fi was connected and available. The phone preferred the metered cellular link over the free Wi-Fi link for a non trivial slice of background traffic. That choice cost the user money and saved Google nothing.
Transmissions with all third party apps closed. The traffic was not attributable to Facebook, Instagram, or any user installed app. The endpoints were Google services running as part of the operating system itself.
No opt out mechanism. The plaintiffs argued there was no setting an ordinary user could toggle to stop the behavior. Disabling location, disabling personalized ads, even logging out of the Google account did not stop the traffic.

The legal theory was conversion under California common law. Cellular data is a finite resource the consumer pays for. By using that resource for transmissions the user did not authorize and could not stop, Google had — in the plaintiffs' framing — converted the user's property to its own use. The complaint pegged the value of the converted data at approximately $300 million per year across the U.S. Android base.

Why "Conversion" Is the Important Word

Privacy class actions usually struggle to clear the standing bar. Federal courts have repeatedly held that the abstract harm of "my data was collected" is not concrete enough to confer Article III standing, especially after the 2021 TransUnion v. Ramirez decision narrowed what counts as injury in fact. Settlement amounts in pure privacy cases have historically been depressed by that doctrinal weakness.

Taylor v. Google sidestepped the problem by pleading the case as theft of a paid commodity rather than as a privacy violation. The harm was not "Google learned things about me." The harm was "Google used cellular data I paid Verizon for, without my permission, to enrich its own services." Conversion is an old common law tort with a clear injury element — the value of the converted property. That framing turned a notoriously hard category of case into a much more conventional one.

The same legal theory could, in principle, be applied to any service that uses metered consumer resources without consent. It is the kind of doctrinal hook plaintiffs lawyers tend to copy as soon as it produces a nine figure settlement, and the $135 million here will move conversion based privacy cases higher up the docket priority for the next few years.

Why California Is Excluded

If you have lived in California at any point during the class period, you are not eligible for this settlement. You may already have been covered by — or due funds from — Csupo v. Google, a parallel California only suit on substantively the same facts. That case settled in July 2025 for $314.6 million, more than twice the value of Taylor on roughly a tenth of the class. The math reflects two California specific factors.

First, California Civil Code §1798.81.5 and the CCPA's private right of action on data breaches gave the Csupo plaintiffs statutory damages without having to prove individualized harm. Second, California's Unfair Competition Law (§17200) has a lower causation bar than the equivalent federal claim. Both factors fed into a much larger per user settlement value.

The contrast tells you something about where consumer privacy enforcement is structurally strongest in the U.S. — California, by a wide margin. The other 49 states are riding behind a federal court system that requires concrete harm and an Article III standing analysis. California's $12.75 million OnStar settlement against GM earlier this month is another data point in the same direction.

The Injunctive Relief Is Where the Real Value Sits

The $135 million money fund is the part that gets reported. The behavioral changes Google has to make are the part that matters.

Under the settlement, Google has to amend the Google Play Terms of Service to disclose the cellular transmissions the complaint identified. The disclosure is not buried — it sits in the section users see during initial Android setup. The Terms now have to enumerate which categories of background traffic Google routes over cellular even when Wi-Fi is available, and Google has to provide a network policy mechanism that prevents that traffic from flowing over a metered connection. Class counsel projects that this single change saves the U.S. Android base roughly $300 million per year in cellular data charges that previously went to Google's silent uses.

The injunctive relief runs for a defined term — five years per the order — and Google has to certify compliance at the 18 month, 36 month, and 60 month marks. Settlement administrators reserve the right to seek attorneys' fees and additional monetary penalties if compliance lapses.

What You Actually Need to Do Before May 29

If you used an Android phone on a cellular network between November 12, 2017 and the final approval date — outside California — you are in the class by default. The settlement administrator will attempt to send you a notice and a payment without any action from you. In practice that has problems. The administrator only has reliable contact information for class members whose data Google's marketing graph held at the time of the preliminary approval. For everyone else, the recommended action is to file a Payment Election Form on the settlement website (Taylor v. Google) before final approval. The form asks for your name, an Android device identifier or carrier email on file, and a payment method — Venmo, PayPal, Zelle, or a mailed check.

May 29 is a different deadline. It is the cutoff for two actions, both of which are exclusionary:

Opt out. If you do not want to be bound by the settlement — typically because you want to file your own lawsuit against Google over the same conduct, or because you want to join a different action later — you have to mail or upload an exclusion request by May 29. Opting out forfeits your payment but preserves your right to sue separately.
Object. If you believe the settlement amount is too low, the attorneys' fees are excessive, or the injunctive relief is inadequate, you can file a written objection with the court by May 29. Objections are read by Judge DeMarchi at the final fairness hearing on June 23. If sustained, they can force renegotiation.

Both actions are formal. Both are explained in the official notice at the case website, and both have to be in the court's hands — not just postmarked — by the deadline. For the vast majority of class members the practical action is to do nothing, accept the modest payment, and benefit from the injunctive relief.

Why a $1.50 Payment Still Matters

The per claimant amount in Taylor v. Google is going to be smaller than the postage for a letter declining it. That has been the standard refrain from consumer skeptics of the class action format for thirty years: the lawyers get rich, the plaintiffs get coffee money, and the corporation books the settlement as a rounding error against forward year revenue.

Two replies to that critique are worth registering. The first is that the deterrent value of a settlement is not the per claimant amount; it is the total fund plus the cost of the injunctive relief. $135 million does not change Alphabet's quarterly earnings, but the operational cost of re engineering Android's network policy mechanism, certifying compliance, and submitting to court oversight for five years is real engineering work that competes against feature roadmap. That cost shapes future product behavior in ways a checkbook payment does not.

The second is that the precedent matters more than the dollars. Taylor v. Google has now established that a conversion claim against a tech platform for unauthorized use of metered consumer resources can survive a motion to dismiss, can certify a national class outside California, and can produce a nine figure settlement. That precedent is now binding in the Northern District of California and persuasive everywhere else. The next case — and there will be a next case — starts from a higher floor.

The Pattern Behind the Pattern

Background cellular transmissions are one instance of a broader architectural pattern. Mobile operating systems, email clients, smart TVs, connected cars, and most modern web pages all run telemetry pipelines that collect user behavior, route it back to the vendor, and use it for product improvement, ad targeting, or both. The user typically has no view into the volume or purpose of the traffic, and the cost of that traffic — whether measured in cellular bytes, in CPU cycles, in battery, or in extracted profile data — is silently absorbed by the consumer.

Email is the medium where this pattern is the most refined and the least scrutinized. A marketing message arrives in your inbox; an embedded 1×1 pixel calls back to a tracking server the moment your client renders the image; the sender learns when you read, where you were when you read it, and which device you used. The mechanics are the same as Android's idle cellular telemetry — silent transmission of consumer data to a commercial endpoint, with the consumer paying the resource cost. The legal cover for the email version is thinner than the legal cover for the Android version, but the litigation track record is also thinner. Taylor v. Google is the kind of precedent that, once portable, applies to email tracking under the same conversion theory.

The closest live analog in U.S. federal court at the moment is the Forbes $10 million CIPA wiretap settlement over web tracking pixels. Email tracking pixels are functionally identical to the Forbes web pixels, and the CIPA framework that produced that settlement applies to email beacons the moment a plaintiff brings the case. The CNIL, France's data protection authority, has already ordered email senders to stop tracking pixel use without consent by July 2026. The U.S. version of that order will arrive through case law rather than regulation, and Taylor v. Google is now part of the trail it will follow.