GM to pay $220 million to 36 attorneys general over alleged OnStar and Smart Driver data sales, no admission
Washington and Oregon say General Motors will pay $220 million to settle claims it sold drivers' location and driving data to brokers that fed insurers. GM admits no liability, the brokers are not parties, and no driver payment is printed.
By Parminder Kumar Sharma · LinkedIn · · 20 min read
$220 million, 36 attorneys general, and no admission from GM
General Motors has agreed to pay $220,000,000 to settle claims by 36 attorneys general that it sold drivers' location and driving data to data brokers, which sold it on to insurers. The Washington consent decree prints $12,311,819 for Washington and Oregon's judgment prints $10,460,649 for Oregon. That is 5.6 per cent and 4.8 per cent of the total, 10.4 per cent together (derived: 22,772,468 divided by 220,000,000). The other 34 shares are not printed in the two texts read for this briefing. The complaint says GM made "over $20 million nationwide" from selling the data to two brokers, so the payment is about eleven times that figure (derived). That ratio is not a penalty to profit measure: the complaint's number covers broker sales only, and the decree lets the states spend the money on costs and enforcement.
What the figure does not establish matters as much. In the decree GM "do not admit to any violation or liability arising from any state, federal, or local law", and the decree says it cannot be used as evidence that GM broke any law. The money goes to the states, not to drivers. The data brokers and insurers are not parties, and GM is only required to ask them to delete data. In the copies the Washington and Oregon offices published, the judge's signature and date lines are blank, so the texts do not show that a court has entered them.
This briefing reads the Washington complaint and consent decree, Oregon's judgment, and the releases from Washington, Oregon, Connecticut and California, all read from 21:09 UTC on Thursday 29 October 2026. The Record's report of the same day is a secondary source and is used only for what it attributes to GM and to the Texas case. The Federal Trade Commission's own pages could not be read (the four ftc.gov addresses requested, including its robots file, answered 404), so the FTC action is described only as Connecticut's release describes it. GM's interest is plain: it is the defendant and wants the matter closed. The attorneys general's interest is equally plain: they are the enforcers and announced the result. Allegations below are allegations.
What the attorneys general allege, and where their papers differ
Washington's complaint was stamped as filed at 9:00 AM on 29 October 2026, the day of the settlement, and the decree resolves it in the same case (derived from the clerk's stamp and the matching case number). It runs to ten pages and is a pleading, not a finding. The table sets out the allegations the press releases lean on, with the paragraph that makes each one and a note on what it leaves unproven.
Allegations in Washington's complaint of 29 October 2026 (paragraph numbers as printed), with the releases read the same day. All are allegations; GM admits none.
| Allegation | Where it is made | What it does not show |
|---|---|---|
| Smart Driver, launched as part of OnStar, collected hard braking, hard acceleration, hard cornering, a high speed threshold, seat belt use, late night driving, and trip time and duration | Complaint paragraph 4.2. The releases say enrolment ran from 2016 to 2024; the complaint says GM released it in 2015 | How many drivers were enrolled. The Washington and Oregon releases say "millions" and give no count |
| Precise location was collected every three seconds from ignition on to ignition off, with latitude, longitude, elevation, heading, speed, a timestamp and a trip identifier | Paragraphs 4.3 and 4.13. Collection started in 2018. From 2019 a persistent vehicle identifier tied it to a VIN (4.14) | How many vehicles. The complaint says "millions of vehicles" and gives no figure |
| GM sold OnStar and Smart Driver data to Verisk from 2015 and to LexisNexis Risk Solutions from 2019. Lexis got precise location; Verisk's contract barred it | Paragraph 4.4. The brokers compiled consumer reports and driver ratings sold to insurers, and some insurers used them in part to set rates | Which drivers' premiums rose, by how much, or with which insurer. No insurer is named |
| GM told drivers an insurance discount programme would share anonymous data, but sold identifiable data for all enrolled drivers | Paragraphs 4.5 and 4.11. GM made "over $20 million nationwide" from these sales | Whether that sum is revenue or profit. The paragraph does not say |
| Over 370,000 drivers were told by GM's apps that they were not enrolled when they were; GM later unenrolled them without telling them | Paragraph 4.12; repeated in the Washington, Oregon and Connecticut releases | How long each driver was wrongly shown as not enrolled |
| GM licensed precise location to Wejo Ltd from 2018, then to Jacobs Engineering Group from 3 January 2024, and approved onward "egress licensees" | Paragraphs 4.15 to 4.17. Wejo is described as a United Kingdom based company that went bankrupt | Who the egress licensees are, or what they did with the data. None is named |
| Dealership staff earned bonuses and dealerships were ranked by enrolments, and staff "allegedly accepted terms and conditions on behalf of customers" | Paragraphs 4.19 and 4.20 and the Washington release | How many enrolments were made without the customer. No count is given |
| The decline path warned that declining "will result in deactivation of all services, including Automatic Crash Response, Emergency Services, and Vehicle Diagnostics" | Paragraph 4.10 | Whether the services were in fact deactivated for those who declined |
| GM's data collection and sale "impacted over 10,283,000 Americans, including at least 123,143 Connecticut residents" | Connecticut's release only. Neither Washington's nor Oregon's release, nor either decree, prints it | Whether the figure is an enrolment count, a driver count, or what period it covers |
Two of the allegations are about OnStar rather than Smart Driver. The location collection and the Wejo and Jacobs licensing in paragraphs 4.13 to 4.18 are pleaded against OnStar data, not the driving score programme. That matters for what GM said on the day. The Record quotes a GM spokesperson saying the "agreement addresses Smart Driver, a product we ended in 2024". The decree's own definition of covered data, set out under Technical details, reaches location data and radio listening data as well as driving behaviour, and it names OnStar by name as a service to be governed.
What the consent decree requires, with the dates it sets
The decree takes effect on "November 30, 2026" (the Effective Date) and its privacy programme obligations "shall continue until January 13, 2046", which is 6,984 days or about 19.1 years later (derived). Paragraphs 35, 38, 46 and 51 to 54 expire after ten years instead. Footnote 1 lists the 36 jurisdictions that are "simultaneously entering into similar judgments": by count of that list, 35 states and the District of Columbia (derived). So the result is 36 parallel judgments, not one national order, and the Washington text defines a protected "Consumer" as "a natural person in Washington". Oregon's reads the same with Oregon in its place. Paragraph numbers in this briefing are Washington's; Oregon's judgment numbers some of them one higher.
Main obligations in the Washington consent decree (paragraph numbers as printed). Deadlines are counted from 30 November 2026; the resulting dates are derived.
| Requirement | Paragraph | Deadline or term |
|---|---|---|
| Get affirmative express consent before collecting or using covered data, or disclosing it to any third party; a separate consent for each separate feature, including insurance affiliates' features | 41, 41a | From the Effective Date |
| The consent request must be separate from any privacy policy or terms of use, must name the data and each purpose, must name the buyers or link to a list of them, and must show how to withdraw | 42 | From the Effective Date |
| Do not degrade a product or service as a penalty for withholding or withdrawing consent, unless collection is technically necessary | 44 | From the Effective Date |
| Let drivers switch off location collection where the vehicle has the technology; let drivers who decline or leave OnStar disable remote collection of all data, with listed safety and update exceptions | 45, 47 | From the Effective Date |
| Enrolment in OnStar by the driver's own action, such as an email; a driver who does nothing for ten days is treated as declining; sample dealerships for anomalous enrolments | 48 | Within 60 days (by 29 January 2027) |
| Dealer training and materials saying customers must read and accept the disclosures themselves | 56 | Within 60 days (by 29 January 2027) |
| Pay $220,000,000 to the participating states, of which $12,311,819 to Washington | 71, 72 | Within 30 days (by 30 December 2026) |
| Specialised training for privacy staff | 50 | Within 45 days (by 14 January 2027) |
| Privacy programme, a chief privacy officer with quarterly reports to the General Counsel and annual reports to the board and the chief executive, public retention schedule | 31, 32, 67, 68 | Within 180 days (by 29 May 2027); runs to 13 January 2046 |
| Delete covered data retained from before 16 January 2025, except for listed purposes such as litigation holds and de identified research, and confirm it in writing to Washington | 62 | Within 180 days (by 29 May 2027) |
| Ask every third party that received covered data before 16 January 2025 to delete it; do not sell or disclose to that party again until it confirms receipt of the request | 55 | From the Effective Date |
| An independent assessor reviews the programme; the report goes to Washington's Attorney General within 30 days of GM receiving it | 57 to 59 | Assessor within 90 days (by 28 February 2027); first period 365 days, then every two years for four years |
| Easy ways for a driver to request deletion (processed within 60 days where no law gives the right) and a copy of their data (within 45 days) | 61, 64 | Until 13 January 2046 |
| Keep records of each consent, including the notice the driver saw and the time and date | 70f | At least five years after the Effective Date |
Several terms deserve a closer look than the headline gives them. The consent standard in paragraph 8 excludes "acceptance of general or broad terms of use", pre ticked boxes, silence and any interface that has the effect of "subverting or impairing user autonomy". The decree defines a safety carve out too: consent is not needed to disclose data to emergency responders, to answer a driver's own request, to comply with legal demands, for recalls and warranty work, or for research and diagnostics provided only de identified data goes to third parties (paragraph 41b). Coarse location, such as a ZIP code or a census block with a radius of at least 1,850 feet (about 564 metres, derived), is outside the definition of location data altogether.
What the record states, and what it does not
Stated and not stated in the Washington and Oregon texts and the releases read on 29 October 2026.
| Question | Stated on the record | Not stated |
|---|---|---|
| Did GM admit anything? | Paragraphs 75 and 76: no admission, and the judgment is not to be used as evidence of a violation | Any court finding that GM broke a law |
| Is the decree in force? | Effective Date is 30 November 2026; payment is due within 30 days of it | Entry by a judge. The signature and date lines are blank in both published copies |
| Who gets the $220 million? | The participating states. Washington $12,311,819 (paragraph 72); Oregon $10,460,649 (paragraph 73); Connecticut says it will receive "more than $6 million" | The other shares. Any restitution to drivers |
| Do drivers get anything? | Rights to a copy of their data and to deletion (paragraphs 61 and 64); an email notice to those enrolled in OnStar from 1 January 2018 (paragraph 65) | Compensation. Any reversal of a premium. A list of which drivers' data was sold |
| Are the buyers bound? | GM must request deletion from those who received data before 16 January 2025; a consumer reporting agency must give written confirmation of deletion or of a legal bar (paragraph 55) | That any buyer has deleted anything. Any term binding an insurer. Whether the data was already used in a rating model |
| Why 16 January 2025? | It is the cut off for both the deletion and the request to buyers | A reason. Connecticut's release says the Federal Trade Commission settled with GM on 16 January 2025, so the dates match; the match is this briefing's inference |
| How many drivers? | "Millions" (Washington, Oregon); 10,283,000 Americans and 123,143 in Connecticut (Connecticut only) | A count in either complaint or decree |
| Is this a fine? | The decree calls it a payment "to be divided by and among the participating states" and lets Washington use its share for costs, monitoring, enforcement or "any lawful purpose" | That it is a civil penalty. The complaint asks for penalties; the decree does not label the sum as one |
Five labels that do the work of a control
"Fine." The Record's headline calls the $220 million a fine. The decree does not. It is a payment divided among the states, with the Washington text allowing use for costs, monitoring and enforcement. A reader who hears "fine" assumes a deterrent calculated on the harm; the record shows no such calculation.
"36 states." It is 35 states and the District of Columbia, each entering its own judgment, each protecting its own residents. Fifteen other states are not on the list (derived: 51 jurisdictions minus 36). California settled alone on 8 May 2026 for $12.75 million, and The Record says Texas's case is ongoing.
"Smart Driver is over." GM ended the programme in 2024, as the Washington release and the complaint both say. The decree is written around OnStar and "covered driver data", which includes location and radio listening data, and it applies to any successor service with substantially the same functionality (paragraph 21). A product being switched off is not the control; the definition is.
"Consent." The complaint says drivers did click "I accept" on a series of screens, and that the decline path warned of losing crash response. A click was recorded; the attorneys general say it was not consent to selling data to insurers. Paragraph 8 of the decree is therefore the useful text: it lists what does not count as consent, including broad terms of use, pre ticked boxes, silence, and interfaces that subvert choice.
"De identified." Data that is de identified after collection falls outside covered data altogether (paragraph 13b). The decree sets a bar for that word: technical safeguards against re identification, business processes that bar buyers from re identifying, and no attempt by GM to do so. Data tied to a VIN, or to a vehicle's garage address, is never de identified. The word is a control only if someone checks it, and the assessor's report goes to Washington's Attorney General, and the decree does not make it public.
Earlier actions, and what is still open
Actions against GM over the same conduct, as the primaries read on 29 October 2026 describe them.
| Action | Money and terms as stated | Source |
|---|---|---|
| Federal Trade Commission, 16 January 2025 | "limited injunctive relief" and no monetary payment, per Connecticut's release. The FTC's own pages could not be read | Connecticut's release (secondary on this point) |
| California Attorney General and four district attorneys, 8 May 2026 | $12.75 million in civil penalties; a five year ban on selling driving data to consumer reporting agencies; deletion within 180 days. Subject to court approval at that date | California's release |
| 36 attorneys general, 29 October 2026 | $220 million; consent, minimisation, deletion, assessments and dealer controls to 2046; no admission | Washington and Oregon texts and releases |
| Texas, filed in 2024 | Ongoing. Seeks a jury trial, penalties of up to $10,000 per offence and a deletion order | The Record (secondary) |
| Consumer class actions | "Several" remain pending, per Connecticut. The decree does not "create, waive, or limit any private right of action" (paragraph 73) | Connecticut's release; the decree |
California's own account adds a useful limit. Its release says the investigation found Californian drivers were not directly hit by higher premiums, "likely because under California's insurance laws" insurers may not use driving data to set rates. The harm the 36 attorneys general describe, a premium that moved, depends on the insurance rules of the driver's state. The decrees do not say which states' drivers paid more. California's payment is 5.8 per cent of the multistate sum (derived: 12.75 divided by 220), and the multistate payment is 17.3 times California's (derived).
Technical details
This is a privacy enforcement matter, so the primaries print no hashes, domains or addresses. They do print the data fields, the consent screen wording and the definitions that decide what the decree covers. Each block below is copied from the document named in its caption, read on 29 October 2026. A privacy or data team can use them as a test list: does our own pipeline emit these fields, and do our own screens meet these definitions?
The location record. The complaint describes what each transmission held. At one record every three seconds, a vehicle that is driven for an hour sends 1,200 records (derived: 3,600 seconds divided by 3). The trip identifier is what turns separate records into a route.
This precise geolocation data consisted of latitude and longitude along with elevation, heading, current speed, a date and timestamp, and a trip identifier that could be used to tie multiple transmissions together to identify the entire route of a specific trip taken by a single vehicle. GM collected precise geolocation data every three seconds from ignition on to ignition off.
What the decree counts as covered data. Paragraph 13 is the scope of the whole decree. Two points: it names radio listening data and a short list of driving events, and it excludes data that is de identified after collection. Data tied to a VIN counts as reasonably linkable.
"Covered Driver Data" means information collected by Defendants that: i. Originates from a Vehicle or a General Motors-branded mobile application ("App"), or derived data (such as data generated algorithmically) from information originating from a Vehicle or App; and ii. Is Location Data or is one of the following events linked or Reasonably Linkable to a Consumer: a) radio listening data regarding specific content, channel, or station; or b) driver behavior information regarding hard braking, hard acceleration, hard cornering, crossing of a designated high-speed threshold, seat belt usage, or late-night driving; and trip time and duration for such events. b. Covered Driver Data excludes data (i) related to build, trim, make, model, and year of the Vehicle or (ii) that is Deidentified post-collection.
What does not count as location. The decree draws a line at coarse location, and at data kept only briefly to produce it. A system that stores a ZIP code level position is outside the definition; one that stores a point is inside.
Data that (1) reveals only a Vehicle's, mobile device's, or a Consumer's coarse location (e.g., ZIP code or census block location with a radius of at least 1,850 feet), or (2) that is used solely for the purpose of generating such coarse location and then Deleted within 48 hours of collection is not "Location Data."
The consent standard. Paragraph 8 is the sentence a product team can test a consent screen against. Each of the four exclusions describes a common design.
The following do not constitute Affirmative Express Consent: a. Inferring consent from the hovering over, muting, pausing, or closing of a given piece of content by the Consumer; b. Acceptance of general or broad terms of use or a similar document that contains descriptions of Covered Driver Data processing along with other, unrelated information; c. Obtaining consent through a user interface that has the effect of subverting or impairing user autonomy, decision-making, or choice; or d. Silence, inactivity or inaction, pre-ticked boxes, and other negative option opt-out constructions that require intervention from the Consumer to prevent agreement.
The words on the screens. The complaint quotes the privacy statement drivers were shown first. Its only mention of insurance is a promise of further consent. This is the text the attorneys general say was contradicted by the sales.
With business partners, such as SiriusXM, in connection with their products and services; research institutes, for research and development purposes (for example, improving highway safety); dealers, fleet or rental companies, for service maintenance of your vehicle. We may also share data with third parties for marketing activities (with necessary consents) or where you have elected to receive a service from them and/or authorized them to request data from GM (for example, financial organizations who offer financing for the purchase or lease of GM vehicles or usage based insurance providers)
will result in deactivation of all services, including Automatic Crash Response, Emergency Services, and Vehicle Diagnostics
The enrolment rule that replaces the dealership click. Paragraph 48 turns enrolment into something the driver does later and alone, with silence meaning no. A team can test this as a state machine: no action within ten days must land in the declined state, and covered data collected before enrolment is limited to the purposes in paragraph 41b.
Within sixty (60) days of the Effective Date, Defendants must implement and maintain a policy and procedure for Consumers to enroll in OnStar by independent Consumer action, such as via email ("Enrollment Notice"). Such policy and procedure must include that any Consumer who does not act within ten (10) days of the Enrollment Notice will be treated as declining enrollment in OnStar as set out in Paragraph 47 of this Judgment.
What to do, for drivers and for the companies that hold the data
The decree binds GM and, in the texts read, only GM, so a driver of another make is not covered by it. The first list is for any driver of a connected car. The second is for any organisation that collects or buys vehicle or device data. Items that go beyond what the primaries print are marked as general advice.
Take this with you
For drivers, in the order worth doing
- Find out what your car sends. Open the manufacturer's connected services account or app and look for driving behaviour, driver score or location features. Do not rely on the app alone: the complaint says GM's apps told over 370,000 drivers they were not enrolled when they were, so ask the manufacturer in writing too.
- Ask for a copy of the data held on you and the list of categories of recipients. GM must now provide a way to do this within 45 days (paragraph 64) and a way to request deletion (paragraph 61). For other makers, whether you have the right depends on your law; this briefing has not checked that.
- Switch off precise location in the vehicle where the setting exists, and decline connected services you do not need. GM must offer a location switch where the vehicle supports it (paragraph 45) and let you disable remote collection if you decline OnStar (paragraph 47). Other makers are not covered by this decree.
- Ask your insurer whether any driving score or usage based programme touched your quote or renewal and where the data came from. If a consumer reporting agency holds a file on you, ask it for a copy where your law gives you that right (general advice, not verified here).
- At the next purchase, read each connected services screen yourself and do not let staff click for you. The complaint alleges dealership staff accepted terms for customers, and the decree now requires GM to train its dealers that customers must accept the disclosures themselves (paragraph 56).
- Keep your own record: a photo of each consent screen and the date. GM must keep consent records (paragraph 70f), but yours may be the only copy you can reach.
Take this with you
For organisations that collect or share telematics, in the order worth doing
- Inventory every vehicle or device field you collect, its purpose, and every recipient, including onward licensees. The decree requires GM to keep an inventory of the categories it discloses (paragraph 38). You cannot answer a regulator, or a driver, without one.
- Make consent separate for each feature and test it against paragraph 8: no broad terms of use, no pre ticked boxes, no silence, no interface that steers. Treat a bundled sign up that enrols a customer in a safety service and a data programme at once as the failing case.
- Check that declining does not remove safety functions you do not technically need to remove. Paragraph 44 bars degrading a service as a penalty for withholding consent; the complaint quotes a warning that declining would deactivate crash response.
- Reconcile enrolment state across systems. Assert on a schedule that the flag a customer sees in the app equals the flag your pipeline uses to collect, and alert on any mismatch. The 370,000 case is a mismatch between those two.
- Make the contract the control. The attorneys general say GM's broker contracts specified insurance products and that one barred location data that the other received. Write the permitted use, a ban on re identification, onward licensing approval and audit rights into every contract, and check delivered fields against them.
- Plan for a buyer's insolvency or sale. The complaint says Wejo's assets were sold and a new licence with GM signed on the same day, 3 January 2024. Put change of control, deletion and certification terms in the contract before you need them.
- Do not pay staff or partners per consent click. Sample enrolments for anomalies as paragraph 48 requires of GM's dealer programme, and look for staff who enrol at unusual rates.
- Delete downstream, not only upstream. The Washington and Oregon releases say unenrolled drivers' data stayed with brokers and insurers. When a customer withdraws, send the deletion to recipients and keep the confirmation.
- Keep the evidence: the notice each customer saw, the choice they made, and the time and date (paragraph 70f), and assess before any new sale of covered data or disclosure of location to a third party (paragraphs 18 and 35).
The question the settlement leaves open
The decree gives GM a clear list of things to change and almost nothing on the data that has already left. GM must ask its buyers to delete and must hold off new sales until they confirm receipt of the request. It does not say that any buyer, or any insurer that bought a driver rating, must stop using what it has already built from the data, or must change a premium that rested on it. Connecticut says several class actions remain, and Texas's case continues, so those may reach further. The decree itself leaves private rights alone.
For any organisation that holds or buys vehicle data, the question is the plain one this case turns on. For the last driver your systems collected from, can you produce the screen they accepted, the date they accepted it, and the list of every party that received their data afterwards?
Key facts
Sources
- PrimaryNews release of 29 October 2026: $220 million, Washington co led, $12.3 million to Washington, the allegations, the injunctive terms and the list of 36 attorneys generalWashington State Office of the Attorney Generalaccessed 2026-10-29
- PrimaryComplaint, State of Washington v General Motors LLC and others, filed 29 October 2026: paragraphs 4.1 to 4.20 and the cause of action. Read as page images and by OCRWashington State Office of the Attorney Generalaccessed 2026-10-29
- PrimaryConsent decree, 38 pages: definitions, injunctive terms, the $220,000,000 payment and the $12,311,819 to Washington, the release, the no admission paragraphs, Exhibit A. Read in fullWashington State Office of the Attorney Generalaccessed 2026-10-29
- PrimaryNews release of 29 October 2026: Oregon to receive more than $10.4 million, the Unlawful Trade Practices Act basis, the co lead and executive committee listOregon Department of Justiceaccessed 2026-10-29
- PrimaryStipulated general judgment and money award, State of Oregon: the same terms with Oregon definitions, the $10,460,649 payment, the Effective Date and the 2046 end dateOregon Department of Justiceaccessed 2026-10-29
- PrimaryNews release of 29 October 2026: Connecticut to receive more than $6 million, 10,283,000 Americans and 123,143 Connecticut residents, the FTC settlement of 16 January 2025 and the pending class actionsConnecticut Office of the Attorney Generalaccessed 2026-10-29
- PrimaryPress release of 8 May 2026: the California settlement with GM, $12.75 million, 2020 to 2024 sales to Verisk and LexisNexis, and the finding that California drivers were not directly hit by premium increasesCalifornia Department of Justice, Office of the Attorney Generalaccessed 2026-10-29
- Reported byReport of 29 October 2026: GM's spokesperson statement and the status of the Texas case. Secondary, read for what it attributesThe Record from Recorded Future Newsaccessed 2026-10-29


