Permission Granted (But Not For That)

sad young ethnic lady arguing during video call

I've said before that if a product is free, you're probably the product. The Texas Attorney General just filed a lawsuit that shows how that works in practice.

On January 13, Texas sued Allstate and its subsidiary Arity, alleging that they built "the world's largest driving behavior database" by secretly collecting data from more than 45 million Americans.1 According to the petition, the data came through popular apps like GasBuddy and Life360,2 using location permission granted for one purpose to collect data for something else entirely, including setting insurance rates for the people using those apps.

The permission was for gas prices, not driving scores

Here is how it worked, according to the petition. You downloaded an app like GasBuddy to find cheaper gas. You gave it permission to use your location because it needs to know where you are to show you nearby stations. What you didn't know was that the app carried Arity's software development kit (SDK), which collected your precise location (latitude, longitude, and altitude), your speed, your acceleration, your phone's tilt and orientation, and when and where your trips began and ended.3 The petition says that data was collected at least every 15 seconds.4

Collection was only the start. The petition alleges that Arity combined that movement data with personal information licensed from the app publishers, including names, phone numbers, addresses, device IDs, and mobile advertising IDs.5 The result was a detailed profile of people's movements that could be, and allegedly was, sold to insurers for underwriting.6

A phone can't tell who is driving

Arity marketed this as "driving behavior" data.7 The trouble is that your phone has no idea whether you're driving, riding as a passenger, taking the bus, or riding a roller coaster. That last one isn't hypothetical. One man reported that his driving score took a hit after he rode The Beast at Kings Island.8

Insurance decisions may have been based on data that can't tell who is driving, or whether anyone is driving at all.

The case tests the whole hidden-SDK business model

The allegations describe almost everything wrong with how mobile data collection usually works. The SDK's presence wasn't meaningfully disclosed to app users.9 The app granted location permission to find gas stations but used it for continuous tracking. Users had no way to opt out of collection or delete their data.10 And the resulting movement data was sold as something it couldn't actually measure.

This is the first major enforcement action under the Texas Data Privacy and Security Act, and it targets practices that are common across the mobile app ecosystem. The case questions the whole model of embedding SDKs in apps and using permissions granted for one purpose to collect data for another. Under Texas law, each violation can carry a civil penalty of up to $7,500.11

For years, many companies have treated privacy as a matter of clever legal language rather than technical controls. That approach builds up privacy debt, and this case is what it looks like when the debt comes due.

Your disclosures have to describe what your code actually does

For anyone building or maintaining systems that handle personal data, the lessons are concrete. If you're collecting data, say what you're collecting and why. A hidden SDK is undisclosed collection, whoever wrote it. Technical access to data isn't the same as permission to use it for any purpose you like, and your privacy statement must match your actual practices rather than serve as legal cover. Claims about what your data shows must be technically sound. You can't sell "driving behavior" if you can't tell who's driving.

None of this is confined to the past. The Attorney General alleges that Arity has collected data from "40 million active mobile connections," captured "every 15 seconds or less," and that kind of collection is running right now in apps on millions of phones. The era of collecting first and asking questions later is ending. Systems need to be built with privacy as the default, with clear disclosure, real consent, and controls users can actually use.

The technical debt of privacy shortcuts eventually comes due. The question is whether we'll learn from cases like this and start building better systems now, or wait until more lawsuits force our hand.

This post does not constitute legal advice. Readers should consult competent legal counsel before taking action based on the analysis presented here.

Follow on Google

Footnotes

  1. Press Release, Office of the Texas Attorney General, Attorney General Ken Paxton Sues Allstate and Arity for Unlawfully Collecting, Using, and Selling Over 45 Million Americans' Driving Data to Insurance Companies (Jan. 13, 2025), https://www.texasattorneygeneral.gov/news/releases/attorney-general-ken-paxton-sues-allstate-and-arity-unlawfully-collecting-using-and-selling-over-45. ↩︎
  2. Plaintiff's Original Petition ¶ 34, Texas v. Allstate Ins. Co. (Tex. Dist. Ct. filed Jan. 13, 2025). ↩︎
  3. Id. ¶ 3. ↩︎
  4. Id. ¶ 4. ↩︎
  5. Id. ¶ 83. ↩︎
  6. Jonathan Stempel, Texas Sues Allstate for Collecting Driver Data Without Consent, Reuters (Jan. 13, 2025), https://www.reuters.com/technology/texas-sues-allstate-over-data-collection-cellphones-2025-01-13/. ↩︎
  7. Plaintiff's Original Petition, supra note 2, ¶ 89. ↩︎
  8. Chad Murphy, Sir, This Is a Roller Coaster. Car Insurance Dings Driving Score for Man Riding The Beast, Cincinnati Enquirer (Oct. 8, 2024), https://www.cincinnati.com/story/entertainment/2024/10/08/insurance-cuts-driving-score-man-riding-the-beast-kings-island/75554987007/. ↩︎
  9. Suzanne Smalley, Texas Sues Allstate, Alleging It Violated Data Privacy Rights of 45 Million Americans, The Record, https://therecord.media/texas-sues-allstate-data-privacy-cars. ↩︎
  10. Plaintiff's Original Petition, supra note 2, ¶¶ 76-80. ↩︎
  11. Tex. Bus. & Com. Code § 541.155, https://statutes.capitol.texas.gov/Docs/BC/htm/BC.541.htm. ↩︎

Comments

Leave a comment

Never shown or shared; only the site's editors see it.

Comments are moderated before they appear. Plain text; web addresses become links.