What 'owner-consented' vehicle data actually means
Connected-vehicle data only works as a trust story. Here's exactly what the customer agrees to, what's read, what never is — and why the consent model is the feature, not the fine print.
Say 'we can read your customers' cars' to a dealer principal and the first reaction is usually a wince — it sounds like surveillance. It isn't, and the difference is the consent model. Understanding it matters, because it's also what you'll be explaining to your customers.
What the customer actually agrees to
The owner connects their own vehicle through an explicit authorization flow — the same pattern as linking a bank account to a budgeting app. They see exactly which permissions they're granting, vehicle by vehicle, and they can disconnect at any time. No credentials are handed over, nothing is installed in the car, and no dongle ever touches the OBD port.
What's read — and what never is
- Read: odometer, oil life, tire pressure, battery and charge state, diagnostic codes
- Read: the signals that predict a service need or a trade window
- Never: conversations, contacts, or anything from the cabin
- Never: data the owner didn't explicitly authorize
Why consent is the feature
A customer who connects their car is opting into a better ownership experience: service booked when it's actually due, a heads-up before a lease overage bites, a real offer when their equity turns positive. Framed honestly — 'let us look out for your car' — connection rates reflect the value. Framed lazily, it reads as tracking. The pitch is the product.
For the dealer, the compliance posture completes the story: data minimization by design, an auditable trail of every read, and infrastructure independently certified to ISO 27001 and 27701. Trust isn't a disclaimer at the bottom of the page — it's the reason the whole layer works.