The Customer Was Enrolled. But Who Authorized the Data Collection? │ CLICBrain Weekly Briefing – Issue #30

Compliance Intelligence for Online Businesses.

What Changed. Why It Matters. What to Do Next.

 

The Customer Was Enrolled. But Who Authorized the Data Collection?

Operational Compliance Intelligence for Internet Businesses.

Welcome to the CLICBrain Weekly Briefing – operational compliance intelligence for internet businesses from CLIClaw.com.
Each week, we identify significant privacy, AI, advertising, data governance, email marketing, and regulatory developments and focus on what they mean operationally: what systems, workflows, governance controls, and evidence organizations should examine in response.
On October 29, New York Attorney General Letitia James announced a $220 million settlement with General Motors involving the collection and sale of drivers’ personal information. New York joined 35 other attorneys general in the settlement, which addresses GM’s Smart Driver program, dealership enrollment practices, and transfers of driving data to brokers for insurance-related uses.
According to the Attorney General’s announcement, GM presented Smart Driver as a way for customers to improve their driving safety and told drivers their information would not be shared with insurers without express consent. The states’ investigation found that GM instead sold driving information to data brokers under contracts specifying insurance-product uses, without disclosing that purpose to drivers.
The announcement also identifies problems earlier in the process: dealership enrollment incentives, employees allegedly accepting terms on customers’ behalf without consent, and an app that incorrectly displayed some drivers as not enrolled while their data was being collected and sold.
This briefing discusses the settlement and the investigative findings described in the Attorney General’s announcement, not findings of liability following a trial.

 

 

 

 

 

Evaluate Consent Alongside the Incentives That Produce Enrollment.

The operational lesson is not simply that consent language matters. It is that the organization should examine how authorization is obtained, recorded, displayed, and relied upon.
An enrollment record can show that a process was completed without resolving the most important questions:
  • What the consumer was told.
  • Who completed the enrollment.
  • What did the consumer understand?
  • What incentive influenced that person.
  • What the system recorded.
  • Did the displayed enrollment status match actual data collection?
  • What data was actually collected.
  • How the data was later used or disclosed.
  • Did the later use match the authorization obtained?
CLICBrain’s operational framework for this issue is Consent Integrity: checking whether the enrollment process and its supporting records reliably establish the consumer’s authorization for the activity at issue. This is an operational framework, not a legal test established by the settlement.

 

What the GM Announcement Reveals.
Enrollment Incentives and Authorization Need Separate Checks.
According to the Attorney General, most customers who signed up for Smart Driver did so at a dealership when purchasing a vehicle. GM used one sign-up process for Smart Driver and OnStar. The announcement alleges that dealership employees sometimes accepted terms and conditions on customers’ behalf without their consent.
The investigation also found that, between 2020 and 2024, dealership employees received bonuses based partly on connected-service sign-ups, including Smart Driver, and dealerships were ranked by enrollment numbers.
For an operational review, those are separate questions. An organization can measure enrollment volume while still failing to verify whether each enrollment reflects the customer’s actual authorization.
✔ CLIClaw Compliance Tip: A useful control question is: Does the organization reward completed enrollment without independently checking how that enrollment was obtained?

 

The Consumer-Facing Status Did Not Match Actual Processing.
The Attorney General’s announcement states that the OnStar app incorrectly told more than 370,000 drivers they were not enrolled in Smart Driver while GM continued collecting and selling their information. It further states that GM later unenrolled those drivers without telling them about the mistake and left their data with brokers and insurance companies.
This introduces a second operational problem: the difference between what the interface tells the consumer and what the underlying systems actually do.
Testing an enrollment-status screen is therefore only part of the review. The organization should also examine whether that status corresponds to collection, transmission, and downstream processing.

 

The Downstream Use Changed the Consequences.
Smart Driver collected information including trip frequency, trip start and end times, hard braking, rapid acceleration, and speeding. According to the announcement, brokers sold the information to insurers, which could use it to change premiums based on driving habits.
The important distinction is between the benefit presented at collection and the consequences of a later commercial use.
For an internet business, the comparable review question is: Before information enters another commercial process, who checks whether that use matches what the consumer was told and authorized?

 

Why This Matters to Internet Businesses.
Use this development as a prompt to review enrollment processes involving employees, sales representatives, affiliates, referral partners, or other intermediaries.
Potential review candidates include a loyalty program, analytics feature, connected service, or account benefit where someone other than the consumer can complete or influence enrollment.
The purpose is not to assume that every intermediary-assisted enrollment is improper. It is to determine whether the organization can distinguish among:
  • A consumer completing the process.
  • A representative assisting while the consumer makes the choice.
  • A representative acting under documented authority.
  • A representative accepting terms without that authority.
Those situations should not be treated as equivalent merely because the system records a completed enrollment.

 

 

 

 

 

Trace One Enrollment From Representation to Downstream Use.

Choose one process that authorizes personal-data collection or use. Examine the following:
Review point
Question to answer
Evidence to examine
Consumer representation
What benefit and data practice were described?
Enrollment screens, scripts, notices, and applicable versions
Enrollment actor
Who actually completed the process?
User identity, representative identity, timestamps, and available audit records
Authorization
What demonstrates the consumer’s choice or the representative’s authority?
Consent records and authorization documentation
Incentives
What rewards or targets influence enrollment?
Compensation plans, performance measures, and partner requirements
Displayed status
What does the consumer see after enrollment?
App and account screens, status histories, and test results
Actual processing
Does collection match that status?
Collection settings, event records, and transfer logs
Downstream use
What uses and recipients depend on the authorization?
Data inventories, contracts, transfer records, and use restrictions
The objective is to identify contradictions, not simply to confirm that each document exists.

 

Operational Problem.
No One Reviews the Whole Enrollment Process.
Consider this hypothetical division of responsibility:
  • Marketing approves the stated benefit.
  • Legal reviews disclosure language.
  • Sales measures enrollment.
  • Product designs the interface.
  • Engineering records the account status.
  • Partnerships manages recipients of the data.
Each function may review its own work without checking the complete sequence. The practical gap appears when one team relies on another team’s enrollment record as proof of authorization, or when a displayed setting is assumed to control a data flow that operates elsewhere.
✔ CLIClaw Compliance Tip: Assign responsibility for reviewing the complete process: Consumer representation → Enrollment action → Authorization evidence → System status → Actual collection → Downstream use

 

 

 

 

 

Incentives Can Shape Consent Quality. A reward for successful enrollment can encourage speed. Speed is valuable, but it is not the same as informed authorization.
Organizations should ask whether incentives reward:
  • Completed consent, or merely completed forms?
  • Accurate enrollment, or enrollment volume?
  • Consumer understanding, or employee efficiency?
 

 

Displayed Status Must Match Actual Processing. If a consumer is told they are not enrolled, the organization must determine whether data collection has actually stopped.
A status display is useful only if it reflects the system’s real data practices. Otherwise, the consumer’s apparent choice may be inaccurate.
 

 

Consent for One Use Does Not Authorize Another. Information collected for one purpose may later be considered for another. A driving-safety program does not automatically authorize insurance-related sales. The same principle applies to loyalty data, wellness data, support records, and analytics.
Before any downstream use, ask whether the original consent and disclosures authorize it.

 

 
Operational Problem.
Each Team Verifies Only Part of the Consent Chain.
Consider a familiar division of responsibility:
  • Sales measures enrollment.
  • Product designs the app experience.
  • Legal reviews the consent language.
  • Engineering records enrollment status.
  • Vendors receive data.
  • Partnerships approve data-sharing arrangements.
Each team may believe its part works. But unless someone reviews the entire chain, no one may confirm that the consumer’s actual authorization matches the data later collected, displayed, or sold.

 

 

 

 

 

“The Account Shows That the Customer Accepted.”

That statement should begin the inquiry, not end it. Ask who performed the action, what the customer saw, which version of the terms applied, and whether later data practices matched the recorded choice. If those answers are uncertain, the record may show acceptance without demonstrating authorization.
✔ CLIClaw Compliance Tip: A completed field is evidence of a recorded event. The review still needs to establish what that event demonstrates.

 

 

 

 

 

Test One Incentivized Enrollment Process.

Select one process where employees or partners receive credit for sign-ups.
  1. Compare the consumer-facing explanation with the actual collection and downstream uses.
  2. Determine whether an employee or partner can accept terms on the consumer’s behalf.
  3. Identify what evidence distinguishes assistance from unauthorized acceptance.
  4. Compare the status shown to the consumer with actual collection and transfer activity.
  5. Examine whether enrollment targets are balanced by authorization-quality checks.
  6. Document discrepancies and assign responsibility for correction.
If the review identifies enrollment without adequate authorization, inconsistent account status, or questionable transfers, involve privacy, legal, and relevant operational teams before deciding how to address affected records and downstream recipients.

 

 

 

 

 

Q: Does an enrollment incentive automatically make consent invalid?

CLICBrain: The GM announcement does not establish that proposition. It describes incentives alongside alleged unauthorized acceptance of terms and other data-practice failures.
The operational question is whether the incentive structure undermines reliable authorization. The legal question depends on the applicable law, the required form of permission, the representations made, and the facts of the enrollment. Qualified counsel should evaluate the legal consequence for a particular organization.
Have another compliance question? Ask CLICBrain on CLIClaw.com – available 24/7.

 

Related CLIClaw Solutions.
This week’s CLICBrain Takeaway highlights the intersection of privacy consent and authorization, sales and intermediary oversight, third-party data sharing, data-broker relationships, privacy assessments, and recordkeeping and verification of consumer choices.
CLIClaw‘s compliance resources can help organizations evaluate related AI, privacy, data security, vendor, marketing, data governance, and operational compliance requirements and identify where risk assessments, testing procedures, incident workflows, documentation, or governance controls may need additional attention.
Explore the CLIClaw Compliance Library to find practical guidance, compliance programs, SOPs, checklists, assessments, FAQs, and other resources for building and maintaining an operational compliance program.

 

One Question to Take With You.
Pick one consent-based process your organization rewards or measures. Could you prove that the person who completed it was authorized to act, that the displayed status matched reality, and that every later use matched what the consumer was told?

 

CLICBrain Weekly Briefings provide operational compliance intelligence and commentary for internet businesses. Regulatory developments, enforcement activity, and legal requirements discussed herein should be evaluated in the context of your organization’s specific operations, systems, data practices, jurisdictions, and risk profile. This briefing is for informational and educational purposes only and does not constitute legal advice.