I Bought the Car. I Didn’t Hire a Witness.

A car should still be somewhere you can go to be left alone.

Not unreachable in an emergency. Not incapable of receiving a useful update. Just yours, for the duration of an ordinary drive. The distinction ought to be easy. Instead, we keep being asked to accept that convenience arrives with an expanding cast of companies somewhere beyond the windscreen, each apparently needing a small piece of the journey.

The objection is not that a machine contains a modem. It is that buying the machine does not seem to settle who gets to participate in using it.

01Follow the traffic

A study from Northeastern University and Consumer Reports gives that objection something firmer than a sinister dashboard illustration. The researchers examined 21 vehicles from 19 brands and 30 companion apps. They observed network destinations and traffic patterns from the cars; encryption prevented them from reading vehicle payloads. Instrumenting phones gave them a closer look at app transmissions. Seven apps sent sensitive identifiers to third-party companies.

That distinction matters. A connection to a server is not proof of the exact information inside it. Nor is this a census of every car or every current software version. The study measured a sample, and its vehicle and app samples did not completely overlap. Its authors also excluded CarPlay and Android Auto phone-mirroring systems from their examination.

The findings are troubling without embellishment. We do not need to turn them into the claim that every car sells every journey to an insurer. Identifying who receives data, and what can actually be observed leaving the device, is a better starting point than declaring the entire dashboard guilty.

Studio Chicane / AI-generated editorial illustration. An imagined generic electronics module, not a component identified in the research or a technical drawing.

02The app is part of the car now

The showroom version of connectivity is always appealing. Unlock it from the kitchen. Check whether you left a window open. Find it in a vast parking lot. Nobody needs an enthusiast lecture about why those conveniences are morally inferior to a metal key.

But an app installed to perform a narrow task creates another relationship. There is the manufacturer, the phone platform, the app's service providers, and whatever analytics has been attached to the experience. To the customer it is one button labelled with the thing they want done. Behind it can be several organisations with different responsibilities.

The right question is not whether any outside supplier is involved. A car company cannot reasonably be expected to manufacture the internet. The question is which participation is necessary for the promised service, which is optional, and whether the owner can tell the difference before agreeing.

A remote command must travel somewhere. That does not make every associated measurement self-justifying. Diagnose a failed unlock, and explain the diagnostic purpose. Improve an app, and explain what is measured. If the purpose is something else, name it. The marketing department's preference for frictionless onboarding is not a reason to make the owner's decision less informed.

03The answer deserves to be in the story

Northeastern's September 29 report includes responses from manufacturers. Honda said the VIN and location information shared with a provider was contractually barred from independent use or sale; the report says Honda requested deletion and changed its app to stop sending geolocation data to that provider. GM said its providers operate under restrictions that prohibit using the data for their own purposes.

Those are relevant responses, not small print to be discarded because they complicate an angry headline. Sending information to a contracted processor and selling it for unrelated exploitation are not automatically the same act. The researchers' criticism concerns transparency and control as well as transmission.

Still, a contractual restriction that an owner never sees is a different kind of reassurance from a comprehensible choice on the screen. I want both: meaningful limits downstream, and a straightforward account of what I am agreeing to upstream. The manufacturer should not have to choose between them.

04A better definition of equipment

We can spend an absurd amount of time specifying a car. Stitching, wheels, dampers, seats, the particular finish around a vent. Then we accept its data behaviour as though it were weather.

It belongs on the equipment list.

Not a badge saying privacy matters. An intelligible description of the functions that require an account, the information each uses, the outside recipients and their purposes, and what remains available when you decline. A buyer ought to be able to compare two cars on that basis just as they compare their rear seats.

That would also improve the argument. Connectivity is not one indivisible good that owners must either embrace or reject. Emergency assistance, navigation, remote access, diagnostics and optional personalisation are different jobs. Treating them as distinct choices would let useful technology defend itself on its merits.

The request is modest: the more optional a purpose is, the harder the system should work to obtain a deliberate yes. Refusal should not be designed as a punishment or buried beneath invitations to reconsider.

05Ownership has a second chapter

Enthusiasts tend to talk about the moment a car becomes theirs. The keys, the first photograph, the first unnecessary trip. A connected car adds another moment we ought to take just as seriously: the moment it stops belonging to the previous person.

A sensible handover needs more than empty cupholders. Follow the manufacturer's procedures for removing paired phones, saved destinations, profiles, digital keys and connected-service relationships. Check what an in-car reset does and what separately requires an account transfer. That is a model-specific task, not a universal claim that pressing one button severs every link.

The same discipline applies in the other direction. Before blaming a car for a particular data practice, establish the model, software, app, settings and evidence. An old forum warning may concern a previous version. A promising new privacy setting may not govern every service. Specificity is how an owner gets a useful answer.

This is related to keeping the car beyond its service plan. The transaction at the beginning is not the full life of the thing. A durable car needs a comprehensible service history; a durable connected car also needs a comprehensible account history.

Studio Chicane / AI-generated editorial illustration. A generic radio study, not a tested product. Convenience and connectivity are choices worth separating.

06Let the drive remain a drive

There is a temptation to make this another contest between old cars and new ones. Buy something without a modem and declare victory. That can be a satisfying personal choice. It is not a sufficient answer for someone buying an ordinary new family car.

They deserve useful technology without having to become network researchers. They should not need to reverse-engineer a routine journey to understand the bargain they made.

In Keep the Radio. Fix the Listening., the point is to separate a desired function from the assumption that every surrounding change must be accepted with it. The same principle applies here. I can want navigation without wanting an opaque data relationship. I can appreciate remote access without volunteering for every adjacent experiment in customer insight.

The study's value is that it makes a hidden arrangement more visible. Its limits are a reason to investigate further, not to invent what the researchers could not see. The editorial demand can nevertheless be clear now.

Tell me what leaves. Tell me where it goes. Tell me why. Give me a meaningful choice.

Then let me drive my car.