General Motors just paid $220 million because of where data came from and where it went next. The dealer reading that headline is likely to think it is an OEM problem. It is not, because the question the states asked is the question any store's text list has to answer: where did this number come from, and what did the person agree to?
Most dealerships cannot answer that for more than a fraction of their list. The vendors who send texts under their own identity can answer it even less, and they are the exposed party.
What Did the GM Settlement Actually Establish?
The Drive reported the outline on October 30.
"General Motors has agreed to pay $220 million to 36 states to settle allegations that it sold drivers' data to brokers, who in turn sold it to insurance companies, where it was used to increase drivers' rates." The Drive
The reported settlement is $220 million, paid to 36 states, over allegations that driver data was sold to brokers and then to insurers.✓ Nov 1 Note the chain in that sentence: driver, automaker, broker, insurer. The harm landed at the end of a chain the driver never saw.
That is the shape of the exposure. The data moved to parties the person never agreed to, and nobody on the way could show a record of what the person had said yes to. The fine is the headline. The lesson is that provenance is now something an attorney general asks about first.
Why Is a Dealer's Text List the Same Question at Smaller Scale?
A dealership's contact file is built from many doors. Sold customers, service customers, form fills, an old purchased list, a vendor's "audience," a number typed into a chat at midnight. Each door carries a different permission, and most stores flatten them into one column called phone.
Once flattened, the origin is gone. A store cannot tell which numbers belong to its own customers, which agreed to marketing, and which arrived with a vendor and an assumption. When a complaint arrives, the store has a number and no story.
This is the weak point in how most texting gets bought. The vendor owns the sending tool, so the vendor owns the log, and the store owns the liability. If the vendor sends under its own registration, the store is renting its own customer line, as we argued in the case for registering the text number in the dealership's name.
Is Consent a Checkbox or a Ledger?
A checkbox is a moment. A ledger is a history. The checkbox says someone ticked a box once, on a form, on a page that may have changed since. The ledger says this number, this store, this permission, this date, this way it was confirmed, and what happened after: every STOP, every complaint, every deletion request.

The difference matters because consent is not static. People revoke it, numbers get reassigned, a customer who agreed to appointment reminders never agreed to a blast. A system that only stores the original yes cannot honor the later no.
The test is simple. Pick any number on your list and ask three questions. How did it get here? What exactly did this person agree to? Has anything changed since? If the answer lives in three systems and one employee's memory, you have a checkbox.
Who Is the Exposed Party When a Vendor Sends Under Its Own Identity?
The vendor sending under its own identity holds the registration, the sender, the log and the stop list. The dealership holds the brand on the message and the customer relationship. When a regulator or a customer comes looking, both are visible, and only one of them can produce the record.
Worse, a stop list that lives in the vendor's tool does not travel. Switch vendors and the opt-outs may stay behind. A customer who replied STOP in March gets a text in September from the new tool. The store did nothing wrong on purpose, and it is still the store on the message.
This is the agency problem in a new coat. The record of who was contacted and why was built by someone else, kept by someone else, and handed back as a dashboard. We made the same point about AI decisions in why an audit needs a record written at the time. Consent is the same: a record made when it happened, or nothing.
What Does a Defensible Consent Record Look Like?
Four properties, none exotic.
- One shared do-not-contact record. Every opt-out surface writes to it: an unsubscribe click, a spam complaint, a hard bounce, a text STOP, a privacy request. Every send checks it first, across email and text.
- Double opt-in for marketing texts. A number is enrolled only when that number itself replies YES. Nobody is texted first.
- The store's name on the first text. The first message to a number says who is writing and how to stop. STOP works everywhere and takes effect immediately.
- Deletion that actually deletes. A request to be forgotten becomes a universal do-not-contact row that no later YES can lift, and the identity records are purged on a schedule.
There is also a fifth, quieter property: an unreadable record holds the send. If the system cannot confirm a number is clear, it does not guess. That one rule separates a compliance system from a mailing tool.
Who the store may text matters as much as how. A dealership's own customer, one with a deal or a repair order in its books or on a list the store uploaded, can receive the store's own account texts such as appointment reminders. Marketing texts still need an affirmative consent record. A website visitor who typed a number on a form is texted only after their own YES.
The AUTONOMi Approach to Consent
AUTONOMi runs one shared do-not-contact ledger that every opt-out surface writes to, including unsubscribe clicks, spam complaints, hard bounces, text STOP replies and privacy requests, and it is checked before every LANE email and before every text and call the platform places.✓ Nov 1 When that record cannot be read, the send is held rather than risked.✓ Nov 1
A consumer joins the dealer text program through the "text me" web form or by texting SAVE to the dealer's number, and in both cases is enrolled only when the number itself replies YES, on the dealership's own registered line.✓ Nov 1 The first text to a number carries the dealership's name and the instruction to reply STOP, enforced in the one sender so no path can skip it.✓ Nov 1 Every consumer marketing text leaves from that line through one sender, capped at four per number per rolling 30 days.✓ Nov 1 AUTONOMi does not text website visitors cold. A visitor who typed a number on a form is texted only after their own YES.
Each dealership's text number is registered with US carriers under the dealership's own legal identity, with AUTONOMi filing and maintaining the registration as the dealer's agent.✓ Nov 1 The brand is the dealer, which is the opposite of sending under a vendor's registration.
A consumer's stop-everything or deletion request reaches the dealership, is recorded, and AUTONOMi applies it as a universal do-not-contact row across email and text that no later YES lifts, with the household's identity records scheduled for purge after a 24-hour grace window.✓ Nov 1 Quiet hours follow stricter state statutes for Texas, Florida, Oklahoma and Washington, and the federal window elsewhere.✓ Nov 1 That is the covered list, not a claim that every state law is handled automatically.
The ad accounts, analytics properties and tag containers AEGIS works in are dealer-owned, and AEGIS operates on delegated access the dealer can revoke.✓ Nov 1 The ledger is the same idea applied to consent: the store's record, on the store's line, in the store's name.
What Should a Dealer Do Before the Next Text Goes Out?
Start with an audit you can finish in a week. Pull the list. Tag each number with its door: sold, service, form, upload, vendor. Mark which have a recorded marketing consent and which do not. Whatever has no origin should not be texted until it does.

Then ask the vendor three questions in writing. Whose registration do the messages go out under? Where does the stop list live, and does it come with us if we leave? Can you produce, for one named number, the consent record in under a minute? The answers sort vendors faster than any demo.
Last, check that every channel feeds one do-not-contact record. A STOP by text that does not stop the email is the failure a complaint is built from.
Where Does Consent Enforcement Go From Here?
The settlement also reportedly requires a third party to audit the automaker's privacy programs. Expect the same posture to reach everyone who touches customer data: programs inspected against records, not promises. The stores that can print a ledger will call that inspection a Tuesday. The stores that cannot will find out what their vendor's dashboard was hiding.
If you want your consent record to live on your own line and your own ledger, sign up and see it on your live stack. Source: The Drive



