Concern 420 · Working draft · editorial review in progress
Car-data collection
Connected-car data collection records information about a vehicle's movement, driving behaviour or occupants through built-in systems and services.
Understanding the concern
A car may transmit location and driving information for navigation, diagnostics or other features. Drivers may not expect the same data to reach a broker or affect insurance. Passengers and additional drivers may also be recorded without managing the original account. The data describes a vehicle's use, not always one person's behaviour.
The FTC's GM and OnStar case addressed allegations about notice and consent for location and driving-data use; a final order was announced in 2026. This shows why a general connected-service agreement may not make every later use obvious. Useful controls explain which feature needs which information and who receives it.
An example
A household discovers that driving data from a shared car has been used outside the feature they thought they enabled.
Illustrative unless identified as a documented case.
Evidence and its limits
The case concerns specific companies and allegations resolved by an order. It is not proof that every connected vehicle shares the same data.
Federal Trade Commission · Enforcement case
General Motors and OnStar: FTC Case ↗ (opens in a new tab)Allegations about location and driving-data consent; final order announced January 2026.
Broader frameworks and background
These resources provide context. They do not establish every claim in this concern.
- OECD AI Principles (opens in a new tab)
framework
- NIST AI RMF (opens in a new tab)
framework
A question to discuss
Are all drivers told what is collected and shared, and can they decline unrelated uses?
Keep track of different views, what needs checking, and any next step in your own discussion notes.
Open discussion notes →Principles for the conversation
Before you finish · reflect together
Virtues and principles to consider
Virtues are qualities we practice in how we treat people and make choices. They are not scores for judging someone. Use these ideas to explore what a thoughtful response could look like.
Dignity
Dignity means recognizing each person's worth regardless of usefulness, status, or a system's score. People deserve respect and a voice in matters that affect them.
Explain important decisions, avoid humiliating treatment, and keep room for a person's story. Do not treat a prediction as a complete account of who someone is.
Ask together: Does this use treat each person as someone whose experience matters?
Trustworthiness
Trustworthiness means giving people good reasons to rely on you. It grows when promises, actions, and evidence line up. With AI, a friendly voice or a famous brand is not enough: people need to know what was checked and what could still go wrong.
In practice, keep promises small enough to test, record mistakes, and tell people when the tool's limits affect them. If a service promises human review, make sure a person really has time and authority to review it.
Ask together: What would give the people affected a sound reason to trust this use?
Stewardship
Stewardship means caring for resources and systems that others depend on, including people who will use them later. It looks beyond the benefit of a quick launch.
Plan for maintenance, energy use, data protection, and eventual shutdown. Ask who will look after the tool when the original team moves on and how future users can avoid inheriting hidden costs.
Ask together: What are we responsible for caring for over time?
Editorial ratings
These are editorial judgments from the register, not measured probabilities or predictions about your situation.
About the register and scoring →More ways to explore
Search for more writing
For more specific or recent material, open a search below or ask for a web summary. AI-generated summaries can contain mistakes; open the original articles to check them.