What Was Taken That Money Cannot Repay

Imagine you pay for a tank of gas. You use your car, you park it in the garage for the night, and you go to sleep. While you sleep, someone has a hose connected to your fuel line. They are siphoning off small amounts, continuously, to power their own operation. When you wake up, your tank is slightly less full. You had no idea. If you try to stop it with the shutoff valve they installed, the valve doesn’t actually work. They labeled it, they let you reach for it, but the siphon kept running.

That is what this case alleges Google did to more than 100 million Android users across the United States for years. The currency was not gasoline. It was cellular data: a resource you pay for, often in strict monthly allotments, with real dollar penalties if you go over. You paid your mobile carrier for every megabyte. Google used some of those megabytes for its own purposes, in the background, without your permission, and without honest disclosure.

The theft, if that is the right word, was designed to be invisible. It happened when your screen was locked. It happened at night. It happened in your pocket and on your nightstand. The court filings describe Google’s Android operating system “secretly appropriating cellular data paid for by Plaintiffs” while devices sat “seemingly idle.” The word “secretly” is in the complaint. That word matters.

The people in this class are not corporations with legal teams on retainer. They are ordinary people who bought budget Android phones because those were the phones they could afford. People on prepaid data plans where every megabyte costs real money. People on fixed incomes who monitor their data usage carefully every single month. People who turned off what they believed was a background data setting, felt reassured, and were still being drained. The reassurance was a lie encoded into the software.

There is also the question of what Google did with that data. The transfers did not disappear into the void. They went to Google’s servers. The complaint describes “a variety of information” transmitted to Google without users’ permission. This was not a bug. This was a system, running on the most widely used mobile operating system on Earth, operating by design. When a corporation with Google’s engineering talent, resources, and internal review processes builds a data toggle that doesn’t work, that toggle does not fail. It performs exactly the function someone intended.

Five years of litigation produced tens of thousands of internal Google documents. It produced nearly 50 days of in-person review of Google’s proprietary source code. It produced depositions of 17 Google employees. Those documents exist. That code was read. Those employees were questioned under oath. The public will likely never see most of that material. What they will see is a $135 million check and a promise to fix the disclosures going forward. For 100 million people whose data was used without real consent, that math lands differently depending on your bank balance.

The court in this case explicitly questioned whether the fair market value of the data drained from users was, in the judge’s own words, “negligible, like really negligible.” That framing deserves scrutiny. The individual value of each data transfer may have been small. But “small per person” multiplied across 100 million people, repeated continuously over years, produces the billion-dollar exposure figure that plaintiffs’ own experts calculated. The smallness was the strategy. Take a little from everyone. Stay below the threshold of outrage. Keep the toggle labeled but broken. The people who felt the drain most acutely, those on tight plans with strict caps, were precisely the people with the fewest resources to pursue individual legal remedies.

What the Documents Actually Say

These are direct quotations from court filings in Case No. 5:20-CV-07956-VKD, filed in the Northern District of California. Nothing below is paraphrased. The words are Google’s, the court’s, and the plaintiffs’ lawyers’, on the record.

“While Plaintiffs’ Android devices are in their purses and pockets, and even while sitting seemingly idle on Plaintiffs’ nightstands as they sleep, Google’s Android operating system secretly appropriates cellular data paid for by Plaintiffs.” Plaintiffs’ Complaint, ECF 1, ¶ 3 — Taylor v. Google LLC, Case No. 5:20-CV-07956-VKD

• This is the core allegation of the lawsuit. It establishes that the data drain was continuous, not occasional, and that it occurred specifically during periods when users were not actively using their devices.
• The word “secretly” is the legal operative word here. It is what separates a disclosed service from an alleged conversion. Conversion is the legal term for taking someone’s property without consent.
• The phrase “cellular data paid for by Plaintiffs” grounds the harm in real money. This was not abstract data floating in the ether. Users paid their mobile carriers for this data, and Google consumed it without disclosed permission.

“Google will be required to change the ‘Learn about Google Play services’ Help Center page to explain that Google Play Services ’causes Android devices to exchange information with Google over cellular networks if the device is not connected to Wi-Fi, meaning Google Play services may use your mobile data’ and that these transfers ‘cannot be turned off.'” Settlement Agreement, Ex. 10, at 47 — quoted in Motion for Preliminary Approval, ECF 260

• This required disclosure did not previously exist. Google is being compelled to add it specifically because it was absent during the entire class period. The absence of this language for years is an admission embedded in the remedy.
• The phrase “cannot be turned off” is the most significant four words in this settlement. It confirms that users had no functional ability to stop these transfers, and that any interface suggesting otherwise was misleading.

“By tapping ‘Accept’ at the bottom of this screen and continuing, you agree that software and apps on your device may automatically communicate with Google servers for a range of purposes, including using your cellular data when you are not connected to Wi-Fi… Some of these communications may happen in the background, when you are not directly interacting with your device, including when the device’s screen is locked. You can control some of the communications through user settings… but some of the communications cannot be turned off. You are responsible for any fees incurred from third parties (such as your mobile carrier) in connection with these cellular communications.” Required New Setup Screen Disclosure Text, Settlement Agreement, Ex. 10, at 52

• This is the full text of the new disclosure Google must now show every user setting up a new Android device. Its existence is proof that no equivalent disclosure existed before this lawsuit forced it. Google sold hundreds of millions of phones without this language.
• The clause “You are responsible for any fees incurred from third parties (such as your mobile carrier)” is notable. Google drafted language explicitly acknowledging that its background data use costs users real money to their carriers, while simultaneously arguing in litigation that those damages were “negligible.”
• The phrase “some of the communications cannot be turned off” appears in the required disclosure language. This is Google, in writing it agreed to, confirming that users have no full opt-out available.

“Plaintiffs understand that, until now, this toggle has purported to give users the ability to turn off Google Play Service’s use of mobile data in the background, but generally has not disabled the transfers at issue in this case.” Motion for Preliminary Approval, ECF 260, at 15-16, describing the ‘allow background data usage’ toggle

• This is the fake toggle admission. A setting visible to users in their Android settings menu presented itself as a control but did not function as one. Users who found and toggled this off believed they had stopped the background data use. They had not.
• The settlement requires Google to “gray out this toggle and not allowing it to be moved by users into the ‘off’ position,” which eliminates the misleading impression. But the misleading toggle existed for the entire class period, which began in November 2017.

“The thing that I found most compelling about Google’s argument on the Daubert damages is that the Plaintiffs’ experts don’t seem to be valuing the it that you have described to me as the converted data… your expert seems to be valuing something other than what is converted.” Hon. Virginia K. DeMarchi, August 19, 2025 Hearing Transcript, ECF 228, at 52:18-21 and 58:24-59:2

• The federal judge presiding over this case expressed significant skepticism about the plaintiffs’ damages methodology during the class certification hearing. This judicial skepticism is the primary reason the settlement was reached at $135 million rather than the billion-dollar-plus figures plaintiffs’ experts had calculated.
• The judge also stated that under certain interpretations, the value of the converted data could be “negligible, like really negligible.” This framing, appearing in a federal courtroom, illustrates how corporate property violations can be rendered legally invisible when the individual harm is small even while the aggregate theft is enormous.

Who Paid the Real Price

Public Health of Democracy: Informed Consent

The core harm documented in this case is the systematic erosion of informed consent at scale. When 100 million people use a device believing they have control over its data behavior, and they do not, the consequences reach beyond individual phone bills.

• The settlement documents confirm that Google never disclosed to Android users, in clear language during device setup, that background system services would consume cellular data without user interaction. This absence of disclosure persisted from at least November 12, 2017 through the filing of the settlement in January 2026, a period of over eight years.
• A setting designed to look like a user control, the “allow background data usage” toggle, was present in Android’s settings menu but according to court documents “generally has not disabled the transfers at issue.” Users who specifically sought to limit their data usage were given false assurance. The psychological harm of discovering a safety mechanism was inoperative is not captured in any damages calculation.
• The injunctive relief required by this settlement mandates that future Android setup flows include the explicit statement that certain transfers “cannot be turned off.” This phrasing did not exist in any prior Google disclosure. Every user who set up an Android phone before this settlement was kept in the dark about a fundamental limit on their own device control.
• The Ninth Circuit had to reverse a district court dismissal before this case could proceed. Without that appeal, the conduct alleged would have faced no accountability at all. The fact that the case nearly died in 2022 illustrates how corporate data practices can survive legal challenge even when the underlying conduct is documented.

Economic Inequality: Who Bears the Cost of “Negligible” Data

The framing of individual harm as financially “negligible” is itself a class issue. The people for whom fractions of a dollar matter most are the people least equipped to fight back.

• Plaintiffs’ damages expert calculated total class-wide exposure of over $1 billion using industry average cellular data pricing, or approximately $9.98 per person based on an estimated class of 105 million people. That figure was later projected to potentially reach $2 billion, or $19.05 per class member, if updated through December 2025.
• The presiding federal judge stated in open court that under Google’s preferred damages theory, the value of the converted data could be “negligible, like really negligible.” This judicial framing treats harm as legal only if it is large enough for wealthier consumers to notice. Prepaid smartphone users on tight monthly data caps experience the same aggregate loss as wealthier users but with proportionally greater financial impact on their monthly budgets.
• Individual payments from the $135 million fund are capped at $100 per class member. After attorneys’ fees of up to $39.8 million and administrative costs of approximately $9.3 million, the net fund available for distribution to 100 million class members is roughly $85.9 million: less than $1 per person at full participation.
• The settlement’s automatic payment mechanism, which attempts to push payments through PayPal, Venmo, or Zelle using Google’s own records of user email addresses, relies on those users having accounts on those platforms. Users without such accounts, who may include older, lower-income, or less digitally integrated class members, must actively claim their payment or risk receiving nothing.
• Google’s annual revenue runs in the hundreds of billions of dollars. The $135 million settlement, described in court filings as “the largest class action settlement ever of a conversion claim in federal court,” represents a fraction of a single day’s revenue for the company. The deterrent value of such a settlement on a corporation of Google’s scale is a legitimate and open question.

What $135 Million Means in Context

Who To Watch and What To Do

The settlement is pending preliminary and final court approval, with a final hearing scheduled for the first week of June 2026. Here is who is accountable, who is watching, and what you can do.

The Entities Responsible

• Google LLC: The defendant. Builder and operator of Google Play Services (GMS Core), the software component at the center of this case, which is installed on substantially all Android phones sold in the United States.
• Alphabet Inc.: Google’s parent company. Not named as a defendant in this filing, but the financial and strategic entity that benefits from the data collection infrastructure at issue.
• Named Plaintiffs: Joseph Taylor, Mick Cleary, Jennifer Nelson: The three individuals who brought this suit on behalf of the class. They receive the same pro rata payment as every other class member, plus any service award approved by the court.

Regulatory Watchlist

• Federal Trade Commission (FTC): Has jurisdiction over deceptive trade practices affecting consumers. The fake toggle, which misrepresented user control over data, fits squarely within FTC deception standards. File consumer complaints at ftc.gov/complaint.
• Federal Communications Commission (FCC): Regulates the cellular data networks whose capacity Google was consuming without users’ knowledge. The intersection of mobile network use and device software practices sits within FCC’s evolving privacy authority.
• State Attorneys General: The California AG’s office is already involved via the companion Csupo case. AGs in every other state cover the Taylor v. Google settlement class. If you want this conduct investigated at a state level, contacting your state AG is a direct action.
• Hon. Virginia K. DeMarchi, U.S. District Court, Northern District of California: The judge who must approve this settlement. Court proceedings are public. The final approval hearing is scheduled for the first week of June 2026. Members of the settlement class have the right to file written objections before the objection deadline (84 days after preliminary approval is issued).
• Congress, Senate Commerce Committee and House Energy and Commerce Committee: Federal consumer data protection legislation has stalled repeatedly. This case is direct evidence of what happens when no comprehensive federal privacy law exists.

What You Can Do Right Now

• If you used an Android phone with cellular data in the United States outside California at any point from November 12, 2017 onward, you are likely a class member. Watch your email. The settlement administrator will attempt to contact you directly using Google’s records of your email address. Do not assume the payment will arrive without your participation.
• Check your Android phone’s settings right now. Go to Settings, then Apps, then Google Play Services, then Data Usage. The settlement requires Google to gray out the “allow background data usage” toggle. If it is still active on your current device, this change has not been implemented yet. Document it.
• If you believe the $135 million settlement is inadequate given the scale of the alleged conduct and the billion-dollar damages calculations in the record, you have the legal right to file a written objection with the court before the objection deadline. Objections must comply with the requirements set out in Section 9 of the Settlement Agreement. You can also opt out of the settlement class entirely to preserve your individual legal rights.
• Share this information with people in your community who use Android phones and who may not know they have data plan rights in this case, particularly older relatives, neighbors on prepaid plans, and anyone who has complained about unexpected data overages. Class action settlements only work when class members actually know they exist.
• Support organizations working on digital rights and privacy legislation, including the Electronic Frontier Foundation (EFF), the Center for Democracy and Technology (CDT), and local digital literacy programs that help low-income smartphone users understand and control their device settings.
• If you are a mobile network carrier customer who was billed for overage fees during the class period that you believe were attributable to Google’s background data use, document those bills. Your individual financial harm may exceed what the class settlement will return to you, and you have the right to opt out and pursue separate action.