The Car That Reports Back: A Practical Privacy Audit for the Connected Vehicle
Photo: Miscellaneous Items in High Demand, PPOC, Library of Congress, Public domain, via Wikimedia Commons
A modern vehicle contains somewhere between 50 and 150 electronic control units, a cellular modem, a Wi-Fi radio, multiple cameras, radar, and a microphone array. It pairs with your phone, imports your contacts, learns your commute, and communicates with the manufacturer's cloud from the moment the ignition is pressed. As a privacy matter, it is closer to a smartphone with seats than to the sedan your parents drove.
Consumer advocacy reviews have repeatedly ranked connected cars among the worst product categories for data handling, and subsequent research has not contradicted that finding. What follows is not an argument against owning one. It is an audit — the checks a careful owner can actually perform, and the questions worth asking before money changes hands.
What the vehicle collects
Broadly, four streams:
- Telematics and diagnostics — mileage, engine state, battery health, fault codes, and increasingly granular driving behavior such as acceleration, braking force, and speed relative to posted limits.
- Location history — GPS traces retained in the vehicle and often uploaded to the manufacturer, sometimes for years.
- Infotainment and cabin data — paired phone contacts and call logs, saved navigation destinations including "home," voice assistant recordings, and in some models cabin camera footage used for driver monitoring.
- Account and commerce data — the manufacturer account, subscription billing, app usage, and any in-vehicle marketplace purchases.
Manufacturer privacy policies commonly permit sharing with service providers, business partners, and in some cases data brokers. Vermont's data broker registry has at times listed automotive entities, and a handful of state privacy statutes now treat vehicle data as consumer data subject to access and deletion rights.
Audit step one: the infotainment account
The single most important asset is the account tied to your VIN. It controls remote start, location services, over-the-air updates, and often the data-sharing consents.
- Use a unique password and a password manager. If the manufacturer supports passkeys, enable them.
- Turn on two-factor authentication, and prefer an authenticator app over SMS.
- Log in through the web portal as well as the app. Data-sharing toggles frequently live in a settings page the in-car menu never shows.
- Review connected-service subscriptions. Every active service is a channel for data leaving the vehicle; deactivate the ones you do not use.
- Check whether the account permits adding secondary drivers, and remove anyone who should no longer have access.
Audit step two: the companion app
Companion apps routinely request continuous location access, contacts, microphone, and notification permissions. Some of these are legitimately required — remote climate control needs a data connection, and phone-as-key features need Bluetooth. Others are not.
Go through the phone's permission screen item by item and downgrade location from "always" to "while using" unless a specific feature breaks. Deny contacts access if the app does not need to place calls. Review the app's own in-product privacy settings separately; most apps have two layers, the operating system's and their own.
Audit step three: Bluetooth, contacts, and stored destinations
Pairing a phone typically imports the phonebook and call history into vehicle storage, where it persists after the phone is gone. Before returning a lease, selling the car, or handing it to a valet for an extended period, delete paired devices and clear the phonebook.
Do the same for saved navigation entries. A stored "home" address and a full recent-destinations list is a detailed picture of your life that takes ten seconds to erase and ten seconds to read.
If the vehicle has a garage-door or gate opener integrated, remove those pairings as well. This is the most concrete physical-security exposure in the entire audit.
Audit step four: over-the-air updates
Software updates are a security control, not an inconvenience. Deferring them indefinitely leaves known vulnerabilities unpatched in a device that connects to a cellular network on your behalf.
Enable automatic installation where offered, and complete updates when prompted. More importantly, treat update policy as a purchase criterion: ask how long the manufacturer commits to providing security patches for the model year, and what happens to connectivity features when that window closes. Vehicles now have software support lifetimes, and a car bought in 2026 may stop receiving fixes well before it stops being drivable.
Audit step five: insurers, dealers, and brokers
Usage-based insurance programs trade driving data for a discount. That trade can be reasonable — and it can also mean braking events and late-night trips become part of a risk profile that influences renewal pricing. Read what is collected, how long it is kept, and whether it can be used in a claims dispute. Opt in deliberately, not because the app was preinstalled.
Dealers receive diagnostic data as a matter of course. Ask your service department what is transmitted automatically and what requires your consent.
If you live in California, Colorado, Connecticut, Virginia, or one of the other states with comprehensive privacy laws, you likely have rights to request a copy of your vehicle data and to have it deleted. Manufacturers have dedicated portals for this; use them, and keep the confirmation.
Buying used: the questions that matter
A used connected car may still be bound to the previous owner's account. Resolve this before payment, in writing:
- Has the previous owner's account been unlinked from this VIN, and can you show me confirmation?
- Has the infotainment system been factory reset, and has the vehicle been removed from any prior companion app?
- What is the current status of the connected-services subscription, and who pays for it after sale?
- Are there outstanding recalls or pending over-the-air updates?
- Which data-sharing consents are currently active on this vehicle?
- What is the security-patch support end date for this model year?
A short owner's checklist
- Unique password plus strong second factor on the manufacturer account
- Location permission set to "while using" where possible
- Paired devices and stored contacts cleared before any transfer of ownership
- Home address and saved destinations erased before resale
- Automatic OTA updates enabled; support end date noted
- Insurance telematics enrolled only after reading the data terms
- State privacy access and deletion requests filed annually
None of this makes a connected car private in any absolute sense. It does convert an opaque data pipeline into a set of decisions you have actually made — which, for a device that knows where you sleep, is the reasonable standard.